View on GitHub

DNSViz: A DNS visualization tool

1xbet.com.lr

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

RRset statusRRset status

Insecure (3)
  • 1xbet.com.lr/A
  • 1xbet.com.lr/NS
  • 1xbet.com.lr/SOA
Secure (1)
  • lr/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (7)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 5613)
  • NSEC proving non-existence of 1xbet.com.lr/DS
  • lr/DNSKEY (alg 8, id 23689)
  • lr/DNSKEY (alg 8, id 29984)
  • lr/DNSKEY (alg 8, id 42940)
  • lr/DS (alg 8, id 29984)

Delegation statusDelegation status

Insecure (1)
  • lr to 1xbet.com.lr
Secure (1)
  • . to lr

NoticesNotices

Errors (4)
  • RRSIG lr/DNSKEY alg 8, id 29984: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • RRSIG lr/DNSKEY alg 8, id 29984: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • RRSIG lr/DNSKEY alg 8, id 29984: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • lr/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (147.28.0.39, UDP_-_EDNS0_512_D_KN)

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