t-mobile.com
Updated:
2024-07-29 20:20:48 UTC (51 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 (1)
- com/SOA
DNSKEY/DS/NSEC status
Secure (6)
- ./DNSKEY (alg 8, id 20038)
- ./DNSKEY (alg 8, id 20326)
- NSEC3 proving non-existence of t-mobile.com/DS
- com/DNSKEY (alg 13, id 19718)
- com/DNSKEY (alg 13, id 59354)
- com/DS (alg 13, id 19718)
Delegation status
Insecure (1)
- com to t-mobile.com
Secure (1)
- . to com
Notices
Errors (16)
- t-mobile.com zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (64.125.226.44, 64.125.228.105)
- t-mobile.com zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (64.125.226.44, 64.125.228.105)
- t-mobile.com/A: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (64.125.226.44, 64.125.228.105, UDP_-_EDNS0_4096_D_KN)
- t-mobile.com/DNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (64.125.226.44, 64.125.228.105, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- t-mobile.com/MX: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (64.125.226.44, 64.125.228.105, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- t-mobile.com/NS: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (64.125.226.44, 64.125.228.105, UDP_-_EDNS0_4096_D_KN)
- t-mobile.com/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (64.125.226.44, 64.125.228.105, TCP_-_EDNS0_4096_D_N)
- t-mobile.com/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (64.125.226.44, 64.125.228.105, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
- t-mobile.com/TXT: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (64.125.226.44, 64.125.228.105, UDP_-_EDNS0_4096_D_KN)
- t-mobile.com/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- t-mobile.com/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- t-mobile.com/CDNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- t-mobile.com/CDS has errors; select the "Denial of existence" DNSSEC option to see them.
- v6cny.h70wa.t-mobile.com/A has errors; select the "Denial of existence" DNSSEC option to see them.
- t-mobile.com/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
- t-mobile.com/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
- ./DNSKEY (alg 8, id 20038): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
- ./DNSKEY (alg 8, id 20326): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
- com/DS (alg 13, id 19718): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
- com/DS (alg 13, id 19718): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
JavaScript is required to make the graph below interactive.
