View on GitHub

DNSViz: A DNS visualization tool

bssn.go.id

Updated: 2024-07-15 06:15:05 UTC (8 months 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)
  • bssn.go.id/A
  • bssn.go.id/MX
  • bssn.go.id/NS
  • bssn.go.id/NSEC3PARAM
  • bssn.go.id/SOA
  • bssn.go.id/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (15)
  • ./DNSKEY (alg 8, id 20038)
  • ./DNSKEY (alg 8, id 20326)
  • bssn.go.id/DNSKEY (alg 7, id 22779)
  • bssn.go.id/DNSKEY (alg 7, id 4838)
  • bssn.go.id/DS (alg 7, id 12639)
  • bssn.go.id/DS (alg 7, id 20931)
  • bssn.go.id/DS (alg 7, id 22779)
  • bssn.go.id/DS (alg 7, id 48675)
  • bssn.go.id/DS (alg 7, id 50775)
  • go.id/DNSKEY (alg 10, id 25427)
  • go.id/DNSKEY (alg 10, id 48051)
  • go.id/DS (alg 10, id 48051)
  • id/DNSKEY (alg 8, id 22449)
  • id/DNSKEY (alg 8, id 26887)
  • id/DS (alg 8, id 26887)
Non_existent (4)
  • bssn.go.id/DNSKEY (alg 7, id 12639)
  • bssn.go.id/DNSKEY (alg 7, id 20931)
  • bssn.go.id/DNSKEY (alg 7, id 48675)
  • bssn.go.id/DNSKEY (alg 7, id 50775)

Delegation statusDelegation status

Secure (3)
  • . to id
  • go.id to bssn.go.id
  • id to go.id

NoticesNotices

Errors (7)
  • go.id zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2402:ee80:b::b, 2402:ee80:c::c)
  • id zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2402:ee80:b::b, 2402:ee80:c::c)
  • bssn.go.id/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • bssn.go.id/CDNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • bssn.go.id/CDS has errors; select the "Denial of existence" DNSSEC option to see them.
  • ndsrw.5b8ot.bssn.go.id/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • bssn.go.id/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (36)
  • RRSIG bssn.go.id/A alg 7, id 4838: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG bssn.go.id/DNSKEY alg 7, id 22779: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG bssn.go.id/DNSKEY alg 7, id 22779: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG bssn.go.id/DNSKEY alg 7, id 4838: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG bssn.go.id/DNSKEY alg 7, id 4838: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG bssn.go.id/DS alg 10, id 25427: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG bssn.go.id/DS alg 10, id 25427: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG bssn.go.id/DS alg 10, id 25427: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG bssn.go.id/DS alg 10, id 25427: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG bssn.go.id/DS alg 10, id 25427: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG bssn.go.id/MX alg 7, id 4838: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG bssn.go.id/NS alg 7, id 4838: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG bssn.go.id/NSEC3PARAM alg 7, id 4838: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG bssn.go.id/SOA alg 7, id 4838: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG bssn.go.id/TXT alg 7, id 4838: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG go.id/DNSKEY alg 10, id 25427: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG go.id/DNSKEY alg 10, id 25427: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG go.id/DNSKEY alg 10, id 48051: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG go.id/DNSKEY alg 10, id 48051: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • bssn.go.id/DS (alg 7, id 12639): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • bssn.go.id/DS (alg 7, id 12639): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • bssn.go.id/DS (alg 7, id 20931): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • bssn.go.id/DS (alg 7, id 20931): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • bssn.go.id/DS (alg 7, id 22779): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • bssn.go.id/DS (alg 7, id 22779): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • bssn.go.id/DS (alg 7, id 48675): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • bssn.go.id/DS (alg 7, id 48675): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • bssn.go.id/DS (alg 7, id 50775): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • bssn.go.id/DS (alg 7, id 50775): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • bssn.go.id/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • bssn.go.id/CDNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • bssn.go.id/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • bssn.go.id/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
  • bssn.go.id/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • bssn.go.id/CDS has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ndsrw.5b8ot.bssn.go.id/A 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