Skip to content
https://va.gov

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 3 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

B
Redirect Chain
1 redirect(s), 1534 ms total
REVIEW
1 redirect(s), 1534 ms total
Info::
Single redirect
Got: https://va.gov → https://www.va.gov/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1534 ms total
Got: 1534 ms

https://va.gov

713 ms · HTTP/1.1

301

https://www.va.gov/

821 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://va.gov301713 msHTTP/1.1
2https://www.va.gov/200821 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.va.gov/
200https://va.gov/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://va.gov/ → https://va.gov:443/

Consistent

B
TLS Certificate Expiry & Recommendations
272 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

272
days left
0d 30d 60d 90d+

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • Add includeSubDomains to the HSTS directive
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A
DNS Records
1 A records, 279 ms lookup
PASS
1 A records, 279 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 152.131.96.221
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2600:8030:0:28::30:221
Info::
4 nameserver(s) configured
Got: ns3x.va.gov, ns1x.va.gov, ns4x.va.gov, ns2x.va.gov
Info::
1 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Warning::
DNS resolution is slow (279 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 279 ms
A152.131.96.221
AAAA2600:8030:0:28::30:221
CNAME—
NSns3x.va.gov, ns1x.va.gov, ns4x.va.gov, ns2x.va.gov
MX
10 mx20.va.gov
TXT
MS=ms28494616
docusign=1df408c8-ae62-42aa-81fb-cbacef5c7561
_5ri78mzgbmvox0mvm8ou5wxkmpx9woh
_w1ybjynlrsafrjumudrp5ilvgsom6hq
docusign=31552c45-f8a2-4607-9542-acf2c7b6ddff
SPF v=spf1 mx ip4:152.130.26.32/27 ip4:152.131.26.32/27 ip4:152.132.26.32/27 ip4:152...
_44pf4890rcbprrl4m69yuzocued8hj3
_ymhmp4c6qowov1llhzi4znjsgw7klp9
google-site-verification=RkAwuvE_HJPBMMNduSFoIOZBXDdFYV8pyziOb8CoqUU
webexdomainverification.4NWTE=159c226b-8398-4ffd-8683-22977242d145
iwIqL1PYelzu9mfBv8t6UAmaBw1PFaM5w0LM/0gDrTOHD9lq2P6biza3ebVIxm4PJbbupeZlfQMuJvET...
m6SyqGL+aO06ndrOtI3kDiZQFVKqPWAGXV+ygrs7DMs=
tbi14aj28g0up3db1th77u1h1s
adobe-idp-site-verification=021f36dcd17c888ff7efe04d03905876a7443340c8a69372bf05...
CAALookup not available with standard resolver
Resolved in 279 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more ▾

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A+
IPv6 Readiness
IPv6 reachable (116 ms)
PASS
IPv6 reachable (116 ms)
Info::
IPv6 is configured and reachable at 2600:8030:0:28::30:221
Got: 116 ms connect
IPv6 Ready
AAAA Records 2600:8030:0:28::30:221 Connection Reachable (116 ms)
A+
Crawlability
robots.txt present, sitemap with 2 URLs
PASS
robots.txt present, sitemap with 2 URLs
Info::
robots.txt is present
Got: 740 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 2 entries
Info::
Sitemap index with 2 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 740 B Sitemaps referenced 3 User-agents usasearch, Synapse, Amazonbot, * Blocking No — crawling allowed
User-agent: usasearch
Allow: /

# existing disallow on va.gov (may not be needed)
User-agent: Synapse
Disallow: /

# block Amazon's AI training crawler
User-agent: Amazonbot
Disallow: /

# existing disallow from vets.gov
User-Agent: *
Disallow: /analytics-opt-out.html
Disallow: /cgi-bin/
Disallow: /drupal
Disallow: /covid19screen
Disallow: /sitemap.xml

# disallow WIP VAMCs
# make sure to add a trailing slash at the end of the path
# to prevent sub-directories from being indexed
# see https://developers.google.com/search/docs/advanced/robots/create-robots-txt#useful-robots.txt-rules


# sitemap index
Sitemap: https://www.va.gov/sitemap_index.xml
Sitemap: https://www.va.gov/sitemap-cb.xml
Sitemap: https://www.va.gov/sitemap-nb.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 2 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
va.gov — via get.gov, 28 years, 11 months old
PASS
va.gov — via get.gov, 28 years, 11 months old
Info::
Domain registered until Aug 4, 2026 (3 months remaining)
Info::
DNSSEC is enabled
Info::
Registrar: get.gov
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Domain expiry

23 days

August 4, 2026

SSL certificate

272 days

Issued by Sectigo Limited

Domain age

28 years, 11 months

Registered October 2, 1997

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Unknown

2600:8030:0:28::30:221

Registrar

get.gov

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar get.gov
Created October 2, 1997 (28 years, 11 months ago)
Expires August 4, 2026 (3 months)
Last Updated January 12, 2026
Name Servers ns1x.va.gov, ns2x.va.gov, ns3x.va.gov, ns4x.va.gov
DNSSEC Enabled
Registrant REDACTED FOR PRIVACY
Hosting
IP Address 2600:8030:0:28::30:221
Data source: rdap (0.4s)

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more ▾

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

A
HTTP Probe Timing
Total 798 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
107 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
153 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
313 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
798 ms
Total Time Total request time from DNS lookup through full response.
798 ms

Connection waterfall

DNS Lookup 107 ms TCP Connect 153 ms TLS Handshake 313 ms Server Processing 225 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback