Skip to content
https://archives.gov

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
94
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.archives.gov/
200https://archives.gov/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

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

Certificate validity

193
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
2 A records, 180 ms lookup
PASS
2 A records, 180 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 52.206.136.3, 52.44.89.206
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2600:1f18:43e8:f301:9046:c05f:75e7:c481, 2600:1f18:43e8:f302:b470:d266:4d03:3ed8
Info::
2 nameserver(s) configured
Got: ns2.fedmettel.net, ns1.fedmettel.net
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
Info::
DNS resolution time: 180 ms
Got: 180 ms
A52.206.136.3, 52.44.89.206
AAAA2600:1f18:43e8:f301:9046:c05f:75e7:c481, 2600:1f18:43e8:f302:b470:d266:4d03:3ed8
CNAME—
NSns2.fedmettel.net, ns1.fedmettel.net
MX
10 us.etp.fireeyegov.com
TXT
google-site-verification=vzFoKGZ49s-tl4Mw26kJfVRiYukV0lHmZlbG0iAYYMk
SPF v=spf1 -all
CAALookup not available with standard resolver
Resolved in 180 ms

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), 576 ms total
PASS
1 redirect(s), 576 ms total
Info::
Single redirect
Got: https://archives.gov → https://www.archives.gov/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 576 ms total
Got: 576 ms

https://archives.gov

299 ms · HTTP/1.1

301

https://www.archives.gov/

277 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://archives.gov301299 msHTTP/1.1nginx
2https://www.archives.gov/200277 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (97 ms)
PASS
IPv6 reachable (97 ms)
Info::
IPv6 is configured and reachable at 2600:1f18:43e8:f301:9046:c05f:75e7:c481, 2600:1f18:43e8:f302:b470:d266:4d03:3ed8
Got: 97 ms connect
IPv6 Ready
AAAA Records 2600:1f18:43e8:f301:9046:c05f:75e7:c481, 2600:1f18:43e8:f302:b470:d266:4d03:3ed8 Connection Reachable (97 ms)
A+
Crawlability
robots.txt present, sitemap with 2 URLs
PASS
robots.txt present, sitemap with 2 URLs
Info::
robots.txt is present
Got: 1048 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 1048 B Sitemaps referenced 4 User-agents usasearch, * 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: *
Crawl-delay: 10

Sitemap: https://www.archives.gov/sitemap.xml
Sitemap: https://www.archives.gov/files/sitemap.xml
Sitemap: https://www.archives.gov/research/native-americans/bia/photos/sitemap.xml
Sitemap: https://www.archives.gov/files/sitemap-other.xml

Disallow: /citizen-archivist/history-hub/hh-test
Disallow: /developer/artificial-intelligence-and-machine-learning-datasets
Disallow: /developer/1940-census
Disallow: /developer/national-archives-catalog-dataset

User-agent: usasearch
Crawl-delay: 2
sitemap.xml 200 OK
Type Sitemap Index URLs 2 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
archives.gov — via get.gov, 25 years, 6 months old
PASS
archives.gov — via get.gov, 25 years, 6 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

49 days

September 2, 2026

SSL certificate

193 days

Issued by Entrust Limited

Domain age

25 years, 6 months

Registered February 1, 2001

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Unknown

2600:1f18:43e8:f301:9046:c05f:75e7:c481

Registrar

get.gov

Unlocked 2 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 February 1, 2001 (25 years, 6 months ago)
Expires September 2, 2026 (4 months)
Last Updated January 6, 2026
Name Servers ns1.fedmettel.net, ns2.fedmettel.net
DNSSEC Enabled
Registrant REDACTED FOR PRIVACY
Hosting
IP Address 2600:1f18:43e8:f301:9046:c05f:75e7:c481
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 413 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
117 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.
101 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
414 ms
Total Time Total request time from DNS lookup through full response.
414 ms

Connection waterfall

DNS Lookup 117 ms TCP Connect 97 ms TLS Handshake 101 ms Server Processing 98 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