View on GitHub

DNSViz: A DNS visualization tool

tokisakigalaxy.xyz

Updated: 2020-10-17 14:32:11 UTC (4 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

Bogus (7)
  • cdn.tokisakigalaxy.xyz/A
  • cdn.tokisakigalaxy.xyz/A
  • tokisakigalaxy.xyz/A
  • tokisakigalaxy.xyz/A
  • tokisakigalaxy.xyz/MX
  • tokisakigalaxy.xyz/SOA
  • tokisakigalaxy.xyz/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (8)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26116)
  • tokisakigalaxy.xyz/DS (alg 13, id 2371)
  • xyz/DNSKEY (alg 8, id 30778)
  • xyz/DNSKEY (alg 8, id 3599)
  • xyz/DNSKEY (alg 8, id 61366)
  • xyz/DS (alg 8, id 3599)
  • xyz/DS (alg 8, id 3599)
Non_existent (1)
  • tokisakigalaxy.xyz/DNSKEY (alg 13, id 2371)

Delegation statusDelegation status

Bogus (1)
  • xyz to tokisakigalaxy.xyz
Secure (1)
  • . to xyz

NoticesNotices

Errors (18)
  • cdn.tokisakigalaxy.xyz/A: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (58.247.212.36, 101.226.220.16, 129.211.176.187, 183.192.201.90, UDP_-_EDNS0_4096_D_K)
  • cdn.tokisakigalaxy.xyz/A: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (58.247.212.48, 61.151.180.44, 129.211.176.224, 162.14.24.230, 162.14.25.230, 183.192.164.117, UDP_-_EDNS0_4096_D_K)
  • tokisakigalaxy.xyz zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (101.226.220.16, 183.192.201.90)
  • tokisakigalaxy.xyz/A: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (58.247.212.36, 58.247.212.48, 129.211.176.224, 183.192.201.90, UDP_-_EDNS0_4096_D_K)
  • tokisakigalaxy.xyz/A: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (61.151.180.44, 101.226.220.16, 129.211.176.187, 162.14.24.230, 162.14.25.230, 183.192.164.117, UDP_-_EDNS0_4096_D_K)
  • tokisakigalaxy.xyz/MX: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (58.247.212.36, 58.247.212.48, 61.151.180.44, 101.226.220.16, 129.211.176.187, 129.211.176.224, 162.14.24.230, 162.14.25.230, 183.192.164.117, 183.192.201.90, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • tokisakigalaxy.xyz/SOA: DNSSEC was effectively downgraded because the response had an invalid RCODE (FORMERR) with EDNS enabled. See RFC 6891, Sec. 7, RFC 2671, Sec. 5.3. (58.247.212.36, 61.151.180.44, UDP_-_EDNS0_4096_D)
  • tokisakigalaxy.xyz/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (58.247.212.36, 58.247.212.48, 61.151.180.44, 101.226.220.16, 129.211.176.187, 129.211.176.224, 162.14.24.230, 162.14.25.230, 183.192.164.117, 183.192.201.90, TCP_-_EDNS0_4096_D, UDP_-_EDNS0_4096_D, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
  • tokisakigalaxy.xyz/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (101.226.220.16, 183.192.201.90, TCP_-_EDNS0_4096_D)
  • tokisakigalaxy.xyz/SOA: The response had an invalid RCODE (FORMERR) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (58.247.212.36, 61.151.180.44, UDP_-_EDNS0_4096_D_K)
  • tokisakigalaxy.xyz/TXT: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (58.247.212.36, 58.247.212.48, 61.151.180.44, 101.226.220.16, 129.211.176.187, 129.211.176.224, 162.14.24.230, 162.14.25.230, 183.192.164.117, 183.192.201.90, UDP_-_EDNS0_4096_D_K)
  • xyz to tokisakigalaxy.xyz: 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. (58.247.212.36, 58.247.212.48, 61.151.180.44, 101.226.220.16, 129.211.176.187, 129.211.176.224, 162.14.24.230, 162.14.25.230, 183.192.164.117, 183.192.201.90, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • xyz to tokisakigalaxy.xyz: The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no DS RR matched a DNSKEY with algorithm 13 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (58.247.212.36, 58.247.212.48, 61.151.180.44, 101.226.220.16, 129.211.176.187, 129.211.176.224, 162.14.24.230, 162.14.25.230, 183.192.164.117, 183.192.201.90, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • tokisakigalaxy.xyz/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • tokisakigalaxy.xyz/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • os8l3q495f.tokisakigalaxy.xyz/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • tokisakigalaxy.xyz/NS has errors; select the "Denial of existence" DNSSEC option to see them.
  • tokisakigalaxy.xyz/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (10)
  • tokisakigalaxy.xyz/SOA: No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (58.247.212.48, 129.211.176.187, 129.211.176.224, 162.14.24.230, 162.14.25.230, UDP_-_EDNS0_4096_D_K)
  • tokisakigalaxy.xyz/SOA: No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (183.192.201.90, UDP_-_EDNS0_4096_D_K_0x20)
  • xyz to tokisakigalaxy.xyz: The following NS name(s) were found in the delegation NS RRset (i.e., in the xyz zone), but not in the authoritative NS RRset: f1g1ns1.dnspod.net, f1g1ns2.dnspod.net See RFC 1034, Sec. 4.2.2.
  • xyz/DS (alg 8, id 3599): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • xyz/DS (alg 8, id 3599): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • xyz/DS (alg 8, id 3599): 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.
  • xyz/DS (alg 8, id 3599): 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.
  • tokisakigalaxy.xyz/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • tokisakigalaxy.xyz/NS has warnings; select the "Denial of existence" DNSSEC option to see them.
  • tokisakigalaxy.xyz/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