walgreens.com
Updated:
2022-12-04 17:00:19 UTC (719 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (5)
- walgreens.com/A
- walgreens.com/MX
- walgreens.com/NS
- walgreens.com/SOA
- walgreens.com/TXT
Secure (2)
- 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 walgreens.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 walgreens.com
Secure (1)
- . to com
Notices
Errors (3)
- walgreens.com zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (204.15.116.132)
- walgreens.com/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (204.15.116.132, UDP_-_NOEDNS_)
- walgreens.com/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (204.15.116.132, UDP_-_NOEDNS_)
Warnings (2)
- com to walgreens.com: The glue address(es) for ns7.walgreens.com (204.15.116.132) differed from its authoritative address(es) (204.15.119.56). See RFC 1034, Sec. 4.2.2.
- walgreens.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:1403:a::40, UDP_-_EDNS0_4096_D_KN)
JavaScript is required to make the graph below interactive.
