pagerduty.com
Updated:
2023-07-10 21:13:35 UTC (502 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (5)
- pagerduty.com/A
- pagerduty.com/MX
- pagerduty.com/NS
- pagerduty.com/SOA
- pagerduty.com/TXT
DNSKEY/DS/NSEC status
Secure (11)
- ./DNSKEY (alg 8, id 11019)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 60955)
- com/DNSKEY (alg 8, id 30909)
- com/DNSKEY (alg 8, id 4459)
- com/DNSKEY (alg 8, id 46551)
- com/DS (alg 8, id 30909)
- pagerduty.com/DNSKEY (alg 13, id 29866)
- pagerduty.com/DNSKEY (alg 13, id 43455)
- pagerduty.com/DNSKEY (alg 13, id 54211)
- pagerduty.com/DS (alg 13, id 54211)
Delegation status
Secure (2)
- . to com
- com to pagerduty.com
Notices
Warnings (5)
- ./DNSKEY (alg 8, id 11019): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:200::b, UDP_-_EDNS0_4096_D_KN)
- ./DNSKEY (alg 8, id 20326): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:200::b, UDP_-_EDNS0_4096_D_KN)
- ./DNSKEY (alg 8, id 60955): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:200::b, UDP_-_EDNS0_4096_D_KN)
- ./DNSKEY: The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:200::b, UDP_-_EDNS0_512_D_KN)
- com to pagerduty.com: Authoritative AAAA records exist for ns-474.awsdns-59.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.
