Skip to content
https://android.com

Infrastructure

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

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://android.com/ https://www.android.com/

Consistent

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

Certificate validity

59
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, 23 ms lookup
PASS
1 A records, 23 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 142.251.209.36
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: 2a00:1450:4002:406::2004
Info::
4 nameserver(s) configured
Got: ns3.google.com, ns2.google.com, ns1.google.com, ns4.google.com
Info::
7 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: 23 ms
Got: 23 ms
A142.251.209.36
AAAA2a00:1450:4002:406::2004
CNAME
NSns3.google.com, ns2.google.com, ns1.google.com, ns4.google.com
MX
10 aspmx.l.google.com
20 alt1.aspmx.l.google.com
20 alt2.aspmx.l.google.com
30 aspmx2.googlemail.com
30 aspmx4.googlemail.com
30 aspmx5.googlemail.com
30 aspmx3.googlemail.com
TXT
facebook-domain-verification=gj228nttbx7jhjxt8nywtlhoaf97eh
SPF v=spf1 include:_spf.google.com ~all
CAALookup not available with standard resolver
Resolved in 23 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), 287 ms total
PASS
1 redirect(s), 287 ms total
Info::
Single redirect
Got: https://android.com → https://www.android.com/ (301)
Info::
WWW normalization redirect

https://android.com

120 ms · HTTP/1.1

301

https://www.android.com/

167 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://android.com301120 msHTTP/1.1sffe
2https://www.android.com/200167 msHTTP/1.1sffe

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (33 ms)
PASS
IPv6 reachable (33 ms)
Info::
IPv6 is configured and reachable at 2a00:1450:4002:406::2004
Got: 33 ms connect
IPv6 Ready
AAAA Records 2a00:1450:4002:406::2004 Connection Reachable (33 ms)
A+
Crawlability
robots.txt present, sitemap with 7 URLs
PASS
robots.txt present, sitemap with 7 URLs
Info::
robots.txt is present
Got: 1485 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 7 entries
Info::
Sitemap index with 7 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1485 B Sitemaps referenced 1 User-agents Applebot, GPTBot, anthropic-ai, cohere-ai, CCBot, ClaudeBot, MistralAI-User, Applebot-Extended, YouBot, *, OAI-SearchBot, Google-Extended, Diffbot, PerplexityBot, Claude-SearchBot Blocking No — crawling allowed
User-Agent: *
Disallow: /search
Disallow: /404
Disallow: /payapp/
Disallow: /results/

User-agent: GPTBot
Disallow: /search
Disallow: /404
Disallow: /payapp/
Disallow: /results/

User-agent: OAI-SearchBot
Disallow: /search
Disallow: /404
Disallow: /payapp/
Disallow: /results/

User-agent: Google-Extended
Disallow: /search
Disallow: /404
Disallow: /payapp/
Disallow: /results/

User-agent: PerplexityBot
Disallow: /search
Disallow: /404
Disallow: /payapp/
Disallow: /results/

User-agent: ClaudeBot
Disallow: /search
Disallow: /404
Disallow: /payapp/
Disallow: /results/

User-agent: Claude-SearchBot
Disallow: /search
Disallow: /404
Disallow: /payapp/
Disallow: /results/

User-agent: anthropic-ai
Disallow: /search
Disallow: /404
Disallow: /payapp/
Disallow: /results/

User-agent: cohere-ai
Disallow: /search
Disallow: /404
Disallow: /payapp/
Disallow: /results/

User-agent: CCBot
Disallow: /search
Disallow: /404
Disallow: /payapp/
Disallow: /results/

User-agent: Diffbot
Disallow: /search
Disallow: /404
Disallow: /payapp/
Disallow: /results/

User-agent: Applebot-Extended
Disallow: /search
Disallow: /404
Disallow: /payapp/
Disallow: /results/

User-agent: Applebot
Disallow: /search
Disallow: /404
Disallow: /payapp/
Disallow: /results/

User-agent: YouBot
Disallow: /search
Disallow: /404
Disallow: /payapp/
Disallow: /results/

User-agent: MistralAI-User
Disallow: /search
Disallow: /404
Disallow: /payapp/
Disallow: /results/

Sitemap: https://www.android.com/sitemap.xml
A
Domain Intelligence
android.com — via MarkMonitor Inc., 29 years, 2 months old
PASS
android.com — via MarkMonitor Inc., 29 years, 2 months old
Warning::
Domain expires in 66 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Jun 22, 2026
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: MarkMonitor 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.
Domain expiry

EXPIRED

June 22, 2026

SSL certificate

59 days

Issued by Google Trust Services

Domain age

29 years, 2 months

Registered June 23, 1997

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2a00:1450:4002:406::2004

Registrar

MarkMonitor Inc.

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Domain has EXPIRED — renew immediately to avoid total site outage
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar MarkMonitor Inc.
Created June 23, 1997 (29 years, 2 months ago)
Expires June 22, 2026 (2 months)
Last Updated May 21, 2025
Name Servers ns1.google.com, ns2.google.com, ns3.google.com, ns4.google.com
DNSSEC Not enabled
Hosting
IP Address 2a00:1450:4002:406::2004
Data source: rdap (0.1s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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

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

Connection waterfall

DNS Lookup 23 ms TCP Connect 33 ms TLS Handshake 55 ms Server Processing 54 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