pay.gov
Updated:
2023-04-22 22:33:01 UTC (581 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (7)
- pay.gov/A
- pay.gov/A
- pay.gov/AAAA
- pay.gov/AAAA
- pay.gov/NS
- pay.gov/SOA
- pay.gov/TXT
Secure (1)
- gov/SOA
DNSKEY/DS/NSEC status
Insecure (2)
- pay.gov/DNSKEY (alg 13, id 38600)
- pay.gov/DNSKEY (alg 13, id 54752)
Secure (6)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 60955)
- NSEC3 proving non-existence of pay.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 pay.gov
Secure (1)
- . to gov
Notices
Errors (4)
- NSEC3 proving non-existence of pay.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 pay.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- RRSIG pay.gov/A alg 13, id 38600: The TTL of the RRset (19) exceeds the value of the Original TTL field of the RRSIG RR covering it (1). See RFC 4035, Sec. 2.2.
- pay.gov/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (3)
- NSEC3 proving non-existence of pay.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of pay.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- pay.gov/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
