ferc.gov
Updated:
2023-04-18 21:08:41 UTC (583 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (9)
- ferc.gov/A
- ferc.gov/MX
- ferc.gov/NS
- ferc.gov/NSEC3PARAM
- ferc.gov/NSEC3PARAM
- ferc.gov/NSEC3PARAM
- ferc.gov/NSEC3PARAM
- ferc.gov/SOA
- ferc.gov/TXT
DNSKEY/DS/NSEC status
Secure (11)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 60955)
- ferc.gov/DNSKEY (alg 8, id 26884)
- ferc.gov/DNSKEY (alg 8, id 54856)
- ferc.gov/DNSKEY (alg 8, id 6009)
- ferc.gov/DS (alg 8, id 54856)
- ferc.gov/DS (alg 8, id 54856)
- gov/DNSKEY (alg 8, id 24250)
- gov/DNSKEY (alg 8, id 50011)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
Delegation status
Secure (2)
- . to gov
- gov to ferc.gov
Notices
Errors (20)
- ./DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (192.112.36.4, UDP_-_EDNS0_512_D_KN)
- ferc.gov zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (204.87.17.240, 216.230.6.246)
- ferc.gov/DNSKEY: No response was received from the server over TCP (tried 12 times). See RFC 1035, Sec. 4.2. (216.230.6.242, TCP_-_EDNS0_4096_D_KN)
- ferc.gov/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (216.230.6.246, UDP_-_NOEDNS_)
- ferc.gov/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (216.230.6.242, 216.230.6.246, UDP_-_EDNS0_512_D_KN)
- ferc.gov/MX: No response was received from the server over TCP (tried 7 times). See RFC 1035, Sec. 4.2. (216.230.6.246, TCP_-_EDNS0_4096_D)
- ferc.gov/MX: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (216.230.6.242, UDP_-_NOEDNS_)
- ferc.gov/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (216.230.6.242, 216.230.6.246, UDP_-_EDNS0_512_D_KN)
- ferc.gov/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (216.230.6.242, 216.230.6.246, TCP_-_EDNS0_4096_D_N)
- ferc.gov/SOA: No response was received from the server over TCP (tried 4 times). See RFC 1035, Sec. 4.2. (216.230.6.242, TCP_-_EDNS0_4096_D)
- ferc.gov/SOA: No response was received from the server over TCP (tried 5 times). See RFC 1035, Sec. 4.2. (216.230.6.242, 216.230.6.246, TCP_-_EDNS0_4096_D_N)
- ferc.gov/SOA: No response was received from the server over TCP (tried 7 times). See RFC 1035, Sec. 4.2. (216.230.6.246, TCP_-_EDNS0_4096_D_KN_0x20)
- ferc.gov/SOA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (204.87.17.240, 204.87.17.241, 216.230.6.242, UDP_-_NOEDNS__0x20)
- ferc.gov/SOA: The TCP connection was interrupted (ECONNRESET). See RFC 1035, Sec. 4.2. (204.87.17.240, TCP_-_EDNS0_4096_D_N)
- ferc.gov/TXT: No response was received from the server over TCP (tried 5 times). See RFC 1035, Sec. 4.2. (216.230.6.246, TCP_-_EDNS0_4096_D_N)
- ferc.gov/TXT: No response was received from the server over TCP (tried 7 times). See RFC 1035, Sec. 4.2. (216.230.6.242, TCP_-_EDNS0_4096_D_KN)
- ferc.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- fk1g0wpmz5.ferc.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- ferc.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- ferc.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (7)
- ferc.gov/DS (alg 8, id 54856): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- ferc.gov/DS (alg 8, id 54856): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- ferc.gov/DS (alg 8, id 54856): 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.
- ferc.gov/DS (alg 8, id 54856): 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.
- ferc.gov/NSEC3PARAM: 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. (216.230.6.246, UDP_-_EDNS0_4096_D_KN)
- ferc.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- ferc.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
