Skip to content
https://addtoany.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
79
GRADE
C
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Santa Clara, United States
301 Moved Permanently
Checks
9
4 PASS 4 REVIEW 1 FIX
F
IPv6 Readiness
Action
IPv6 records exist but unreachable
FIX
IPv6 records exist but unreachable
Warning::
IPv6 DNS records exist but server is not reachable
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Got: 2606:4700:10::6814:14c0, 2606:4700:10::ac42:abac
Info::
IPv6 connection error
Got: dial tcp6 [2606:4700:10::6814:14c0]:443: connect: network is unreachable
IPv6 Misconfigured
AAAA Records 2606:4700:10::6814:14c0, 2606:4700:10::ac42:abac Connection UNREACHABLE

Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.

Why this matters

Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.

Learn more

Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.

Source: RFC 8305 (Happy Eyeballs)

B
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 308 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

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 308 B Sitemaps referenced 0 User-agents *, facebookexternalhit Blocking No — crawling allowed
User-agent: *

Disallow: /add_to/

Disallow: /add_to/*

Disallow: /email?*

Disallow: /share?*

Disallow: /share_save?*

Disallow: /subscribe?*


User-agent: facebookexternalhit

Disallow: /add_to/

Disallow: /add_to/*

Disallow: /email?*

Disallow: /share?*

Disallow: /share_save?*

Disallow: /subscribe?*
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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.addtoany.com/
200https://addtoany.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://addtoany.com/ https://addtoany.com/

Consistent

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

Certificate validity

88
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
B
CDN & Delivery
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: SJC)
Got: cf-ray: 9ed4f025cfcfaf0d-SJC
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9ed4f025cfcfaf0d-SJC
A+
DNS Records
2 A records, 9 ms lookup
PASS
2 A records, 9 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.20.20.192, 172.66.171.172
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:10::6814:14c0, 2606:4700:10::ac42:abac
Info::
2 nameserver(s) configured
Got: bob.ns.cloudflare.com, lily.ns.cloudflare.com
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: 9 ms
Got: 9 ms
A104.20.20.192, 172.66.171.172
AAAA2606:4700:10::6814:14c0, 2606:4700:10::ac42:abac
CNAME
NSbob.ns.cloudflare.com, lily.ns.cloudflare.com
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 alt3.aspmx.l.google.com
10 alt4.aspmx.l.google.com
TXT
google-site-verification=ZWgtkbZd-14eP41i3bjh_VyKfgoUkIXt0h6GE_-jt6w
SPF v=spf1 include:_spf.google.com include:spf.mtasv.net include:sites.nearlyfreespe...
CAALookup not available with standard resolver
Resolved in 9 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), 58 ms total
PASS
1 redirect(s), 58 ms total
Info::
Single redirect
Got: https://addtoany.com → https://www.addtoany.com/ (301)
Info::
WWW normalization redirect

https://addtoany.com

31 ms · HTTP/1.1

301

https://www.addtoany.com/

27 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://addtoany.com30131 msHTTP/1.1cloudflare
2https://www.addtoany.com/20027 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
Domain Intelligence
addtoany.com — via Cloudflare, Inc., 20 years, 4 months old, hosted on Cloudflare
PASS
addtoany.com — via Cloudflare, Inc., 20 years, 4 months old, hosted on Cloudflare
Info::
Domain registered until Mar 10, 2027 (10 months remaining)
Info::
DNSSEC is enabled
Info::
Registrar: Cloudflare, 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: Cloudflare
Got: AS13335
Domain expiry

240 days

March 10, 2027

SSL certificate

88 days

Issued by Google Trust Services

Domain age

20 years, 4 months

Registered March 10, 2006

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

104.20.20.192

Registrar

Cloudflare, Inc.

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Cloudflare, Inc.
Created March 10, 2006 (20 years, 4 months ago)
Expires March 10, 2027 (10 months)
Last Updated February 8, 2026
Name Servers bob.ns.cloudflare.com, lily.ns.cloudflare.com
DNSSEC Enabled
Hosting
IP Address 104.20.20.192
ASN AS13335 (CLOUDFLARENET - Cloudflare, Inc., US)
Provider Cloudflare
Data source: rdap (0.2s)

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 30 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
9 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
4 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
8 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
30 ms
Total Time Total request time from DNS lookup through full response.
30 ms

Connection waterfall

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