Measurement estimates from a single vantage point — not a compliance certification. Guidance below is for operators, not an SLA.
DNS
IPv4-only
[3] 0/0/0 [O]
Meaning: Shows how many authoritative name servers exist, and how many IPv6 endpoints are configured, responsive, and operational.
IPv4 3/3/3 · IPv6 0/0/0 · location O
| Host | IPv4 | IPv6 | Probes |
|---|
ns3.telinet.com.pg [O] |
124.240.221.43 |
— |
ipv4 124.240.221.43 ok; |
ns1.telinet.com.pg [O] |
124.240.221.33 |
— |
ipv4 124.240.221.33 ok; |
ns2.telinet.com.pg [O] |
124.240.221.34 |
— |
ipv4 124.240.221.34 ok; |
📌 Action item(s):
- Publish AAAA records for name server: ns1.telinet.com.pg, ns2.telinet.com.pg, ns3.telinet.com.pg.
Mail
Dual-stack
[5 MX] v4 smtp 5/5/4 v6 smtp 4/4/4 [M]
Meaning: Shows MX footprint and SMTP health per IP family. Operational means an SMTP banner and EHLO exchange succeeded on port 25.
IPv4 SMTP 5/5/4 · IPv6 4/4/4 · location M
| Host | IPv4 | IPv6 | Probes |
|---|
mail.telikom.com.pg [I] |
202.58.130.43 |
— |
ipv4 202.58.130.43 timeout; |
mx1.mtaroutes.com [O] |
149.13.75.27 |
2001:978:2:2c::137:100 |
ipv4 149.13.75.27 ok; ipv6 2001:978:2:2c::137:100 ok; |
mx3.mtaroutes.com [O] |
154.59.104.23 |
2001:978:2:2c::137:100 |
ipv4 154.59.104.23 ok; ipv6 2001:978:2:2c::137:100 ok; |
mx2.mtaroutes.com [O] |
149.13.75.27 |
2001:978:2:7::162:100 |
ipv4 149.13.75.27 ok; ipv6 2001:978:2:7::162:100 ok; |
mx4.mtaroutes.com [O] |
154.59.193.124 |
2001:978:2:6::f:124 |
ipv4 154.59.193.124 ok; ipv6 2001:978:2:6::f:124 ok; |
📌 Action item(s):
- Publish AAAA records for mail (MX): mail.telikom.com.pg.
Web
IPv4-only
[1] 0/0/0 [I]
Meaning: Shows IPv6 web endpoint readiness for the discovered HTTPS host. Operational means family-specific HTTPS requests complete successfully.
IPv4 1/1/1 · IPv6 0/0/0 · location I
| Host | IPv4 | IPv6 | Probes |
|---|
www.telikom.com.pg [I] |
124.240.221.35 |
— |
ipv4 ok; |
📌 Action item(s):
- Publish AAAA records for web host: www.telikom.com.pg.
DNSSEC
Unsigned
U/-/-
Meaning: Shows whether DNSKEY data is observed at the apex (signed), absent (unsigned), or unavailable due to lookup error.
Apex DNSKEY presence only — not full chain validation.
Analyze on DNSViz
📌 Action item(s):
- Enable DNSSEC signing and publish a DNSKEY at the apex. Use DNSViz to validate the full chain.
DMARC
p=quarantine, sp=none
p=quarantine, sp=none — published organizational policy. Ask receivers to quarantine failing mail; reject is stronger.
Meaning: Published DMARC policy at _dmarc.telikom.com.pg (DNS TXT). Shows organizational policy (p=) and subdomain policy (sp=) when set.
Record at _dmarc.telikom.com.pg:
v=DMARC1; p=quarantine; sp=none; rua=mailto:a.0iap7zd3@sdmarc.net,mailto:dmarc@telinet.com.pg; ruf=mailto:dmarc@telinet.com.pg; adkim=r; aspf=r
Policy publication only — SPF/DKIM not measured. Not part of the 0–4 row score.
Check on dmarcian
📌 Action item(s):
- Tighten DMARC toward p=reject when ready. Review on dmarcian.