Infrastructure - https://www.apple.com BeaverCheck Audit

B

DNS Records

1 A records, 36 ms lookup

REVIEW

1 A records, 36 ms lookup

Resolves to 1 IPv4 address(es)

Got: 2.20.169.45

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

Has 2 IPv6 (AAAA) record(s)

Got: 2a02:26f0:1380:293::1aca, 2a02:26f0:1380:2ac::1aca

CNAME record at zone apex

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Got: www-apple-com.v.aaplimg.com

No NS records found

No MX records — email not configured via DNS

No SPF record found in TXT records

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

DNS resolution time: 36 ms

Got: 36 ms

A	2.20.169.45
AAAA	2a02:26f0:1380:293::1aca, 2a02:26f0:1380:2ac::1aca
CNAME	www-apple-com.v.aaplimg.com
NS	—
MX	—
TXT	—
CAA	Lookup not available with standard resolver

Resolved in 36 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

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more ▾

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

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)

B

DNSSEC

Unsigned (DNSSEC not deployed)

REVIEW

Unsigned (DNSSEC not deployed)

DNSSEC is not deployed

The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).

B

CAA Records

No CAA records (any CA may issue certificates)

REVIEW

No CAA records (any CA may issue certificates)

No CAA records published

Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.

B

Reverse DNS

0/3 IPs match cert SAN

REVIEW

0/3 IPs match cert SAN

PTR for 2.20.169.45 does not match any cert SAN: a2-20-169-45.deploy.static.akamaitechnologies.com

Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.

PTR for 2a02:26f0:1380:293::1aca does not match any cert SAN: g2a02-26f0-1380-0293-0000-0000-0000-1aca.deploy.static.akamaitechnologies.com

Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.

PTR for 2a02:26f0:1380:2ac::1aca does not match any cert SAN: g2a02-26f0-1380-02ac-0000-0000-0000-1aca.deploy.static.akamaitechnologies.com

Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.

B

TLS Certificate Expiry & Recommendations

41 days until leaf cert expires — 2 issues to address

REVIEW

Certificate validity

41

days left

0d 30d 60d 90d+

Recommended actions

Submit your domain to hstspreload.org to be added to the Chrome preload list
Enable DNSSEC on your domain for DNS spoofing protection

B

CDN & Delivery

Akamai

REVIEW

Akamai

Document is served via Akamai CDN

Got: 2.20.169.45 in 2.16.0.0/13 (Akamai)

Document served via CDN: Akamai

Provider Akamai Evidence 2.20.169.45 in 2.16.0.0/13 (Akamai)

B

CDN Cache Observability

No CDN cache-status headers in the response

REVIEW

No CDN cache-status headers in the response

Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.

B

Operational Status Page

No status page link detected

REVIEW

No status page link detected

No operational status page link detected

Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.

A+

Subdomain Takeover

No subdomain takeover risk detected

PASS

No subdomain takeover risk detected

CNAME does not point at a known takeover-able service

A+

Multi-Resolver DNS Speed

Mean 15ms across 3 resolvers (spread 29ms)

PASS

Mean 15ms across 3 resolvers (spread 29ms)

Quad9: 0ms

Got: 0ms via 9.9.9.9:53

Cloudflare: 17ms

Got: 17ms via 1.1.1.1:53

Google: 29ms

Got: 29ms via 8.8.8.8:53

A+

Redirect Chain

No redirects — direct access

PASS

No redirects — direct access

Got: https://www.apple.com

https://www.apple.com

96 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://www.apple.com	200	96 ms	HTTP/1.1	Apple

A+

IPv6 Readiness

IPv6 reachable (1 ms)

PASS

IPv6 reachable (1 ms)

IPv6 is configured and reachable at 2a02:26f0:1380:293::1aca, 2a02:26f0:1380:2ac::1aca

Got: 1 ms connect

IPv6 Ready

AAAA Records 2a02:26f0:1380:293::1aca, 2a02:26f0:1380:2ac::1aca Connection Reachable (1 ms)

A+

Crawlability

robots.txt present, sitemap with 47 URLs

PASS

robots.txt present, sitemap with 47 URLs

robots.txt is present

Got: 1018 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 47 entries

Sitemap index with 47 child sitemaps

robots.txt references sitemap

robots.txt 200 OK

Size 1018 B Sitemaps referenced 5 User-agents Sogou spider2, *, Baiduspider, HaoSouSpider, Sogou web spider, Sogou inst spider Blocking No — crawling allowed

# robots.txt for https://www.apple.com/

User-agent: *
Disallow: /*shop/browse/overlay/*
Disallow: /*shop/iphone/payments/overlay/*
Disallow: /cn/*/aow/*
Disallow: /tmall*
Allow: /ac/globalnav/2.0/*/images/ac-globalnav/globalnav/search/* 	

User-agent: Baiduspider
Disallow: /*
Allow: /cn/*
Allow: /cn-edu/*
Allow: /cn-k12/*

User-agent: HaoSouSpider
Disallow: /*
Allow: /cn/*
Allow: /cn-edu/*
Allow: /cn-k12/*

User-agent: Sogou web spider
Disallow: /*
Allow: /cn/*
Allow: /cn-k12/*

User-agent: Sogou inst spider
Disallow: /*
Allow: /cn/*
Allow: /cn-k12/*

User-agent: Sogou spider2
Disallow: /*
Allow: /cn/*
Allow: /cn-k12/*

#DaumWebMasterTool:6ff40e0f09564a9d4e3bc80e7cbde7c196677a2f5f610eb9c029836774f9a8e9:D9a8IEFAzmC/NWsQ3tB0Wg==

Sitemap: https://www.apple.com/shop/sitemap.xml
Sitemap: https://www.apple.com/autopush/sitemap/sitemap-index.xml
Sitemap: https://www.apple.com/newsroom/sitemap.xml
Sitemap: https://www.apple.com/retail/sitemap/sitemap.xml
Sitemap: https://www.apple.com/today/sitemap-index.xml

sitemap.xml 200 OK

Type Sitemap Index URLs 47 entries Valid XML Yes

Child Sitemaps:

A+

URL Variants

www/non-www, trailing slash, HTTP→HTTPS

PASS

www/non-www, trailing slash, HTTP→HTTPS

www/non-www redirect configured correctly (preferred: www)

HTTP correctly redirects to HTTPS permanently

Got: HTTP 301

www / non-www

200https://www.apple.com/

301https://apple.com/

Preferred variant: www

HTTP → HTTPS

301http://www.apple.com/ → https://www.apple.com/

Consistent

A+

Domain Intelligence

apple.com — via Nom-iq Ltd. dba COM LAUDE, 40 years, 3 months old

PASS

apple.com — via Nom-iq Ltd. dba COM LAUDE, 40 years, 3 months old

Domain registered until Feb 20, 2027 (3 months remaining)

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.

Registrar: Nom-iq Ltd. dba COM LAUDE

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

103 days

February 20, 2027

SSL certificate

41 days

Issued by Apple Inc.

Domain age

40 years, 3 months

Registered February 19, 1987

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2620:149:af0::10

Registrar

Nom-iq Ltd. dba COM LAUDE

Unlocked 4 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 Nom-iq Ltd. dba COM LAUDE

Created February 19, 1987 (40 years, 3 months ago)

Expires February 20, 2027 (3 months)

Last Updated February 9, 2026

Name Servers a.ns.apple.com, b.ns.apple.com, c.ns.apple.com, d.ns.apple.com

DNSSEC Not enabled

Hosting

IP Address 2620:149:af0::10

Data source: rdap (0.2s)

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 135 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

PASS

DNS Lookup

22 ms

TCP Connect

17 ms

TLS Handshake

35 ms

Time to First Byte

114 ms

Total Time

135 ms

Connection waterfall

DNS Lookup 22 ms TCP Connect 17 ms TLS Handshake 35 ms Server Processing 40 ms Content Transfer 22 ms

A+

Health Check Endpoint

Health endpoint at https://www.apple.com/health (HTTP 200)

PASS

Health endpoint at https://www.apple.com/health (HTTP 200)

Public health endpoint at https://www.apple.com/health

Got: https://www.apple.com/health