View on GitHub

DNSViz: A DNS visualization tool

usembassy.gov

« Previous analysis | Next analysis »
DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Bogus (5)
  • usembassy.gov/A
  • usembassy.gov/AAAA
  • usembassy.gov/NS
  • usembassy.gov/SOA
  • usembassy.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (11)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26116)
  • gov/DNSKEY (alg 8, id 15489)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • usembassy.gov/DNSKEY (alg 8, id 11080)
  • usembassy.gov/DNSKEY (alg 8, id 1129)
  • usembassy.gov/DNSKEY (alg 8, id 21715)
  • usembassy.gov/DS (alg 8, id 11080)
  • usembassy.gov/DS (alg 8, id 11080)

Delegation statusDelegation status

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

NoticesNotices

Errors (8)
  • RRSIG usembassy.gov/A alg 8, id 21715: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • RRSIG usembassy.gov/AAAA alg 8, id 21715: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • RRSIG usembassy.gov/NS alg 8, id 21715: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • RRSIG usembassy.gov/SOA alg 8, id 21715: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • RRSIG usembassy.gov/TXT alg 8, id 21715: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • usembassy.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • jme16xhacb.usembassy.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • usembassy.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (11)
  • gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • gov/DS (alg 8, id 7698): 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.
  • gov/DS (alg 8, id 7698): 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.
  • usembassy.gov/DS (alg 8, id 11080): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • usembassy.gov/DS (alg 8, id 11080): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • usembassy.gov/DS (alg 8, id 11080): 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.
  • usembassy.gov/DS (alg 8, id 11080): 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.
  • usembassy.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • jme16xhacb.usembassy.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • usembassy.gov/MX 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