View on GitHub

DNSViz: A DNS visualization tool

amberalert.gov

Updated: 2024-02-28 11:24:42 UTC (267 days ago) Update now
« Previous analysis | Next analysis »
DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Secure (6)
  • amberalert.gov/A
  • amberalert.gov/AAAA
  • amberalert.gov/NS
  • amberalert.gov/NSEC3PARAM
  • amberalert.gov/SOA
  • amberalert.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (12)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 30903)
  • amberalert.gov/DNSKEY (alg 8, id 40732)
  • amberalert.gov/DNSKEY (alg 8, id 53223)
  • amberalert.gov/DNSKEY (alg 8, id 61704)
  • amberalert.gov/DNSKEY (alg 8, id 62155)
  • amberalert.gov/DS (alg 8, id 40732)
  • amberalert.gov/DS (alg 8, id 40732)
  • gov/DNSKEY (alg 8, id 10104)
  • gov/DNSKEY (alg 8, id 49735)
  • gov/DNSKEY (alg 8, id 64280)
  • gov/DS (alg 8, id 64280)

Delegation statusDelegation status

Secure (2)
  • . to gov
  • gov to amberalert.gov

NoticesNotices

Errors (9)
  • amberalert.gov zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (2607:f330:5000:107f::86)
  • amberalert.gov/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2607:f330:5000:107f::86, UDP_-_EDNS0_4096_D_KN)
  • amberalert.gov/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (2607:f330:5000:107f::86, UDP_-_EDNS0_512_D_KN)
  • amberalert.gov/NSEC3PARAM: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2607:f330:5000:107f::86, UDP_-_NOEDNS_)
  • amberalert.gov/SOA: No response was received from the server over TCP (tried 4 times). See RFC 1035, Sec. 4.2. (2607:f330:5000:107f::86, TCP_-_EDNS0_4096_D_N)
  • amberalert.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • amberalert.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • l98zfnj2ix.amberalert.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • amberalert.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (7)
  • amberalert.gov/DS (alg 8, id 40732): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • amberalert.gov/DS (alg 8, id 40732): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • amberalert.gov/DS (alg 8, id 40732): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
  • amberalert.gov/DS (alg 8, id 40732): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
  • amberalert.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
  • l98zfnj2ix.amberalert.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • amberalert.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.

DNSKEY legend

Full legend
SEP bit setSEP bit set
Revoke bit setRevoke bit set
Trust anchorTrust anchor
Download: png | svg
Warning JavaScript is required to make the graph below interactive.
DNSSEC authentication graph