Measurement estimates from a single vantage point — not a compliance certification. Guidance below is for operators, not an SLA.
DNS
Dual-stack
[4] 4/4/4 [O]
Meaning: Shows how many authoritative name servers exist, and how many IPv6 endpoints are configured, responsive, and operational.
IPv4 4/4/4 · IPv6 4/4/4 · location O
| Host | IPv4 | IPv6 | Probes |
ns-1563.awsdns-03.co.uk [O] |
205.251.198.27 |
2600:9000:5306:1b00::1 |
ipv4 205.251.198.27 ok; ipv6 2600:9000:5306:1b00::1 ok; |
ns-933.awsdns-52.net [O] |
205.251.195.165 |
2600:9000:5303:a500::1 |
ipv4 205.251.195.165 ok; ipv6 2600:9000:5303:a500::1 ok; |
ns-1437.awsdns-51.org [O] |
205.251.197.157 |
2600:9000:5305:9d00::1 |
ipv4 205.251.197.157 ok; ipv6 2600:9000:5305:9d00::1 ok; |
ns-288.awsdns-36.com [O] |
205.251.193.32 |
2600:9000:5301:2000::1 |
ipv4 205.251.193.32 ok; ipv6 2600:9000:5301:2000::1 ok; |
Mail
Dual-stack
[5 MX] v4 smtp 5/5/5 v6 smtp 5/5/5 [O]
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/5 · IPv6 5/5/5 · location O
| Host | IPv4 | IPv6 | Probes |
aspmx.l.google.com [O] |
192.179.26.26 |
2607:f8b0:400e:c05::1b |
ipv4 192.179.26.26 ok; ipv6 2607:f8b0:400e:c05::1b ok; |
aspmx2.googlemail.com [O] |
192.178.231.27 |
2607:f8b0:4023:200d::1b |
ipv4 192.178.231.27 ok; ipv6 2607:f8b0:4023:200d::1b ok; |
aspmx3.googlemail.com [O] |
172.217.216.26 |
2607:f8b0:4023:2803::1a |
ipv4 172.217.216.26 ok; ipv6 2607:f8b0:4023:2803::1a ok; |
alt2.aspmx.l.google.com [O] |
172.217.216.27 |
2607:f8b0:4023:2803::1b |
ipv4 172.217.216.27 ok; ipv6 2607:f8b0:4023:2803::1b ok; |
alt1.aspmx.l.google.com [O] |
192.178.231.27 |
2607:f8b0:4023:200d::1a |
ipv4 192.178.231.27 ok; ipv6 2607:f8b0:4023:200d::1a ok; |
Web
Dual-stack
[1] 8/8/8 [I]
Meaning: Shows IPv6 web endpoint readiness for the discovered HTTPS host. Operational means family-specific HTTPS requests complete successfully.
IPv4 4/4/4 · IPv6 8/8/8 · location I
| Host | IPv4 | IPv6 | Probes |
www.visittci.com [I] |
3.163.24.10, 3.163.24.38, 3.163.24.78, 3.163.24.43 |
2600:9000:260f:a800:5:e7e:a280:93a1, 2600:9000:260f:c00:5:e7e:a280:93a1, 2600:9000:260f:2a00:5:e7e:a280:93a1, 2600:9000:260f:f800:5:e7e:a280:93a1, 2600:9000:260f:d600:5:e7e:a280:93a1, 2600:9000:260f:ec00:5:e7e:a280:93a1, 2600:9000:260f:5200:5:e7e:a280:93a1, 2600:9000:260f:8c00:5:e7e:a280:93a1 |
ipv4 ok; ipv6 ok; |
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=none
p=none — published organizational policy. Monitoring only (receivers should not reject mail); tighten toward quarantine, then reject when ready. Not the same as missing DMARC.
Meaning: Published DMARC policy at _dmarc.visittci.com (DNS TXT). Shows organizational policy (p=) and subdomain policy (sp=) when set.
Record at _dmarc.visittci.com:
v=DMARC1; p=none;
Policy publication only — SPF/DKIM not measured. Not part of the 0–4 row score.
Check on dmarcian
📌 Action item(s):
- DMARC is monitoring-only (p=none). Move toward quarantine, then reject. Review on dmarcian.