Skip to content
https://gsa.gov

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
92
GRADE
A
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
6 PASS 2 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
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.gsa.gov/
200https://gsa.gov/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://gsa.gov/ → https://gsa.gov/

Consistent

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

Certificate validity

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

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
DNS Records
1 A records, 124 ms lookup
PASS
1 A records, 124 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 23.22.13.113
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:1f18:f88:4313:6df7:f986:f915:78d6
Info::
5 nameserver(s) configured
Got: dns4.gsa.gov, dns.gsa.gov, dns3.gsa.gov, dns5.gsa.gov, dns2.gsa.gov
Info::
5 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
Info::
DNS resolution time: 124 ms
Got: 124 ms
A23.22.13.113
AAAA2600:1f18:f88:4313:6df7:f986:f915:78d6
CNAME—
NSdns4.gsa.gov, dns.gsa.gov, dns3.gsa.gov, dns5.gsa.gov, dns2.gsa.gov
MX
1 aspmx.l.google.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
10 alt3.aspmx.l.google.com
10 alt4.aspmx.l.google.com
TXT
SPF v=spf1 include:spf_a0.gsa.gov include:spf_a1.gsa.gov include:spf_a2.gsa.gov incl...
docusign=6f6dab46-2129-4700-bcc2-4be235fe5aff
google-site-verification=-Yfs3oCZ4rPr5BMX8tRANSV7anmxMrHQdjVTsXEs3hI
atlassian-sending-domain-verification=e954f878-7df6-4ee3-8ac9-ee19a1c2313b
MS=ms26417977
amazonses:WroIovKkM+OAxfzL9xYOXM46pksrcS266o23tVoM86M=
MS=ms26706564
docusign=72fc694f-0f63-46e4-b089-e0c8171c4139
google-site-verification=VcCceMeA2ZU7w_aEbQxO6sRlhMMgjjkULRiYjMO_IkY
amazonses:VpDldJ0Y17bUz5N4BLA9tuxzm/5CaAJjTwSrhS/1yiE=
airtable-verification=e6bb1631f52c503b7a3701046ed7af9b
mongodb-site-verification=CzhLKr4OAzreXpHBbawUlSmfDifmuWc1
google-site-verification=fyO5fRlizCOUL6drs0QADUV1J8JHq09DYpoUVMXu5VI
atlassian-domain-verification=mCilJyOCl8iDKRaaRyLEWIDAFdy9cbTRnpIZHoYyHGHDPfFNo1...
MS=ms52409976
MS=ms74458519
_4pfesgfj8b7lm7k40p5oy1y9c8s88fa
amazonses:nvZjWRLWNEaQIGC6ol8XEJa7lrt7INEu2jUWId7r0J8=
google-site-verification=hCDz_TYLNfL0TB3q_SoYaXaHl6TlJdbXfYQyAItdDBE
figma-domain-verification=92ef70a8bfe22d77050cd6d3a3fb0671e21c82984fb63729f6b949...
docker-verification=b87e77d3-0821-4993-87f8-2dad0f313ed3
webexdomainverification.7Q711=c9959908-c26f-4865-8fc7-1792b83294ab
mongodb-site-verification=EqZXwkmCFUWN8QEautFYXdCqXV6HH3Ox
d3nv1z3w6h7vef.cloudfront.net
smartsheet-gov-site-validation=n83lQJsr87UvaVx95hZfV7JDrREq891h
apple-domain-verification=amOa5lUwKVdgvUFn
CAALookup not available with standard resolver
Resolved in 124 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.

A
Redirect Chain
1 redirect(s), 592 ms total
PASS
1 redirect(s), 592 ms total
Info::
Single redirect
Got: https://gsa.gov → https://www.gsa.gov/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 592 ms total
Got: 592 ms

https://gsa.gov

301 ms · HTTP/1.1

301

https://www.gsa.gov/

291 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://gsa.gov301301 msHTTP/1.1
2https://www.gsa.gov/200291 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (101 ms)
PASS
IPv6 reachable (101 ms)
Info::
IPv6 is configured and reachable at 2600:1f18:f88:4313:6df7:f986:f915:78d6
Got: 101 ms connect
IPv6 Ready
AAAA Records 2600:1f18:f88:4313:6df7:f986:f915:78d6 Connection Reachable (101 ms)
A+
Crawlability
robots.txt present, sitemap with 7979 URLs
PASS
robots.txt present, sitemap with 7979 URLs
Info::
robots.txt is present
Got: 2027 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 7979 entries
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 2027 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
#
# robots.txt
#
# This file is to prevent the crawling and indexing of certain parts
# of your site by web crawlers and spiders run by sites like Yahoo!
# and Google. By telling these "robots" where not to go on your site,
# you save bandwidth and server resources.
#
# This file will be ignored unless it is at the root of your host:
# Used:    http://example.com/robots.txt
# Ignored: http://example.com/site/robots.txt
#
# For more information about the robots.txt standard, see:
# http://www.robotstxt.org/robotstxt.html

User-agent: *
# CSS, JS, Images
Allow: /core/*.css$
Allow: /core/*.css?
Allow: /core/*.js$
Allow: /core/*.js?
Allow: /core/*.gif
Allow: /core/*.jpg
Allow: /core/*.jpeg
Allow: /core/*.png
Allow: /core/*.svg
Allow: /profiles/*.css$
Allow: /profiles/*.css?
Allow: /profiles/*.js$
Allow: /profiles/*.js?
Allow: /profiles/*.gif
Allow: /profiles/*.jpg
Allow: /profiles/*.jpeg
Allow: /profiles/*.png
Allow: /profiles/*.svg
# Directories
Disallow: /core/
Disallow: /profiles/
# Files
Disallow: /README.md
Disallow: /composer/Metapackage/README.txt
Disallow: /composer/Plugin/ProjectMessage/README.md
Disallow: /composer/Plugin/Scaffold/README.md
Disallow: /composer/Plugin/VendorHardening/README.txt
Disallow: /composer/Template/README.txt
Disallow: /modules/README.txt
Disallow: /sites/README.txt
Disallow: /themes/README.txt
Disallow: /web.config
# Paths (clean URLs)
Disallow: /admin/
Disallow: /comment/reply/
Disallow: /filter/tips
Disallow: /node/add/
Disallow: /search/
Disallow: /user/register
Disallow: /user/password
Disallow: /user/login
Disallow: /user/logout
Disallow: /media/oembed
Disallow: /*/media/oembed
# Paths (no clean URLs)
Disallow: /index.php/admin/
Disallow: /index.php/comment/reply/
Disallow: /index.php/filter/tips
Disallow: /index.php/node/add/
Disallow: /index.php/search/
Disallow: /index.php/user/password
Disallow: /index.php/user/register
Disallow: /index.php/user/login
Disallow: /index.php/user/logout
Disallow: /index.php/media/oembed
Disallow: /index.php/*/media/oembed
sitemap.xml 200 OK
Type URL Set URLs 7979 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
gsa.gov — via get.gov, 28 years, 11 months old
PASS
gsa.gov — via get.gov, 28 years, 11 months old
Info::
Domain registered until Sep 2, 2026 (4 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

46 days

September 2, 2026

SSL certificate

58 days

Issued by Let's Encrypt

Domain age

28 years, 11 months

Registered October 2, 1997

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Unknown

2600:1f18:f88:4313:6df7:f986:f915:78d6

Registrar

get.gov

Unlocked 5 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 September 2, 2026 (4 months)
Last Updated November 6, 2025
Name Servers dns.gsa.gov, dns2.gsa.gov, dns3.gsa.gov, dns4.gsa.gov, dns5.gsa.gov
DNSSEC Enabled
Registrant REDACTED FOR PRIVACY
Hosting
IP Address 2600:1f18:f88:4313:6df7:f986:f915:78d6
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 318 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
21 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
97 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
103 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
319 ms
Total Time Total request time from DNS lookup through full response.
319 ms

Connection waterfall

DNS Lookup 21 ms TCP Connect 97 ms TLS Handshake 103 ms Server Processing 97 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