View on GitHub

DNSViz: A DNS visualization tool

jit.cloud

« 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 (5)
  • jit.cloud/A
  • jit.cloud/MX
  • jit.cloud/NS
  • jit.cloud/SOA
  • jit.cloud/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (12)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 30903)
  • cloud/DNSKEY (alg 8, id 37675)
  • cloud/DNSKEY (alg 8, id 48499)
  • cloud/DS (alg 8, id 48499)
  • jit.cloud/DNSKEY (alg 5, id 29196)
  • jit.cloud/DNSKEY (alg 5, id 47914)
  • jit.cloud/DNSKEY (alg 8, id 19009)
  • jit.cloud/DNSKEY (alg 8, id 63697)
  • jit.cloud/DS (alg 5, id 47914)
  • jit.cloud/DS (alg 8, id 63697)
  • jit.cloud/DS (alg 8, id 63697)

Delegation statusDelegation status

Secure (2)
  • . to cloud
  • cloud to jit.cloud

NoticesNotices

Errors (14)
  • RRSIG jit.cloud/DNSKEY alg 5, id 29196: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • RRSIG jit.cloud/DNSKEY alg 5, id 29196: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • RRSIG jit.cloud/DNSKEY alg 5, id 29196: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • RRSIG jit.cloud/DNSKEY alg 5, id 29196: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • RRSIG jit.cloud/DNSKEY alg 5, id 47914: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • RRSIG jit.cloud/DNSKEY alg 5, id 47914: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • RRSIG jit.cloud/DNSKEY alg 5, id 47914: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • RRSIG jit.cloud/DNSKEY alg 5, id 47914: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • RRSIG jit.cloud/SOA alg 5, id 29196: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • jit.cloud/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
  • xrequfs10h.jit.cloud/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • jit.cloud/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • jit.cloud/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • jit.cloud/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (26)
  • RRSIG jit.cloud/A alg 5, id 29196: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG jit.cloud/DNSKEY alg 5, id 29196: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG jit.cloud/DNSKEY alg 5, id 29196: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG jit.cloud/DNSKEY alg 5, id 29196: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG jit.cloud/DNSKEY alg 5, id 29196: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG jit.cloud/DNSKEY alg 5, id 47914: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG jit.cloud/DNSKEY alg 5, id 47914: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG jit.cloud/DNSKEY alg 5, id 47914: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG jit.cloud/DNSKEY alg 5, id 47914: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG jit.cloud/MX alg 5, id 29196: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG jit.cloud/NS alg 5, id 29196: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG jit.cloud/SOA alg 5, id 29196: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG jit.cloud/TXT alg 5, id 29196: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • jit.cloud/DS (alg 5, id 47914): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • jit.cloud/DS (alg 5, id 47914): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • jit.cloud/DS (alg 5, id 47914): 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.
  • jit.cloud/DS (alg 5, id 47914): 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.
  • jit.cloud/DS (alg 8, id 63697): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • jit.cloud/DS (alg 8, id 63697): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • jit.cloud/DS (alg 8, id 63697): 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.
  • jit.cloud/DS (alg 8, id 63697): 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.
  • jit.cloud/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
  • xrequfs10h.jit.cloud/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • jit.cloud/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • jit.cloud/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • jit.cloud/AAAA 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