faa.gov
Updated:
2023-03-26 00:38:20 UTC (611 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (4)
- faa.gov/NS
- faa.gov/NSEC3PARAM
- faa.gov/SOA
- faa.gov/TXT
DNSKEY/DS/NSEC status
Secure (11)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 60955)
- ./DNSKEY (alg 8, id 951)
- faa.gov/DNSKEY (alg 10, id 16040)
- faa.gov/DNSKEY (alg 10, id 49653)
- faa.gov/DNSKEY (alg 10, id 61700)
- faa.gov/DS (alg 10, id 49653)
- faa.gov/DS (alg 10, id 49653)
- gov/DNSKEY (alg 8, id 24250)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
Delegation status
Secure (2)
- . to gov
- gov to faa.gov
Notices
Errors (15)
- faa.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (155.178.199.16, 155.178.206.21, 2001:19e8:8001:2990::16)
- faa.gov/DNSKEY: No response was received from the server over UDP (tried 13 times). See RFC 1035, Sec. 4.2. (162.58.33.66, 2001:19e8:8041:21::80, UDP_-_EDNS0_4096_D_KN)
- faa.gov/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (162.58.33.66, 162.58.35.136, UDP_-_EDNS0_512_D_KN)
- faa.gov/MX: No response was received from the server over TCP (tried 1 times). See RFC 1035, Sec. 4.2. (2001:19e8:8041:21::80, TCP_-_EDNS0_4096_D_KN)
- faa.gov/MX: No response was received from the server over UDP (tried 10 times). See RFC 1035, Sec. 4.2. (162.58.33.66, 162.58.35.136, UDP_-_EDNS0_4096_D_KN)
- faa.gov/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (162.58.33.66, 162.58.35.136, 2001:19e8:8041:21::80, UDP_-_EDNS0_512_D_KN)
- faa.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (155.178.199.16, 155.178.206.21, 2001:19e8:8001:2990::16, UDP_-_NOEDNS_)
- faa.gov/NSEC3PARAM: No response was received from the server over TCP (tried 5 times). See RFC 1035, Sec. 4.2. (162.58.35.136, TCP_-_EDNS0_4096_D_KN)
- faa.gov/SOA: No response was received from the server over TCP (tried 5 times). See RFC 1035, Sec. 4.2. (162.58.35.136, 2001:19e8:8041:21::80, TCP_-_EDNS0_4096_D_KN, TCP_-_EDNS0_4096_D_KN_0x20)
- faa.gov/TXT: No response was received from the server over TCP (tried 5 times). See RFC 1035, Sec. 4.2. (162.58.33.66, 2001:19e8:8041:21::80, TCP_-_EDNS0_4096_D_KN)
- faa.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- faa.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- faa.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- hzb6u2rc7q.faa.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- faa.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (20)
- RRSIG faa.gov/DNSKEY alg 10, id 16040: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG faa.gov/DNSKEY alg 10, id 16040: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG faa.gov/DNSKEY alg 10, id 16040: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG faa.gov/DNSKEY alg 10, id 49653: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG faa.gov/DNSKEY alg 10, id 49653: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG faa.gov/DNSKEY alg 10, id 49653: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG faa.gov/NS alg 10, id 16040: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG faa.gov/NSEC3PARAM alg 10, id 16040: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG faa.gov/SOA alg 10, id 16040: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG faa.gov/TXT alg 10, id 16040: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- faa.gov/DS (alg 10, id 49653): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- faa.gov/DS (alg 10, id 49653): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- faa.gov/DS (alg 10, id 49653): 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.
- faa.gov/DS (alg 10, id 49653): 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.
- faa.gov/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. (162.58.35.136, UDP_-_EDNS0_4096_D_KN)
- gov to faa.gov: AAAA glue records exist for faa-mc-egm1.faa.gov, but there are no corresponding authoritative AAAA records. See RFC 1034, Sec. 4.2.2.
- faa.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- faa.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- faa.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- faa.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
