t-mobile.com
Updated:
2023-05-01 22:17:00 UTC (571 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 (6)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 60955)
- NSEC3 proving non-existence of t-mobile.com/DS
- com/DNSKEY (alg 8, id 30909)
- com/DNSKEY (alg 8, id 46551)
- com/DS (alg 8, id 30909)
Delegation status
Insecure (1)
- com to t-mobile.com
Secure (1)
- . to com
Notices
Errors (4)
- t-mobile.com/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (2607:fb90:c13e:fff0:4aa3:af08:0:aaaa, 2607:fb90:c13f:ffff:a255:5e9a:0:aaaa, UDP_-_EDNS0_512_D_KN)
- t-mobile.com/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (2607:fb90:c13e:fff0:4aa3:af08:0:aaaa, 2607:fb90:c13f:ffff:a255:5e9a:0:aaaa, UDP_-_EDNS0_512_D_KN)
- t-mobile.com/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (2607:fb90:c13e:fff0:4aa3:af08:0:aaaa, 2607:fb90:c13f:ffff:a255:5e9a:0:aaaa, TCP_-_EDNS0_4096_D_N)
- t-mobile.com/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
