View on GitHub

DNSViz: A DNS visualization tool

admin.inkmail.eu

Updated: 2024-03-01 15:09:09 UTC (249 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

Insecure (4)
  • admin.inkmail.eu/A (NXDOMAIN)
  • admin.inkmail.eu/CNAME
  • inkmail.eu/SOA
  • ns.inkmail.eu/A
Secure (2)
  • eu/SOA
  • eu/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Insecure (3)
  • NSEC3 proving non-existence of admin.inkmail.eu/A
  • inkmail.eu/DNSKEY (alg 8, id 41013)
  • inkmail.eu/DNSKEY (alg 8, id 8930)
Secure (6)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 30903)
  • NSEC3 proving non-existence of inkmail.eu/DS
  • eu/DNSKEY (alg 8, id 35926)
  • eu/DNSKEY (alg 8, id 47148)
  • eu/DS (alg 8, id 35926)

Delegation statusDelegation status

Insecure (1)
  • eu to inkmail.eu
Secure (1)
  • . to eu

NoticesNotices

Errors (10)
  • NSEC3 proving non-existence of admin.inkmail.eu/A: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of admin.inkmail.eu/A: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of admin.inkmail.eu/A: The following queries resulted in an answer response, even though the NSEC3 records indicate that the queried names don't exist: admin.inkmail.eu/CNAME See RFC 5155, Sec. 8.4.
  • NSEC3 proving non-existence of admin.inkmail.eu/A: The following queries resulted in an answer response, even though the NSEC3 records indicate that the queried names don't exist: admin.inkmail.eu/CNAME See RFC 5155, Sec. 8.4.
  • admin.inkmail.eu/CNAME: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (89.159.178.163, UDP_-_EDNS0_4096_D_KN)
  • eu zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:978:2:1::93:2)
  • inkmail.eu/DNSKEY (alg 8, id 41013): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (89.159.178.163, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • ns.inkmail.eu/A: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (89.159.178.163, UDP_-_EDNS0_4096_D_KN)
  • inkmail.eu/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • admin.inkmail.eu/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (5)
  • NSEC3 proving non-existence of admin.inkmail.eu/A: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of admin.inkmail.eu/A: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • inkmail.eu/DNSKEY (alg 8, id 8930): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (89.159.178.163, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • inkmail.eu/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • admin.inkmail.eu/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