View on GitHub

DNSViz: A DNS visualization tool

پاکستان

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

RRset statusRRset status

Bogus (2)
  • پاکستان/NS
  • پاکستان/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (3)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 46594)
  • پاکستان/DS (alg 7, id 21720)
Non_existent (1)
  • پاکستان/DNSKEY (alg 7, id 21720)

Delegation statusDelegation status

Bogus (1)
  • . to پاکستان

NoticesNotices

Errors (15)
  • . to پاکستان: 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. (202.83.164.166, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • . to پاکستان: The DS RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no DS RR matched a DNSKEY with algorithm 7 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (202.83.164.166, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • پاکستان zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (202.83.164.167)
  • پاکستان zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (202.83.164.167)
  • پاکستان zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (175.107.192.11)
  • پاکستان/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (202.83.164.167, UDP_-_EDNS0_512_D_K, UDP_-_NOEDNS_)
  • پاکستان/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (202.83.164.166, UDP_-_EDNS0_4096_D_K)
  • پاکستان/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (175.107.192.11, UDP_-_NOEDNS_)
  • پاکستان/NS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (202.83.164.167, UDP_-_NOEDNS_)
  • پاکستان/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (202.83.164.166, TCP_-_EDNS0_4096_D, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
  • پاکستان/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (202.83.164.167, TCP_-_NOEDNS_)
  • پاکستان/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (202.83.164.167, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
  • xn--mgbai9azgqp6j/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • 03q1otsx8n.xn--mgbai9azgqp6j/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • xn--mgbai9azgqp6j/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
  • پاکستان/DS (alg 7, id 21720): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • پاکستان/DS (alg 7, id 21720): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • پاکستان/DS (alg 7, id 21720): 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.
  • پاکستان/DS (alg 7, id 21720): 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.

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