faa.gov
Updated:
2023-05-24 21:06:43 UTC (472 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (4)
- faa.gov/MX
- faa.gov/NS
- faa.gov/SOA
- faa.gov/TXT
Secure (1)
- gov/SOA
DNSKEY/DS/NSEC status
Secure (6)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 60955)
- NSEC3 proving non-existence of faa.gov/DS
- gov/DNSKEY (alg 8, id 50011)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
Delegation status
Insecure (1)
- gov to faa.gov
Secure (1)
- . to gov
Notices
Errors (6)
- NSEC3 proving non-existence of faa.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of faa.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- 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, 162.58.33.66, 2001:19e8:8001:2990::16, 2001:19e8:8041:21::80)
- 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, 162.58.33.66, 2001:19e8:8001:2990::16, 2001:19e8:8041:21::80, UDP_-_NOEDNS_)
- faa.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- faa.gov/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
- NSEC3 proving non-existence of faa.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of faa.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- gov to faa.gov: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the gov zone): faa-ct-egm1.faa.gov, faa-mc-egm1.faa.gov See RFC 1034, Sec. 4.2.2.
- faa.gov/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
