mypay.gov
Updated:
2020-10-22 18:02:29 UTC (1280 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Secure (1)
- gov/SOA
DNSKEY/DS/NSEC status
Secure (7)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 26116)
- NSEC3 proving non-existence of mypay.gov/DS
- gov/DNSKEY (alg 8, id 15489)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
Delegation status
Lame (1)
- gov to mypay.gov
Secure (1)
- . to gov
Notices
Errors (4)
- mypay.gov zone: The following NS name(s) did not resolve to address(es): dns19.dfas.mil, dns2.dfas.mil, dns23.dfas.mil
- mypay.gov zone: The server(s) were not responsive to queries over UDP. (206.39.12.245, 207.133.150.245, 207.133.248.245)
- mypay.gov/A: No response was received from the server over UDP (tried 12 times). (206.39.12.245, 207.133.150.245, 207.133.248.245, UDP_-_NOEDNS_)
- mypay.gov/NS: No response was received from the server over UDP (tried 12 times). (206.39.12.245, 207.133.150.245, 207.133.248.245, UDP_-_NOEDNS_)
Warnings (4)
- gov/DS (alg 8, id 7698): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
- gov/DS (alg 8, id 7698): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
- gov/DS (alg 8, id 7698): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset.
- gov/DS (alg 8, id 7698): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset.
JavaScript is required to make the graph below interactive.
