pfizer.com
Updated:
2023-05-25 23:22:44 UTC (545 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (5)
- pfizer.com/A
- pfizer.com/MX
- pfizer.com/NS
- pfizer.com/SOA
- pfizer.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 pfizer.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 pfizer.com
Secure (1)
- . to com
Notices
Errors (2)
- pfizer.com/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (108.59.161.15, 108.59.162.15, 108.59.163.15, 108.59.164.15, 2600:2000:2210::15, 2600:2000:2220::15, 2600:2000:2230::15, 2600:2000:2240::15, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
- pfizer.com/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (1)
- pfizer.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::15, 2600:2000:2220::15, 2600:2000:2230::15, 2600:2000:2240::15, UDP_-_EDNS0_4096_D_KN)
JavaScript is required to make the graph below interactive.
