Skip to content
https://www.archive.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
80
GRADE
B
FIX
2
REVIEW
2
PASS
5
INFO
0
Probed from Santa Clara, United Stated
302 Found
Checks
9
5 PASS 2 REVIEW 2 FIX
D
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
FIX
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
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 302 Expected: 301 redirect to HTTPS

www / non-www

200https://www.archive.org/
200https://archive.org/

Inconsistent — duplicate content risk

HTTP → HTTPS

302http://www.archive.org/ → http://archive.org/

HTTP version does not redirect to HTTPS

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.

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

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

Certificate validity

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

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable DNSSEC on your domain for DNS spoofing protection
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A
DNS Records
1 A records, 8 ms lookup
PASS
1 A records, 8 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 207.241.224.2
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 8 ms
Got: 8 ms
A207.241.224.2
AAAA—
CNAME—
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 8 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.

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

A
Redirect Chain
1 redirect(s), 88 ms total
PASS
1 redirect(s), 88 ms total
Info::
Single redirect
Got: https://www.archive.org → https://archive.org/ (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://www.archive.org

https://www.archive.org

29 ms · HTTP/1.1

302

https://archive.org/

59 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.archive.org30229 msHTTP/1.1nginx/1.24.0
2https://archive.org/20059 msHTTP/1.1nginx/1.24.0

See the visual redirect chain in the HTTP Probe tab →

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more ▾

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

A+
Crawlability
robots.txt present, sitemap with 1403 URLs
PASS
robots.txt present, sitemap with 1403 URLs
Info::
robots.txt is present
Got: 238 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 1403 entries
Info::
Sitemap index with 1403 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 238 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed

Sitemap: https://archive.org/sitemap/sitemap.xml

##############################################
#
# Welcome to the Internet Archive!
#
##############################################

User-agent: *
Disallow: /control/
Disallow: /report/
sitemap.xml 200 OK
Type Sitemap Index URLs 1403 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
archive.org — via easyDNS Technologies Inc., 30 years, 9 months old, hosted on INTERNET-ARCHIVE - Internet Archive, US
PASS
archive.org — via easyDNS Technologies Inc., 30 years, 9 months old, hosted on INTERNET-ARCHIVE - Internet Archive, US
Info::
Domain registered until Dec 13, 2030 (4 years, 9 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: easyDNS Technologies Inc.
Info::
Hosting: INTERNET-ARCHIVE - Internet Archive, US
Got: AS7941
Domain expiry

1579 days

December 13, 2030

SSL certificate

308 days

Issued by GoDaddy.com, Inc.

Domain age

30 years, 9 months

Registered December 14, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

INTERNET-ARCHIVE - Internet Archive, US

ASN AS7941

207.241.224.2

Registrar

easyDNS Technologies Inc.

Lock status unknown 6 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
Registrar easyDNS Technologies Inc.
Created December 14, 1995 (30 years, 9 months ago)
Expires December 13, 2030 (4 years, 9 months)
Last Updated July 8, 2025
Name Servers ns3.archive.org, ns1.archive.org, ns2.archive.org, ns-global.kjsl.com, ns0036.secondary.cloudflare.com, ns0208.secondary.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 207.241.224.2
ASN AS7941 (INTERNET-ARCHIVE - Internet Archive, US)
Provider INTERNET-ARCHIVE - Internet Archive, US
Data source: rdap (0.3s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more ▾

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

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

Connection waterfall

DNS Lookup 4 ms TCP Connect 6 ms TLS Handshake 10 ms Server Processing 6 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