View on GitHub

DNSViz: A DNS visualization tool

cyberthreat.id

Updated: 2024-03-14 15:46:50 UTC (269 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

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (6)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 30903)
  • cyberthreat.id/DS (alg 8, id 24997)
  • id/DNSKEY (alg 8, id 22449)
  • id/DNSKEY (alg 8, id 26887)
  • id/DS (alg 8, id 26887)
Non_existent (1)
  • cyberthreat.id/DNSKEY (alg 8, id 24997)

Delegation statusDelegation status

Bogus (1)
  • id to cyberthreat.id
Secure (1)
  • . to id

NoticesNotices

Errors (5)
  • cyberthreat.id zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (103.149.180.1, 103.149.180.2, 2001:df3:3580:d42::1, 2001:df3:3580:d42::2)
  • cyberthreat.id zone: There was an error resolving the following NS name(s) to address(es): nx1.ruangsiber.id, nx2.ruangsiber.id
  • cyberthreat.id/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (103.149.180.1, 103.149.180.2, 2001:df3:3580:d42::1, 2001:df3:3580:d42::2, UDP_-_NOEDNS_)
  • cyberthreat.id/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (103.149.180.1, 103.149.180.2, 2001:df3:3580:d42::1, 2001:df3:3580:d42::2, UDP_-_NOEDNS_)
  • id to cyberthreat.id: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11.

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