ameslab.gov
Updated:
2020-08-12 02:32:20 UTC (1376 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- ameslab.gov/MX
- ameslab.gov/NS
- ameslab.gov/SOA
- ameslab.gov/SOA
- ameslab.gov/SOA
- ameslab.gov/TXT
DNSKEY/DS/NSEC status
Secure (13)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 46594)
- ameslab.gov/DNSKEY (alg 8, id 39541)
- ameslab.gov/DNSKEY (alg 8, id 41791)
- ameslab.gov/DNSKEY (alg 8, id 64185)
- ameslab.gov/DS (alg 8, id 39541)
- ameslab.gov/DS (alg 8, id 39541)
- ameslab.gov/DS (alg 8, id 41791)
- ameslab.gov/DS (alg 8, id 41791)
- gov/DNSKEY (alg 8, id 26665)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
Delegation status
Secure (2)
- . to gov
- gov to ameslab.gov
Notices
Errors (8)
- ameslab.gov zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. (129.186.67.145, 2610:130:102:112::2)
- ameslab.gov zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. (129.186.67.145, 2610:130:102:112::2)
- ameslab.gov/DNSKEY: The response had an invalid RCODE (SERVFAIL). (129.186.67.145, 2610:130:102:112::2, UDP_-_EDNS0_512_D_K, UDP_-_NOEDNS_)
- ameslab.gov/MX: The response had an invalid RCODE (SERVFAIL). (129.186.67.145, 2610:130:102:112::2, UDP_-_EDNS0_512_D_K, UDP_-_NOEDNS_)
- ameslab.gov/NS: The response had an invalid RCODE (SERVFAIL). (129.186.67.145, 2610:130:102:112::2, UDP_-_NOEDNS_)
- ameslab.gov/SOA: The response had an invalid RCODE (SERVFAIL). (129.186.67.145, 2610:130:102:112::2, TCP_-_NOEDNS_)
- ameslab.gov/SOA: The response had an invalid RCODE (SERVFAIL). (129.186.67.145, 2610:130:102:112::2, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
- ameslab.gov/TXT: The response had an invalid RCODE (SERVFAIL). (129.186.67.145, 2610:130:102:112::2, UDP_-_NOEDNS_)
Warnings (14)
- ameslab.gov/DS (alg 8, id 39541): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
- ameslab.gov/DS (alg 8, id 39541): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
- ameslab.gov/DS (alg 8, id 39541): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset.
- ameslab.gov/DS (alg 8, id 39541): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset.
- ameslab.gov/DS (alg 8, id 41791): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
- ameslab.gov/DS (alg 8, id 41791): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
- ameslab.gov/DS (alg 8, id 41791): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset.
- ameslab.gov/DS (alg 8, id 41791): 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 to ameslab.gov: Authoritative AAAA records exist for fiber.ameslab.gov, but there are no corresponding AAAA glue records.
- gov to ameslab.gov: Authoritative AAAA records exist for scsds.ameslab.gov, but there are no corresponding AAAA glue records.
- 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.
