bp.com
Updated:
2022-11-06 19:04:52 UTC (748 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (5)
- bp.com/A
- bp.com/MX
- bp.com/NS
- bp.com/SOA
- bp.com/TXT
Secure (3)
- com/SOA
- com/SOA
- com/SOA
DNSKEY/DS/NSEC status
Secure (6)
- ./DNSKEY (alg 8, id 18733)
- ./DNSKEY (alg 8, id 20326)
- NSEC3 proving non-existence of bp.com/DS
- com/DNSKEY (alg 8, id 30909)
- com/DNSKEY (alg 8, id 53929)
- com/DS (alg 8, id 30909)
Delegation status
Insecure (1)
- com to bp.com
Secure (1)
- . to com
Notices
Warnings (3)
- bp.com/TXT: No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2600:2000:2210::8, 2600:2000:2220::8, 2600:2000:2230::8, 2600:2000:2240::8, UDP_-_EDNS0_4096_D_KN)
- com/DS (alg 8, id 30909): No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (193.0.14.129, UDP_-_EDNS0_4096_D_KN)
- com/DS (alg 8, id 30909): No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (193.0.14.129, UDP_-_EDNS0_4096_D_KN)
JavaScript is required to make the graph below interactive.
