View on GitHub

DNSViz: A DNS visualization tool

gov.pt

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

RRset statusRRset status

Bogus (4)
  • gov.pt/NS
  • gov.pt/NSEC3PARAM
  • gov.pt/SOA
  • gov.pt/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Bogus (3)
  • gov.pt/DNSKEY (alg 10, id 41576)
  • gov.pt/DNSKEY (alg 10, id 51381)
  • gov.pt/DNSKEY (alg 10, id 55073)
Secure (6)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 5613)
  • gov.pt/DS (alg 10, id 51381)
  • pt/DNSKEY (alg 13, id 30640)
  • pt/DNSKEY (alg 13, id 40155)
  • pt/DS (alg 13, id 40155)

Delegation statusDelegation status

Bogus (1)
  • pt to gov.pt
Secure (1)
  • . to pt

NoticesNotices

Errors (32)
  • RRSIG gov.pt/DNSKEY alg 10, id 41576: The Signature Expiration field of the RRSIG RR (2024-04-30 11:25:05+00:00) is 7 hours, 14 minutes in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG gov.pt/DNSKEY alg 10, id 41576: The Signature Expiration field of the RRSIG RR (2024-04-30 11:25:05+00:00) is 7 hours, 14 minutes in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG gov.pt/DNSKEY alg 10, id 41576: The Signature Expiration field of the RRSIG RR (2024-04-30 11:25:05+00:00) is 7 hours, 14 minutes in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG gov.pt/DNSKEY alg 10, id 51381: The Signature Expiration field of the RRSIG RR (2024-04-30 11:25:05+00:00) is 7 hours, 14 minutes in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG gov.pt/DNSKEY alg 10, id 51381: The Signature Expiration field of the RRSIG RR (2024-04-30 11:25:05+00:00) is 7 hours, 14 minutes in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG gov.pt/DNSKEY alg 10, id 51381: The Signature Expiration field of the RRSIG RR (2024-04-30 11:25:05+00:00) is 7 hours, 14 minutes in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG gov.pt/DNSKEY alg 10, id 55073: The Signature Expiration field of the RRSIG RR (2024-04-30 11:25:05+00:00) is 7 hours, 14 minutes in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG gov.pt/DNSKEY alg 10, id 55073: The Signature Expiration field of the RRSIG RR (2024-04-30 11:25:05+00:00) is 7 hours, 14 minutes in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG gov.pt/DNSKEY alg 10, id 55073: The Signature Expiration field of the RRSIG RR (2024-04-30 11:25:05+00:00) is 7 hours, 14 minutes in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG gov.pt/NS alg 10, id 41576: The Signature Expiration field of the RRSIG RR (2024-04-30 11:25:04+00:00) is 7 hours, 14 minutes in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG gov.pt/NS alg 10, id 55073: The Signature Expiration field of the RRSIG RR (2024-04-30 11:25:04+00:00) is 7 hours, 14 minutes in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG gov.pt/NSEC3PARAM alg 10, id 41576: The Signature Expiration field of the RRSIG RR (2024-04-30 11:25:05+00:00) is 7 hours, 14 minutes in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG gov.pt/NSEC3PARAM alg 10, id 55073: The Signature Expiration field of the RRSIG RR (2024-04-30 11:25:05+00:00) is 7 hours, 14 minutes in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG gov.pt/SOA alg 10, id 41576: The Signature Expiration field of the RRSIG RR (2024-04-30 11:25:04+00:00) is 7 hours, 14 minutes in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG gov.pt/SOA alg 10, id 55073: The Signature Expiration field of the RRSIG RR (2024-04-30 11:25:04+00:00) is 7 hours, 14 minutes in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG gov.pt/TXT alg 10, id 41576: The Signature Expiration field of the RRSIG RR (2024-04-30 11:25:04+00:00) is 7 hours, 14 minutes in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG gov.pt/TXT alg 10, id 55073: The Signature Expiration field of the RRSIG RR (2024-04-30 11:25:04+00:00) is 7 hours, 14 minutes in the past. See RFC 4035, Sec. 5.3.1.
  • gov.pt zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (185.39.208.1)
  • gov.pt zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (193.47.185.3)
  • gov.pt/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (185.39.208.1, UDP_-_EDNS0_4096_D_KN)
  • gov.pt/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (193.47.185.3, UDP_-_NOEDNS_)
  • gov.pt/NSEC3PARAM: No response was received from the server over TCP (tried 12 times). See RFC 1035, Sec. 4.2. (185.39.208.1, TCP_-_EDNS0_4096_D_KN)
  • gov.pt/SOA: No response was received from the server over TCP (tried 12 times). See RFC 1035, Sec. 4.2. (185.39.208.1, TCP_-_EDNS0_4096_D_KN, TCP_-_EDNS0_4096_D_KN_0x20)
  • gov.pt/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (185.39.208.1, TCP_-_EDNS0_4096_D_N)
  • gov.pt/TXT: No response was received from the server over TCP (tried 12 times). See RFC 1035, Sec. 4.2. (185.39.208.1, TCP_-_EDNS0_4096_D_KN)
  • pt to gov.pt: 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. (193.136.2.228, 194.58.196.32, 194.58.198.32, 2001:690:a80:4001::200, 2a01:3f1:832::53, 2a01:3f1:3032::53, 2a04:6d80::1, TCP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN)
  • gov.pt/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • gov.pt/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • gov.pt/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • gov.pt/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • gov.pt/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • eclir1s8t2.gov.pt/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (23)
  • RRSIG gov.pt/DNSKEY alg 10, id 41576: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG gov.pt/DNSKEY alg 10, id 41576: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG gov.pt/DNSKEY alg 10, id 41576: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG gov.pt/DNSKEY alg 10, id 51381: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG gov.pt/DNSKEY alg 10, id 51381: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG gov.pt/DNSKEY alg 10, id 51381: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG gov.pt/DNSKEY alg 10, id 55073: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG gov.pt/DNSKEY alg 10, id 55073: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG gov.pt/DNSKEY alg 10, id 55073: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG gov.pt/NS alg 10, id 41576: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG gov.pt/NS alg 10, id 55073: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG gov.pt/NSEC3PARAM alg 10, id 41576: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG gov.pt/NSEC3PARAM alg 10, id 55073: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG gov.pt/SOA alg 10, id 41576: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG gov.pt/SOA alg 10, id 55073: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG gov.pt/TXT alg 10, id 41576: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG gov.pt/TXT alg 10, id 55073: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • gov.pt/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • gov.pt/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • gov.pt/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • gov.pt/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
  • gov.pt/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • eclir1s8t2.gov.pt/A 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