View on GitHub

DNSViz: A DNS visualization tool

vets.gov

DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Secure (14)
  • vets.gov/A
  • vets.gov/A
  • vets.gov/AAAA
  • vets.gov/AAAA
  • vets.gov/NS
  • vets.gov/NSEC3PARAM
  • vets.gov/NSEC3PARAM
  • vets.gov/NSEC3PARAM
  • vets.gov/NSEC3PARAM
  • vets.gov/NSEC3PARAM
  • vets.gov/NSEC3PARAM
  • vets.gov/NSEC3PARAM
  • vets.gov/SOA
  • vets.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (10)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 47671)
  • gov/DNSKEY (alg 8, id 2706)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • vets.gov/DNSKEY (alg 7, id 34493)
  • vets.gov/DNSKEY (alg 7, id 44589)
  • vets.gov/DNSKEY (alg 7, id 58815)
  • vets.gov/DS (alg 7, id 58815)
  • vets.gov/DS (alg 7, id 58815)

Delegation statusDelegation status

Secure (2)
  • . to gov
  • gov to vets.gov

NoticesNotices

Errors (3)
  • vets.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • vets.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • l4jcum5zne.vets.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (223)
  • RRSIG vets.gov/A alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/A alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/A alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/A alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/A alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/A alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/A alg 7, id 34493: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:00:51+00:00) is within possible clock skew range (2 minutes) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/A alg 7, id 34493: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:01:06+00:00) is within possible clock skew range (2 minutes) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/A alg 7, id 34493: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:02:39+00:00) is within possible clock skew range (27 seconds) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/A alg 7, id 34493: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:02:50+00:00) is within possible clock skew range (16 seconds) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/A alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/A alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/A alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/A alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/A alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/A alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/A alg 7, id 44589: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:00:51+00:00) is within possible clock skew range (2 minutes) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/A alg 7, id 44589: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:01:06+00:00) is within possible clock skew range (2 minutes) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/A alg 7, id 44589: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:02:39+00:00) is within possible clock skew range (27 seconds) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/A alg 7, id 44589: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:02:50+00:00) is within possible clock skew range (16 seconds) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/AAAA alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/AAAA alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/AAAA alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/AAAA alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/AAAA alg 7, id 34493: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:02:50+00:00) is within possible clock skew range (16 seconds) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/AAAA alg 7, id 34493: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:02:50+00:00) is within possible clock skew range (16 seconds) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/AAAA alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/AAAA alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/AAAA alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/AAAA alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/AAAA alg 7, id 44589: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:02:50+00:00) is within possible clock skew range (16 seconds) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/AAAA alg 7, id 44589: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:02:50+00:00) is within possible clock skew range (16 seconds) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 34493: The value of the Signature Inception field of the RRSIG RR (2022-05-03 17:58:37+00:00) is within possible clock skew range (4 minutes) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 34493: The value of the Signature Inception field of the RRSIG RR (2022-05-03 17:58:37+00:00) is within possible clock skew range (4 minutes) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 34493: The value of the Signature Inception field of the RRSIG RR (2022-05-03 17:58:37+00:00) is within possible clock skew range (4 minutes) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 34493: The value of the Signature Inception field of the RRSIG RR (2022-05-03 17:59:34+00:00) is within possible clock skew range (3 minutes) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 34493: The value of the Signature Inception field of the RRSIG RR (2022-05-03 17:59:34+00:00) is within possible clock skew range (3 minutes) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 34493: The value of the Signature Inception field of the RRSIG RR (2022-05-03 17:59:34+00:00) is within possible clock skew range (3 minutes) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 34493: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:00:54+00:00) is within possible clock skew range (2 minutes) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 34493: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:00:54+00:00) is within possible clock skew range (2 minutes) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 34493: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:00:54+00:00) is within possible clock skew range (2 minutes) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 34493: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:01:06+00:00) is within possible clock skew range (2 minutes) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 34493: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:01:06+00:00) is within possible clock skew range (2 minutes) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 34493: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:01:06+00:00) is within possible clock skew range (2 minutes) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 44589: The value of the Signature Inception field of the RRSIG RR (2022-05-03 17:58:37+00:00) is within possible clock skew range (4 minutes) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 44589: The value of the Signature Inception field of the RRSIG RR (2022-05-03 17:58:37+00:00) is within possible clock skew range (4 minutes) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 44589: The value of the Signature Inception field of the RRSIG RR (2022-05-03 17:58:37+00:00) is within possible clock skew range (4 minutes) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 44589: The value of the Signature Inception field of the RRSIG RR (2022-05-03 17:59:34+00:00) is within possible clock skew range (3 minutes) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 44589: The value of the Signature Inception field of the RRSIG RR (2022-05-03 17:59:34+00:00) is within possible clock skew range (3 minutes) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 44589: The value of the Signature Inception field of the RRSIG RR (2022-05-03 17:59:34+00:00) is within possible clock skew range (3 minutes) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 44589: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:00:54+00:00) is within possible clock skew range (2 minutes) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 44589: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:00:54+00:00) is within possible clock skew range (2 minutes) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 44589: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:00:54+00:00) is within possible clock skew range (2 minutes) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 44589: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:01:06+00:00) is within possible clock skew range (2 minutes) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 44589: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:01:06+00:00) is within possible clock skew range (2 minutes) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 44589: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:01:06+00:00) is within possible clock skew range (2 minutes) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 58815: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 58815: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 58815: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 58815: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 58815: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 58815: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 58815: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 58815: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 58815: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 58815: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 58815: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 58815: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 58815: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 58815: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 58815: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 58815: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 58815: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 58815: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 58815: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 58815: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 58815: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 58815: The value of the Signature Inception field of the RRSIG RR (2022-05-03 17:58:37+00:00) is within possible clock skew range (4 minutes) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 58815: The value of the Signature Inception field of the RRSIG RR (2022-05-03 17:58:37+00:00) is within possible clock skew range (4 minutes) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 58815: The value of the Signature Inception field of the RRSIG RR (2022-05-03 17:58:37+00:00) is within possible clock skew range (4 minutes) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 58815: The value of the Signature Inception field of the RRSIG RR (2022-05-03 17:59:34+00:00) is within possible clock skew range (3 minutes) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 58815: The value of the Signature Inception field of the RRSIG RR (2022-05-03 17:59:34+00:00) is within possible clock skew range (3 minutes) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 58815: The value of the Signature Inception field of the RRSIG RR (2022-05-03 17:59:34+00:00) is within possible clock skew range (3 minutes) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 58815: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:00:54+00:00) is within possible clock skew range (2 minutes) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 58815: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:00:54+00:00) is within possible clock skew range (2 minutes) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 58815: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:00:54+00:00) is within possible clock skew range (2 minutes) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 58815: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:01:06+00:00) is within possible clock skew range (2 minutes) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 58815: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:01:06+00:00) is within possible clock skew range (2 minutes) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/DNSKEY alg 7, id 58815: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:01:06+00:00) is within possible clock skew range (2 minutes) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/NS alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/NS alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/NS alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/NS alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/NS alg 7, id 34493: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:02:12+00:00) is within possible clock skew range (54 seconds) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/NS alg 7, id 34493: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:02:50+00:00) is within possible clock skew range (16 seconds) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/NS alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/NS alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/NS alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/NS alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/NS alg 7, id 44589: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:02:12+00:00) is within possible clock skew range (54 seconds) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/NS alg 7, id 44589: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:02:50+00:00) is within possible clock skew range (16 seconds) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/NSEC3PARAM alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/NSEC3PARAM alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/NSEC3PARAM alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/NSEC3PARAM alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/NSEC3PARAM alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/NSEC3PARAM alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/NSEC3PARAM alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/NSEC3PARAM alg 7, id 34493: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:02:50+00:00) is within possible clock skew range (16 seconds) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/NSEC3PARAM alg 7, id 34493: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:02:50+00:00) is within possible clock skew range (16 seconds) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/NSEC3PARAM alg 7, id 34493: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:02:50+00:00) is within possible clock skew range (16 seconds) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/NSEC3PARAM alg 7, id 34493: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:02:50+00:00) is within possible clock skew range (16 seconds) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/NSEC3PARAM alg 7, id 34493: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:02:50+00:00) is within possible clock skew range (16 seconds) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/NSEC3PARAM alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/NSEC3PARAM alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/NSEC3PARAM alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/NSEC3PARAM alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/NSEC3PARAM alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/NSEC3PARAM alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/NSEC3PARAM alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/NSEC3PARAM alg 7, id 44589: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:02:50+00:00) is within possible clock skew range (16 seconds) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/NSEC3PARAM alg 7, id 44589: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:02:50+00:00) is within possible clock skew range (16 seconds) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/NSEC3PARAM alg 7, id 44589: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:02:50+00:00) is within possible clock skew range (16 seconds) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/NSEC3PARAM alg 7, id 44589: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:02:50+00:00) is within possible clock skew range (16 seconds) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/NSEC3PARAM alg 7, id 44589: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:02:50+00:00) is within possible clock skew range (16 seconds) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/SOA alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/SOA alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/SOA alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/SOA alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/SOA alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/SOA alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/SOA alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/SOA alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/SOA alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/SOA alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/SOA alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/SOA alg 7, id 34493: The value of the Signature Inception field of the RRSIG RR (2022-05-03 17:59:18+00:00) is within possible clock skew range (3 minutes) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/SOA alg 7, id 34493: The value of the Signature Inception field of the RRSIG RR (2022-05-03 17:59:56+00:00) is within possible clock skew range (3 minutes) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/SOA alg 7, id 34493: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:00:22+00:00) is within possible clock skew range (2 minutes) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/SOA alg 7, id 34493: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:01:00+00:00) is within possible clock skew range (2 minutes) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/SOA alg 7, id 34493: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:01:26+00:00) is within possible clock skew range (1 minute) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/SOA alg 7, id 34493: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:01:36+00:00) is within possible clock skew range (1 minute) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/SOA alg 7, id 34493: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:02:38+00:00) is within possible clock skew range (28 seconds) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/SOA alg 7, id 34493: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:02:50+00:00) is within possible clock skew range (16 seconds) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/SOA alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/SOA alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/SOA alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/SOA alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/SOA alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/SOA alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/SOA alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/SOA alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/SOA alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/SOA alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/SOA alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/SOA alg 7, id 44589: The value of the Signature Inception field of the RRSIG RR (2022-05-03 17:59:18+00:00) is within possible clock skew range (3 minutes) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/SOA alg 7, id 44589: The value of the Signature Inception field of the RRSIG RR (2022-05-03 17:59:56+00:00) is within possible clock skew range (3 minutes) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/SOA alg 7, id 44589: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:00:22+00:00) is within possible clock skew range (2 minutes) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/SOA alg 7, id 44589: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:01:00+00:00) is within possible clock skew range (2 minutes) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/SOA alg 7, id 44589: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:01:26+00:00) is within possible clock skew range (1 minute) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/SOA alg 7, id 44589: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:01:36+00:00) is within possible clock skew range (1 minute) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/SOA alg 7, id 44589: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:02:38+00:00) is within possible clock skew range (28 seconds) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/SOA alg 7, id 44589: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:02:50+00:00) is within possible clock skew range (16 seconds) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/TXT alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/TXT alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/TXT alg 7, id 34493: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/TXT alg 7, id 34493: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:02:50+00:00) is within possible clock skew range (16 seconds) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG vets.gov/TXT alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/TXT alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/TXT alg 7, id 44589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG vets.gov/TXT alg 7, id 44589: The value of the Signature Inception field of the RRSIG RR (2022-05-03 18:02:50+00:00) is within possible clock skew range (16 seconds) of the current time (2022-05-03 18:03:06+00:00). See RFC 4035, Sec. 5.3.1.
  • gov/DS (alg 8, id 7698): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (192.203.230.10, UDP_-_EDNS0_4096_D_KN)
  • gov/DS (alg 8, id 7698): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (192.203.230.10, UDP_-_EDNS0_4096_D_KN)
  • vets.gov/DS (alg 7, id 58815): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • vets.gov/DS (alg 7, id 58815): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • vets.gov/DS (alg 7, id 58815): 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.
  • vets.gov/DS (alg 7, id 58815): 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.
  • vets.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
  • vets.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • vets.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • l4jcum5zne.vets.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.

DNSKEY legend

Full legend
SEP bit setSEP bit set
Revoke bit setRevoke bit set
Trust anchorTrust anchor
Download: png | svg
Warning JavaScript is required to make the graph below interactive.
DNSSEC authentication graph