samhsa.gov
Updated:
2023-04-06 11:50:12 UTC (598 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- samhsa.gov/A
- samhsa.gov/AAAA
- samhsa.gov/MX
- samhsa.gov/NS
- samhsa.gov/SOA
- samhsa.gov/TXT
DNSKEY/DS/NSEC status
Secure (12)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 60955)
- ./DNSKEY (alg 8, id 951)
- gov/DNSKEY (alg 8, id 24250)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- samhsa.gov/DNSKEY (alg 8, id 26761)
- samhsa.gov/DNSKEY (alg 8, id 35998)
- samhsa.gov/DNSKEY (alg 8, id 56684)
- samhsa.gov/DNSKEY (alg 8, id 58264)
- samhsa.gov/DS (alg 8, id 56684)
- samhsa.gov/DS (alg 8, id 58264)
Delegation status
Secure (2)
- . to gov
- gov to samhsa.gov
Notices
Errors (4)
- samhsa.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2607:f220:0:1::2a, 2607:f220:0:1::2b, 2607:f220:0:1::2c, 2607:f220:0:1::2d)
- samhsa.gov/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2607:f220:0:1::2a, 2607:f220:0:1::2b, 2607:f220:0:1::2c, 2607:f220:0:1::2d, UDP_-_NOEDNS_)
- samhsa.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2607:f220:0:1::2a, 2607:f220:0:1::2b, 2607:f220:0:1::2c, 2607:f220:0:1::2d, UDP_-_NOEDNS_)
- bzoktgusrv.samhsa.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
