View on GitHub

DNSViz: A DNS visualization tool

cargo24.lv

Updated: 2021-10-22 08:30:37 UTC (1157 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

Bogus (5)
  • cargo24.lv/A
  • cargo24.lv/MX
  • cargo24.lv/NS
  • cargo24.lv/SOA
  • cargo24.lv/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (6)
  • ./DNSKEY (alg 8, id 14748)
  • ./DNSKEY (alg 8, id 20326)
  • cargo24.lv/DS (alg 8, id 32092)
  • lv/DNSKEY (alg 8, id 31113)
  • lv/DNSKEY (alg 8, id 42018)
  • lv/DS (alg 8, id 42018)
Non_existent (1)
  • cargo24.lv/DNSKEY (alg 8, id 32092)

Delegation statusDelegation status

Bogus (1)
  • lv to cargo24.lv
Secure (1)
  • . to lv

NoticesNotices

Errors (12)
  • cargo24.lv/A: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (84.19.30.80, 194.135.93.138, 2a00:f70:abcd:102:2000:5555:1111:7cf, UDP_-_EDNS0_4096_D_KN)
  • cargo24.lv/MX: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (84.19.30.80, 194.135.93.138, 2a00:f70:abcd:102:2000:5555:1111:7cf, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • cargo24.lv/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (84.19.30.80, 194.135.93.138, 2a00:f70:abcd:102:2000:5555:1111:7cf, UDP_-_EDNS0_4096_D_KN)
  • cargo24.lv/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (84.19.30.80, 194.135.93.138, 2a00:f70:abcd:102:2000:5555:1111:7cf, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • cargo24.lv/TXT: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (84.19.30.80, 194.135.93.138, 2a00:f70:abcd:102:2000:5555:1111:7cf, UDP_-_EDNS0_4096_D_KN)
  • lv to cargo24.lv: 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. (84.19.30.80, 194.135.93.138, 2a00:f70:abcd:102:2000:5555:1111:7cf, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • lv to cargo24.lv: The DS RRset for the zone included algorithm 8 (RSASHA256), but no DS RR matched a DNSKEY with algorithm 8 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (84.19.30.80, 194.135.93.138, 2a00:f70:abcd:102:2000:5555:1111:7cf, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • cargo24.lv/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • bmt20pcw19.cargo24.lv/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • cargo24.lv/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • cargo24.lv/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
  • cargo24.lv/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (1)
  • lv to cargo24.lv: Authoritative AAAA records exist for ns1.items.lv, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.

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