View on GitHub

DNSViz: A DNS visualization tool

buymy.coffee

Updated: 2022-04-11 17:00:31 UTC (3 years 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

Secure (1)
  • coffee/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (7)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 47671)
  • NSEC3 proving non-existence of buymy.coffee/DS
  • coffee/DNSKEY (alg 8, id 32658)
  • coffee/DNSKEY (alg 8, id 35448)
  • coffee/DNSKEY (alg 8, id 37636)
  • coffee/DS (alg 8, id 37636)

Delegation statusDelegation status

Lame (1)
  • coffee to buymy.coffee
Secure (1)
  • . to coffee

NoticesNotices

Errors (17)
  • NSEC3 proving non-existence of buymy.coffee/DS: 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 buymy.coffee/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • buymy.coffee zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (205.251.192.128, 205.251.194.206, 205.251.197.30, 205.251.198.65, 2600:9000:5300:8000::1, 2600:9000:5302:ce00::1, 2600:9000:5305:1e00::1, 2600:9000:5306:4100::1)
  • buymy.coffee zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (205.251.192.128, 205.251.194.206, 205.251.197.30, 205.251.198.65, 2600:9000:5300:8000::1, 2600:9000:5302:ce00::1, 2600:9000:5305:1e00::1, 2600:9000:5306:4100::1)
  • buymy.coffee/A: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (205.251.192.128, 205.251.194.206, 205.251.197.30, 205.251.198.65, 2600:9000:5300:8000::1, 2600:9000:5302:ce00::1, 2600:9000:5305:1e00::1, 2600:9000:5306:4100::1, UDP_-_EDNS0_4096_D_KN)
  • buymy.coffee/AAAA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (205.251.192.128, 205.251.194.206, 205.251.197.30, 205.251.198.65, 2600:9000:5300:8000::1, 2600:9000:5302:ce00::1, 2600:9000:5305:1e00::1, 2600:9000:5306:4100::1, UDP_-_EDNS0_4096_D_KN)
  • buymy.coffee/DNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (205.251.192.128, 205.251.194.206, 205.251.197.30, 205.251.198.65, 2600:9000:5300:8000::1, 2600:9000:5302:ce00::1, 2600:9000:5305:1e00::1, 2600:9000:5306:4100::1, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • buymy.coffee/MX: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (205.251.192.128, 205.251.194.206, 205.251.197.30, 205.251.198.65, 2600:9000:5300:8000::1, 2600:9000:5302:ce00::1, 2600:9000:5305:1e00::1, 2600:9000:5306:4100::1, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • buymy.coffee/NS: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (205.251.192.128, 205.251.194.206, 205.251.197.30, 205.251.198.65, 2600:9000:5300:8000::1, 2600:9000:5302:ce00::1, 2600:9000:5305:1e00::1, 2600:9000:5306:4100::1, UDP_-_EDNS0_4096_D_KN)
  • buymy.coffee/NSEC3PARAM: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (205.251.192.128, 205.251.194.206, 205.251.197.30, 205.251.198.65, 2600:9000:5300:8000::1, 2600:9000:5302:ce00::1, 2600:9000:5305:1e00::1, 2600:9000:5306:4100::1, UDP_-_EDNS0_4096_D_KN)
  • buymy.coffee/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (205.251.192.128, 205.251.194.206, 205.251.197.30, 205.251.198.65, 2600:9000:5300:8000::1, 2600:9000:5302:ce00::1, 2600:9000:5305:1e00::1, 2600:9000:5306:4100::1, TCP_-_EDNS0_4096_D_N)
  • buymy.coffee/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (205.251.192.128, 205.251.194.206, 205.251.197.30, 205.251.198.65, 2600:9000:5300:8000::1, 2600:9000:5302:ce00::1, 2600:9000:5305:1e00::1, 2600:9000:5306:4100::1, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • buymy.coffee/TXT: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (205.251.192.128, 205.251.194.206, 205.251.197.30, 205.251.198.65, 2600:9000:5300:8000::1, 2600:9000:5302:ce00::1, 2600:9000:5305:1e00::1, 2600:9000:5306:4100::1, UDP_-_EDNS0_4096_D_KN)
  • buymy.coffee/DS has errors; select the "Denial of existence" DNSSEC option to see them.
  • q5ju1aensm.buymy.coffee/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • buymy.coffee/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • buymy.coffee/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (3)
  • NSEC3 proving non-existence of buymy.coffee/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of buymy.coffee/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • buymy.coffee/DS 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