IPv6 Addresses Detected
2600:9000:20db:7400:2:b8f0:1d00:93a1
2600:9000:20db:7a00:2:b8f0:1d00:93a1
2600:9000:20db:e600:2:b8f0:1d00:93a1
2600:9000:20db:2800:2:b8f0:1d00:93a1
2600:9000:20db:1e00:2:b8f0:1d00:93a1
2600:9000:20db:b800:2:b8f0:1d00:93a1
2600:9000:20db:6600:2:b8f0:1d00:93a1
2600:9000:20db:7000:2:b8f0:1d00:93a1
IPv4 Addresses Detected
18.65.135.12
18.65.135.24
18.65.135.91
18.65.135.71
Network Information
WHOISIPv6 Network
- Organization
- Amazon.com, Inc.
- Country
- US
- ASN
- AS16509 AMAZON-02 - Amazon.com, Inc., US
- Network
- 2600:9000::/28
IPv4 Network
- Organization
- Amazon.com, Inc.
- Country
- US
- ASN
- AS16509 AMAZON-02 - Amazon.com, Inc., US
- Network
- 18.64.0.0/14
Web Services
35%The domain has at least one IPv6 address (AAAA DNS record).
✓ 2600:9000:20db:7400:2:b8f0:1d00:93a1, 2600:9000:20db:7a00:2:b8f0:1d00:93a1, 2600:9000:20db:e600:2:b8f0:1d00:93a1, 2600:9000:20db:2800:2:b8f0:1d00:93a1, 2600:9000:20db:1e00:2:b8f0:1d00:93a1, 2600:9000:20db:b800:2:b8f0:1d00:93a1, 2600:9000:20db:6600:2:b8f0:1d00:93a1, 2600:9000:20db:7000:2:b8f0:1d00:93a1
The IPv6 addresses are publicly routable — not link-local, ULA, loopback or documentation ranges.
✓ All addresses are globally routable.
Website reachable on port 80 when connecting via IPv6.
✓ HTTP (port 80) responds over IPv6 — 151ms TTFB.
Website reachable on port 443 when connecting via IPv6.
✓ HTTPS (port 443) responds over IPv6 — 110ms TTFB.
Website responds when connected exclusively over IPv6, with no IPv4 fallback. Simulates what happens when IPv4 is turned off.
✓ Site is fully reachable via IPv6-only.
The SSL/TLS certificate is valid, not expired, and matches the domain when connected via IPv6.
✓ Certificate valid — issued by C = US, O = "DigiCert, Inc.", CN = DigiCert Secure Site OV G2 TLS CN RSA4096 SHA256 2022 CA1, expires Nov 7 23:59:59 2026 GMT
The domain has both A and AAAA records for backwards compatibility during the IPv6 transition.
✓ Domain has both A and AAAA records.
Server advertises HTTP/3 support via the Alt-Svc: h3 header.
✓ Alt-Svc: h3 header detected.
DNS & DNSSEC
25%At least one authoritative nameserver has an IPv6 address (AAAA record).
✓ Nameserver has IPv6 address.
Authoritative nameserver accepts TCP connections on port 53 over IPv6.
✓ Nameserver is reachable via IPv6 on port 53.
Nameserver actually resolves DNS queries when asked over IPv6 — not just TCP open, but functionally answering.
✗ Nameserver does not answer queries over IPv6.
Full DNSSEC chain-of-trust validation passes. Prevents DNS cache poisoning and spoofing.
✗ DNSSEC validation failed or zone is unsigned.
A PTR record exists in ip6.arpa for the IPv6 address. Important for email delivery and network diagnostics.
✗ No PTR record found.
Delegation Signer record exists in the parent zone.
✗ No DS record at parent.
RRSIG signatures are present and not expired.
✗ No valid RRSIG found.
The cryptographic algorithm used for DNSSEC signing.
No DNSKEY record found.
Email Services
25%The domain has at least one MX (Mail Exchange) DNS record pointing to a mail server.
✗ No MX record found in DNS.
The highest-priority MX server resolves to an IPv6 address (AAAA record).
✗ MX server has no IPv6 address.
The MX server accepts SMTP connections (port 25) over IPv6 and responds with a 220 banner.
✗ SMTP is not reachable over IPv6.
The MX server supports STARTTLS encryption when connected over IPv6.
✗ STARTTLS not available over IPv6.
A TXT record with v=spf1 exists, declaring which servers may send email for this domain.
✗ No SPF record found.
A DKIM public key is published at a common selector, enabling email signature verification.
No common DKIM selector found.
A DMARC policy record exists at _dmarc.<domain>, enabling email authentication reporting.
✓ DMARC record found.
IPv4 Baseline
15%The domain has at least one IPv4 address (A DNS record).
✓ 18.65.135.12, 18.65.135.24, 18.65.135.91, 18.65.135.71
Website reachable on port 80 when connecting via IPv4.
✓ HTTP (port 80) responds over IPv4 — 107ms TTFB.
Website reachable on port 443 when connecting via IPv4.
✓ HTTPS (port 443) responds over IPv4 — 80ms TTFB.
DNS Resolution Performance
Comparison of A (IPv4) vs AAAA (IPv6) query times across resolvers and transports. Shows median (p50) of 3 samples.
| Resolver | Transport | A (IPv4) | AAAA (IPv6) | Delta |
|---|---|---|---|---|
| System | Default | 17.97 ms (p95: 27.76) | 18.22 ms (p95: 18.49) | +0.3 ms |
| IPv4 | 56.34 ms (p95: 69.97) | 43.62 ms (p95: 47.87) | -12.7 ms | |
| IPv6 | 60.33 ms (p95: 82.06) | 1037.02 ms (p95: 1086.49) | +976.7 ms | |
| Cloudflare | IPv4 | 21.91 ms (p95: 37.08) | 22.68 ms (p95: 29.05) | +0.8 ms |
| Cloudflare | IPv6 | 21.29 ms (p95: 34.14) | 20.24 ms (p95: 25.47) | -1.1 ms |
This result is backed by an HMAC-SHA256 signed evidence record. Scan the code or follow the link to verify the audit trail independently.
93b23b56-7ba2-4a10-a449-6618637b62c6
Score History
Check History
Last 3 checks
| Date | Score | Status | Triggered By |
|---|---|---|---|
|
13 Jun 2026 01:05 UTC |
64 % | Partial | scheduled |
|
07 Mar 2026 01:16 UTC |
64 % | Partial | manual |
|
06 Mar 2026 19:10 UTC |
64 % | Partial | manual |