t-mobile.com
Updated:
2025-12-11 07:17:54 UTC (58 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (5)
- t-mobile.com/A
- t-mobile.com/MX
- t-mobile.com/NS
- t-mobile.com/SOA
- t-mobile.com/TXT
Secure (2)
- com/SOA
- com/SOA
DNSKEY/DS/NSEC status
Secure (7)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 38696)
- ./DNSKEY (alg 8, id 61809)
- NSEC3 proving non-existence of t-mobile.com/DS
- com/DNSKEY (alg 13, id 19718)
- com/DNSKEY (alg 13, id 46539)
- com/DS (alg 13, id 19718)
Delegation status
Insecure (1)
- com to t-mobile.com
Secure (1)
- . to com
Notices
Errors (3)
- t-mobile.com zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:550:1:a::d, 2001:550:1:b::d)
- t-mobile.com/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:550:1:a::d, 2001:550:1:b::d, UDP_-_NOEDNS_)
- t-mobile.com/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:550:1:a::d, 2001:550:1:b::d, UDP_-_NOEDNS_)
Warnings (2)
- com to t-mobile.com: Authoritative AAAA records exist for auth2.dns.cogentco.com, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- com to t-mobile.com: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the com zone): ns10.tmobileus.com, ns10.tmobileus.net See RFC 1034, Sec. 4.2.2.
JavaScript is required to make the graph below interactive.
