Skip to content
https://coca-cola.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
80
GRADE
B
FIX
2
REVIEW
3
PASS
4
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
4 PASS 3 REVIEW 2 FIX
D
Redirect Chain
Action
3 redirect(s), 732 ms total
FIX
3 redirect(s), 732 ms total
Warning::
3 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::
3-hop chain could be reduced to 1 hop
Redirect directly from https://coca-cola.com to https://www.coca-cola.com/fr/fr
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://www.coca-cola.com/
Info::
Redirect overhead: 732 ms total
Got: 732 ms

https://coca-cola.com

492 ms · HTTP/1.1

301

http://www.coca-cola.com/

39 ms · HTTP/1.1

301

https://www.coca-cola.com/

87 ms · HTTP/1.1

302

https://www.coca-cola.com/fr/fr

115 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://coca-cola.com301492 msHTTP/1.1Apache/2.4.59 ()
2http://www.coca-cola.com/30139 msHTTP/1.1CEP
3https://www.coca-cola.com/30287 msHTTP/1.1CEP
4https://www.coca-cola.com/fr/fr200115 msHTTP/1.1CEP

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://coca-cola.com to https://www.coca-cola.com/fr/fr

Why this matters

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

Source: web.dev

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

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

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

302https://www.coca-cola.com/
200https://coca-cola.com/

Preferred variant: non-www

HTTP → HTTPS

301http://coca-cola.com/ http://www.coca-cola.com/

HTTP version does not redirect to HTTPS

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

Certificate validity

288
days left
0d 30d 60d 90d+

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • 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, 32 ms lookup
PASS
1 A records, 32 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 52.14.144.171
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns1-09.azure-dns.com, ns4-09.azure-dns.info, ns2-09.azure-dns.net, ns3-09.azure-dns.org
Info::
2 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: 32 ms
Got: 32 ms
A52.14.144.171
AAAA
CNAME
NSns1-09.azure-dns.com, ns4-09.azure-dns.info, ns2-09.azure-dns.net, ns3-09.azure-dns.org
MX
10 mxb-0037a502.gslb.pphosted.com
10 mxa-0037a502.gslb.pphosted.com
TXT
brevo-code:e4e807ee6f41785447fa24bf45c4ab49
{DE9F-6E17-A88C-D531-18CF-47EC-CDB5-D7FC}
SPF v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com -all
atlassian-domain-verification=v9EdLa37Af1JINLF0pHBpd6xit6uXKfuFAc1QRwcBQCIRN9Pfu...
knowbe4-site-verification=9a96b28c57205f37a147be9b77a94b54
{docusign=37be6a2b-4b3d-4878-8a87-d98e7b894ccf}
msfpkey=eney6bhm0k5pjew13vussvsn
docusign=37be6a2b-4b3d-4878-8a87-d98e7b894ccf
docusign=41136f26-cd9f-4103-ae44-fc36db692f42
8od2lsk7qrgjq6i824bqhrfifl
AD3E-5EA9-09CF-6C47-9257-E26C-5208-F2B5
4E61-7F59-700C-3A33-DA4D-C579-5188-6042
DE9F-6E17-A88C-D531-18CF-47EC-CDB5-D7FC
tgg64854dfe846ngu1td7eemjv
https://cocacola.campaign.adobe.com
MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCO0+Po97e4YISVnNydWPZ9DRKMEapeD5/3BK0DHHhH...
CAALookup not available with standard resolver
Resolved in 32 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+
Crawlability
robots.txt present, sitemap with 154 URLs
PASS
robots.txt present, sitemap with 154 URLs
Info::
robots.txt is present
Got: 184 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 154 entries
Info::
Sitemap index with 154 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 184 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /*/configuration
Disallow: /*/configuration/*
Disallow: /*/login
Disallow: /*/token-exchange
Sitemap: https://www.coca-cola.com/content/onexp.sitemap-index.xml

sitemap.xml 200 OK
Type Sitemap Index URLs 154 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
coca-cola.com — via MarkMonitor Inc., 31 years, 11 months old, hosted on AWS
PASS
coca-cola.com — via MarkMonitor Inc., 31 years, 11 months old, hosted on AWS
Info::
Domain registered until Oct 13, 2026 (5 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: 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.
Info::
Hosting: AWS
Got: AS16509
Domain expiry

93 days

October 13, 2026

SSL certificate

288 days

Issued by Amazon

Domain age

31 years, 11 months

Registered October 14, 1994

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

52.14.144.171

Registrar

MarkMonitor Inc.

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 MarkMonitor Inc.
Created October 14, 1994 (31 years, 11 months ago)
Expires October 13, 2026 (5 months)
Last Updated September 11, 2025
Name Servers ns1-09.azure-dns.com, ns2-09.azure-dns.net, ns3-09.azure-dns.org, ns4-09.azure-dns.info
DNSSEC Not enabled
Hosting
IP Address 52.14.144.171
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.3s)

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

Connection waterfall

DNS Lookup 34 ms TCP Connect 116 ms TLS Handshake 235 ms Server Processing 120 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