Skip to content
https://apple.co

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
77
GRADE
C
FIX
0
REVIEW
6
PASS
3
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
3 PASS 6 REVIEW
B
Redirect Chain
2 redirect(s), 214 ms total
REVIEW
2 redirect(s), 214 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
HTTP to HTTPS redirect present
Info::
WWW normalization redirect
Warning::
2-hop chain could be reduced to 1 hop
Redirect directly from https://apple.co to https://www.apple.com/
Info::
Cross-domain redirect detected

https://apple.co

147 ms · HTTP/1.1

301

http://www.apple.com/

39 ms · HTTP/1.1

301

https://www.apple.com/

28 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://apple.co301147 msHTTP/1.1nginx
2http://www.apple.com/30139 msHTTP/1.1AkamaiGHost
3https://www.apple.com/20028 msHTTP/1.1Apple

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

Redirect directly from https://apple.co to https://www.apple.com/

Why this matters

Redirect chain could be flattened to one hop — server config tweak removes intermediate latency.

Source: web.dev

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
Crawlability
Action
robots.txt present, sitemap with 0 URLs
REVIEW
robots.txt present, sitemap with 0 URLs
Info::
robots.txt is present
Got: 123 bytes
Info::
sitemap.xml is present
Warning::
sitemap.xml contains invalid XML
Search engines may not be able to parse the sitemap. Fix XML validation errors.
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.

Search engines may not be able to parse the sitemap. Fix XML validation errors.

Why this matters

An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.

Learn more

Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.

Source: sitemaps.org / Google Search Central

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 123 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
# Welcome to Bitly =)
# robots welcome;
# API documentation can be found at https://dev.bitly.com/
User-Agent: *
Disallow:

sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML No
B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 301 Expected: 301 redirect to HTTPS

www / non-www

301https://www.apple.co/
200https://apple.co/

Preferred variant: non-www

HTTP → HTTPS

301http://apple.co/ http://www.apple.com/

HTTP version does not redirect to HTTPS

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

Certificate validity

56
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
B
CDN & Delivery
Google Cloud CDN
REVIEW
Google Cloud CDN
Info::
Site is served via Google Cloud CDN CDN
Got: via: 1.1 google, 1.1 google
CDN Detected: Google Cloud CDN
Provider Google Cloud CDN Evidence via: 1.1 google, 1.1 google
A+
DNS Records
2 A records, 28 ms lookup
PASS
2 A records, 28 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 67.199.248.12, 67.199.248.13
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: c.ns.apple.com, d.ns.apple.com, a.ns.apple.com, b.ns.apple.com
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: 28 ms
Got: 28 ms
A67.199.248.12, 67.199.248.13
AAAA
CNAME
NSc.ns.apple.com, d.ns.apple.com, a.ns.apple.com, b.ns.apple.com
MX
TXT
google-site-verification=8CjRhCdF3tjhpGuWnJcQqwITHAnZ_D5hmO3Dan4Q20c
facebook-domain-verification=bbkulh2r7rxdgt6bg48kw44344lj3d
CAALookup not available with standard resolver
Resolved in 28 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.

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+
Domain Intelligence
apple.co — via Nom-iq Ltd. dba COM LAUDE, 16 years, 4 months old, hosted on Google Cloud
PASS
apple.co — via Nom-iq Ltd. dba COM LAUDE, 16 years, 4 months old, hosted on Google Cloud
Info::
Domain registered until Feb 23, 2027 (10 months remaining)
Info::
Registrar: Nom-iq Ltd. dba COM LAUDE
Info::
Registrar lock is enabled
Domain cannot be transferred without explicit unlock from the registrar. This protects against unauthorized transfers.
Info::
Hosting: Google Cloud
Got: AS396982
Domain expiry

222 days

February 23, 2027

SSL certificate

56 days

Issued by Apple Inc.

Domain age

16 years, 4 months

Registered February 24, 2010

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Google Cloud

ASN AS396982

67.199.248.13

Registrar

Nom-iq Ltd. dba COM LAUDE

Locked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar Nom-iq Ltd. dba COM LAUDE
Created February 24, 2010 (16 years, 4 months ago)
Expires February 23, 2027 (10 months)
Last Updated February 24, 2026
Name Servers d.ns.apple.com, a.ns.apple.com, b.ns.apple.com, c.ns.apple.com
Hosting
IP Address 67.199.248.13
ASN AS396982 (GOOGLE-CLOUD-PLATFORM - Google LLC, US)
Provider Google Cloud
Data source: whois (0.8s)

Domain cannot be transferred without explicit unlock from the registrar. This protects against unauthorized transfers.

Why this matters

Registrar lock (clientTransferProhibited et al.) prevents unauthorized domain transfers — strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

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

Connection waterfall

DNS Lookup 27 ms TCP Connect 17 ms TLS Handshake 24 ms Server Processing 111 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