assurant.com
Updated:
2022-05-24 22:33:56 UTC (1294 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (5)
- assurant.com/A
- assurant.com/MX
- assurant.com/NS
- assurant.com/SOA
- assurant.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 assurant.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 assurant.com
Secure (1)
- . to com
Notices
Errors (3)
- assurant.com zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2604:b440:0:206::a, 2604:b440:1:24::a)
- assurant.com/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2604:b440:0:206::a, 2604:b440:1:24::a, UDP_-_NOEDNS_)
- assurant.com/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2604:b440:0:206::a, 2604:b440:1:24::a, UDP_-_NOEDNS_)
Warnings (2)
- com to assurant.com: Authoritative AAAA records exist for ns3.assurant.com, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- com to assurant.com: Authoritative AAAA records exist for ns4.assurant.com, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
JavaScript is required to make the graph below interactive.
