exxonmobil.com
Updated:
2024-12-11 23:09:46 UTC (16 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (5)
- exxonmobil.com/A
- exxonmobil.com/MX
- exxonmobil.com/NS
- exxonmobil.com/SOA
- exxonmobil.com/TXT
Secure (2)
- com/SOA
- com/SOA
DNSKEY/DS/NSEC status
Secure (6)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 61050)
- NSEC3 proving non-existence of exxonmobil.com/DS
- com/DNSKEY (alg 13, id 19718)
- com/DNSKEY (alg 13, id 29942)
- com/DS (alg 13, id 19718)
Delegation status
Insecure (1)
- com to exxonmobil.com
Secure (1)
- . to com
Notices
Warnings (3)
- com to exxonmobil.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): use6.akam.net, ns2-67.akam.net See RFC 1034, Sec. 4.2.2.
- com to exxonmobil.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: a13-67.akam.net, a3-66.akam.net See RFC 1034, Sec. 4.2.2.
- exxonmobil.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:1480:800::43, UDP_-_EDNS0_4096_D_KN)
JavaScript is required to make the graph below interactive.
