metlife.com
Updated:
2022-06-19 03:14:19 UTC (889 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (6)
- metlife.com/A
- metlife.com/MX
- metlife.com/NS
- metlife.com/NS
- metlife.com/SOA
- metlife.com/TXT
Secure (2)
- com/SOA
- com/SOA
DNSKEY/DS/NSEC status
Secure (6)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 47671)
- NSEC3 proving non-existence of metlife.com/DS
- com/DNSKEY (alg 8, id 30909)
- com/DNSKEY (alg 8, id 37269)
- com/DS (alg 8, id 30909)
Delegation status
Insecure (1)
- com to metlife.com
Secure (1)
- . to com
Notices
Errors (4)
- metlife.com zone: The following NS name(s) did not resolve to address(es): s1ns1.metlife.com, s2ns2.metlife.com, s3ns3.metlife.com, s4ns4.metlife.com
- metlife.com zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (209.164.208.172)
- metlife.com/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (209.164.208.172, UDP_-_NOEDNS_)
- metlife.com/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (209.164.208.172, UDP_-_NOEDNS_)
Warnings (2)
- com to metlife.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): ns3.metlife.com, s4ns4.metlife.com, s3ns3.metlife.com, s2ns2.metlife.com, s1ns1.metlife.com See RFC 1034, Sec. 4.2.2.
- com to metlife.com: The following NS name(s) were found in the delegation NS RRset (i.e., in the com zone), but not in the authoritative NS RRset: ns1.edgecastdns.net, ns2.edgecastdns.net, ns3.edgecastdns.net, ns4.edgecastdns.net See RFC 1034, Sec. 4.2.2.
JavaScript is required to make the graph below interactive.
