Skip to content
https://archive-it.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
2
REVIEW
3
PASS
4
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
4 PASS 3 REVIEW 2 FIX
F
HTTP Probe Timing
Action
Total 7974 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
FIX
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
159 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
7.28 s
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
370 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
7.97 s
Total Time Total request time from DNS lookup through full response.
7.97 s

Connection waterfall

DNS Lookup 159 ms TCP Connect 7.28 s TLS Handshake 370 ms Server Processing 164 ms Content Transfer 0 ms
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

C
URL Variants
Action
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
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

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

Inconsistent — duplicate content risk

HTTP → HTTPS

302http://archive-it.org/ https://archive-it.org/

Use 301 (permanent) instead of 302 (temporary)

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

Certificate validity

57
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
2 A records, 163 ms lookup
PASS
2 A records, 163 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 207.241.225.8, 207.241.232.8
Info::
No IPv6 (AAAA) records
Info::
3 nameserver(s) configured
Got: ns1.archive.org, ns3.archive.org, ns2.archive.org
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::
SPF record present in TXT
Info::
DNS resolution time: 163 ms
Got: 163 ms
A207.241.225.8, 207.241.232.8
AAAA
CNAME
NSns1.archive.org, ns3.archive.org, ns2.archive.org
MX
TXT
google-site-verification=DLn1LsAZ0MB67DfavyE7ViNb_MV8TyE2EstuO5zuQfk
SPF v=spf1 a:mail.archive.org ip4:207.241.224.6/32 ~all
5inm1q8n5espqouk6mhcddhjo6
google-site-verification=4Te5UU7D4fVJozJSLaT2NZygTJLAamjSTD-s-1txkFM
CAALookup not available with standard resolver
Resolved in 163 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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://archive-it.org

https://archive-it.org

483 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://archive-it.org200483 msHTTP/1.1
A
Crawlability
robots.txt present, sitemap with 0 URLs
PASS
robots.txt present, sitemap with 0 URLs
Info::
robots.txt is present
Got: 470 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Warning::
sitemap.xml is empty — no URLs found
An empty sitemap provides no value. Add <url> entries for your pages.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

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 470 B Sitemaps referenced 0 User-agents Blocking No — crawling allowed
<html>
    <head>
        <title>Rate limit reached</title>
    </head>
    <body>
        <div style="text-align: center;">
            <p>
                You've reached the limit for the number of requests that can be made in a short period of time. Please wait a moment and try again.
                If you believe this message was shown in error or need assistance, please contact us at Aitratelimit@archive.org
            </p>
        </div>
    </body>
</html>

sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML Yes
A+
Domain Intelligence
archive-it.org — via easyDNS Technologies Inc., 21 years, 2 months old, hosted on INTERNET-ARCHIVE - Internet Archive, US
PASS
archive-it.org — via easyDNS Technologies Inc., 21 years, 2 months old, hosted on INTERNET-ARCHIVE - Internet Archive, US
Info::
Domain registered until Jun 1, 2028 (2 years, 1 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.
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.
Info::
Hosting: INTERNET-ARCHIVE - Internet Archive, US
Got: AS7941
Domain expiry

684 days

June 1, 2028

SSL certificate

57 days

Issued by Let's Encrypt

Domain age

21 years, 2 months

Registered June 1, 2005

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

INTERNET-ARCHIVE - Internet Archive, US

ASN AS7941

207.241.232.8

Registrar

easyDNS Technologies Inc.

Unlocked 3 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
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar easyDNS Technologies Inc.
Created June 1, 2005 (21 years, 2 months ago)
Expires June 1, 2028 (2 years, 1 months)
Last Updated July 8, 2025
Name Servers ns3.archive.org, ns1.archive.org, ns2.archive.org
DNSSEC Not enabled
Hosting
IP Address 207.241.232.8
ASN AS7941 (INTERNET-ARCHIVE - Internet Archive, US)
Provider INTERNET-ARCHIVE - Internet Archive, US
Data source: rdap (0.6s)

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

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback