IPv6 Addresses Detected
2600:9000:20af:7400:11:dff8:ffc0:93a1
2600:9000:20af:4800:11:dff8:ffc0:93a1
2600:9000:20af:6600:11:dff8:ffc0:93a1
2600:9000:20af:ca00:11:dff8:ffc0:93a1
2600:9000:20af:1600:11:dff8:ffc0:93a1
2600:9000:20af:a00:11:dff8:ffc0:93a1
2600:9000:20af:2e00:11:dff8:ffc0:93a1
2600:9000:20af:f600:11:dff8:ffc0:93a1
IPv4 Addresses Detected
210.19.116.31
210.19.115.31
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
- TT DOTCOM SDN BHD
- Country
- MY
- ASN
- AS9930 TTNET-MY - TIME dotCom Berhad No. 14, Jalan Majistret U1/26 Hicom Glenmarie Industrial Park 40150 Shah Alam Selangor, Malaysia, MY
- Network
- 210.19.0.0/16
Web Services
35%The domain has at least one IPv6 address (AAAA DNS record).
✓ 2600:9000:20af:7400:11:dff8:ffc0:93a1, 2600:9000:20af:4800:11:dff8:ffc0:93a1, 2600:9000:20af:6600:11:dff8:ffc0:93a1, 2600:9000:20af:ca00:11:dff8:ffc0:93a1, 2600:9000:20af:1600:11:dff8:ffc0:93a1, 2600:9000:20af:a00:11:dff8:ffc0:93a1, 2600:9000:20af:2e00:11:dff8:ffc0:93a1, 2600:9000:20af:f600:11:dff8:ffc0: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 — 84ms TTFB.
Website reachable on port 443 when connecting via IPv6.
✗ HTTPS is not accessible over IPv6.
Website responds when connected exclusively over IPv6, with no IPv4 fallback. Simulates what happens when IPv4 is turned off.
✗ Site is not reachable when limited to IPv6-only.
The SSL/TLS certificate is valid, not expired, and matches the domain when connected via IPv6.
✗ TLS certificate is invalid, expired, or hostname mismatch over IPv6.
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.
✗ No HTTP/3 support detected.
DNS & DNSSEC
25%At least one authoritative nameserver has an IPv6 address (AAAA record).
✗ No nameserver has an AAAA record.
Authoritative nameserver accepts TCP connections on port 53 over IPv6.
✗ No nameserver is reachable over IPv6.
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.
✗ No DMARC record found.
IPv4 Baseline
15%The domain has at least one IPv4 address (A DNS record).
✓ 210.19.116.31, 210.19.115.31
Website reachable on port 80 when connecting via IPv4.
✓ HTTP (port 80) responds over IPv4 — 311ms TTFB.
Website reachable on port 443 when connecting via IPv4.
✓ HTTPS (port 443) responds over IPv4 — 353ms 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 | 24.7 ms (p95: 34.57) | 16.98 ms (p95: 17.11) | -7.7 ms |
| IPv4 | 21.1 ms (p95: 44.23) | 34.37 ms (p95: 44.58) | +13.3 ms | |
| IPv6 | 31.81 ms (p95: 50.85) | 30.19 ms (p95: 37.31) | -1.6 ms | |
| Cloudflare | IPv4 | 19.14 ms (p95: 26.67) | 19.83 ms (p95: 24.62) | +0.7 ms |
| Cloudflare | IPv6 | 40.21 ms (p95: 44.07) | 13 ms (p95: 36.88) | -27.2 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.
9470e265-a45d-4cc7-a6e3-bbc87e678a50
Score History
Check History
Last 7 checks
| Date | Score | Status | Triggered By |
|---|---|---|---|
|
13 Jun 2026 00:48 UTC |
33 % | None | scheduled |
|
07 Mar 2026 01:00 UTC |
37 % | Partial | manual |
|
06 Mar 2026 18:55 UTC |
37 % | Partial | manual |
|
06 Mar 2026 17:42 UTC |
37 % | Partial | manual |
|
06 Mar 2026 17:16 UTC |
37 % | Partial | manual |
|
06 Mar 2026 11:18 UTC |
37 % | Partial | manual |
|
04 Mar 2026 03:03 UTC |
37 % | Partial | manual |