View on GitHub

DNSViz: A DNS visualization tool

fehrm.gov

Updated: 2025-03-12 19:08:40 UTC (294 days ago) Update now
« Previous analysis | Next analysis »
DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Insecure (4)
  • fehrm.gov/A
  • fehrm.gov/NS
  • fehrm.gov/SOA
  • fehrm.gov/TXT
Secure (1)
  • gov/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (7)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26470)
  • ./DNSKEY (alg 8, id 38696)
  • NSEC proving non-existence of fehrm.gov/DS
  • gov/DNSKEY (alg 13, id 2536)
  • gov/DNSKEY (alg 13, id 35496)
  • gov/DS (alg 13, id 2536)

Delegation statusDelegation status

Insecure (1)
  • gov to fehrm.gov
Secure (1)
  • . to gov

NoticesNotices

Warnings (2)
  • fehrm.gov/SOA: No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (214.2.213.178, UDP_-_EDNS0_4096_D_KN)
  • gov to fehrm.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): ns01-we-gw.health.mil See RFC 1034, Sec. 4.2.2.

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