Skip to content
https://mcdonalds.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Amsterdam, Netherlands
301 Moved Permanently
Checks
9
5 PASS 3 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
Redirect Chain
2 redirect(s), 336 ms total
REVIEW
2 redirect(s), 336 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://www.mcdonalds.com/

https://mcdonalds.com

283 ms · HTTP/1.1

301

https://www.mcdonalds.com/

20 ms · HTTP/1.1

302

https://www.mcdonalds.com/nl/nl-nl.html

33 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://mcdonalds.com301283 msHTTP/1.1Apache
2https://www.mcdonalds.com/30220 msHTTP/1.1AkamaiGHost
3https://www.mcdonalds.com/nl/nl-nl.html20033 msHTTP/1.1

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

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

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
TLS Certificate Expiry & Recommendations
111 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

111
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, 13 ms lookup
PASS
1 A records, 13 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 44.208.147.61
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: ns-1445.awsdns-52.org, ns-1685.awsdns-18.co.uk, ns-76.awsdns-09.com, ns-840.awsdns-41.net
Info::
1 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: 13 ms
Got: 13 ms
A44.208.147.61
AAAA
CNAME
NSns-1445.awsdns-52.org, ns-1685.awsdns-18.co.uk, ns-76.awsdns-09.com, ns-840.awsdns-41.net
MX
10 sesmail.mcdonalds.com
TXT
_d3o1mforjeyzo5o6hpvgssdka31obmm
amazonses:24YzB2l981UTyShDCxFnkb9onqr7EICEKxuiXuT0JsE=
amazonses:2yrtLrBZnUnx460KXwTUxZ01Ud5ZLaiIxLObRgOROXw=
amazonses:w61li6pZNv7ThE859iAQ4pB3r+/V0o3raZ+l+MjGGUM=
atlassian-domain-verification=xr1imvOStLlJuzF56e9Es6XYgxsJ/g37cNaRq9ELyWsnXQwPY/...
bu6vtqae5ivnlcygdwdv5tlv3ouelhgc._domainkey.us.mcdonalds.com bu6vtqae5ivnlcygdwd...
facebook-domain-verification=kgdg0z0q8plsrhydjn7cfc4060qs7e
fastly-domain-delegation-00492901-5H2jV3eG3-2025-08-19
fcr34w4ydxvjlpfd378b6gy13sp70nl7
globalsign-domain-verification=sQ-XKBfUo5JDJd8xvoOg94ZQ0q4WWtarHMUXPLXva-
google-site-verification=1l2IiUZudhFss5aXQBmrC0xBBRT3SDEZcMHyKrwitWw
google-site-verification=8P1qbyxjsZuEtxjuD8vE7jaw73fnw7996n0mmon34wQ
google-site-verification=EnEJy4OfSOZcfOxa0vglOOBdiZyRTGBoa0jFKvz64hM
google-site-verification=IUH4L9-jC3u-HQprdyL6jS-GBE4RgbW59jup9wd8nts
google-site-verification=dWgCJy1wnoMQHUrevkULexZ6C4F67zRJRyhd2BD_0JM
google-site-verification=iBg7YjcBWxqMsH0VIfkAY9LwQ9Q6HNstaznRQmt-JBo
google-site-verification=rbTHUfWUluMmGA18BckcrPVjVE2u58QQF0CE8DcHjv4
i3ercugito3yrnvxyidnkrs3ronr4jyy._domainkey.us.mcdonalds.com i3ercugito3yrnvxyid...
m44vwjmxlvh26mg9nf08qshrn8rzy3s3
m4gcv5ds4osmwyunlxglow4zhbi2av7n._domainkey.us.mcdonalds.com m4gcv5ds4osmwyunlxg...
SPF v=spf1 include:spf.mailjet.com include:_spf.q4press.com include:amazonses.com in...
CAALookup not available with standard resolver
Resolved in 13 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 9717 URLs
PASS
robots.txt present, sitemap with 9717 URLs
Info::
robots.txt is present
Got: 3903 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 9717 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 3903 B Sitemaps referenced 58 User-agents SiteAuditBot, * Blocking No — crawling allowed
User-agent: SiteAuditBot
Disallow:  
User-agent: *
Allow: *.js
Allow: *.css
Allow: *.gif
Allow: *.png
Allow: /.well-known/apple-app-site-association
Allow: /.well-known/assetlinks.json
Disallow: /config/
Disallow: /utility/
Disallow: /content/prelaunch/
Disallow: /prelaunch/
Disallow: /us/en-us/wifi-desktop.html
Sitemap: https://www.mcdonalds.com/us/en-us/restaurant-sitemap.xml
Sitemap: https://www.mcdonalds.com/us/es-us/restaurant-sitemap.xml
Sitemap: https://www.mcdonalds.com/nl/nl-nl/restaurant-sitemap.xml
Sitemap: https://www.mcdonalds.com/om/en-om/restaurant-sitemap.xml
Sitemap: https://www.mcdonalds.com/om/ar-om/restaurant-sitemap.xml
Sitemap: https://www.mcdonalds.com/tw/zh-tw/restaurant-sitemap.xml
Sitemap: https://www.mcdonalds.com/no/nb-no/restaurant-sitemap.xml
Sitemap: https://www.mcdonalds.com/dk/da-dk/restaurant-sitemap.xml
Sitemap: https://www.mcdonalds.com/ie/en-ie/restaurant-sitemap.xml
Sitemap: https://www.mcdonalds.com/ae/en-ae/restaurant-sitemap.xml
Sitemap: https://www.mcdonalds.com/ae/ar-ae/restaurant-sitemap.xml
Sitemap: https://www.mcdonalds.com/bh/en-bh/restaurant-sitemap.xml
Sitemap: https://www.mcdonalds.com/gb/en-gb/restaurant-sitemap.xml
Sitemap: https://www.mcdonalds.com/ca/en-ca/restaurant-sitemap.xml
Sitemap: https://www.mcdonalds.com/ca/fr-ca/restaurant-sitemap.xml
Sitemap: https://www.mcdonalds.com/fi/fi-fi/restaurant-sitemap.xml
Sitemap: https://www.mcdonalds.com/de/de-de/restaurant-sitemap.xml
Sitemap: https://www.mcdonalds.com/se/sv-se/restaurant-sitemap.xml
Sitemap: https://www.mcdonalds.com/qa/en-qa/restaurant-sitemap.xml
Sitemap: https://www.mcdonalds.com/qa/ar-qa/restaurant-sitemap.xml
Sitemap: https://www.mcdonalds.com/au/en-au/restaurant-sitemap.xml
Sitemap: https://www.mcdonalds.com/kw/ar-kw/restaurant-sitemap.xml
Sitemap: https://www.mcdonalds.com/kw/en-kw/restaurant-sitemap.xml
Sitemap: https://www.mcdonalds.com/sa/ar-sa/riyadh/restaurant-sitemap.xml
Sitemap: https://www.mcdonalds.com/sa/ar-sa/jeddah/restaurant-sitemap.xml
Sitemap: https://www.mcdonalds.com/us/en-us.sitemap.xml
Sitemap: https://www.mcdonalds.com/us/es-us.sitemap.xml
Sitemap: https://www.mcdonalds.com/aag/en-us.sitemap.xml
Sitemap: https://www.mcdonalds.com/no/nb-no.sitemap.xml
Sitemap: https://www.mcdonalds.com/ie/en-ie.sitemap.xml
Sitemap: https://www.mcdonalds.com/sa/en-sa/jeddah.sitemap.xml
Sitemap: https://www.mcdonalds.com/sa/en-sa/riyadh.sitemap.xml
Sitemap: https://www.mcdonalds.com/sa/ar-sa/jeddah.sitemap.xml
Sitemap: https://www.mcdonalds.com/sa/ar-sa/riyadh.sitemap.xml
Sitemap: https://www.mcdonalds.com/ca/en-ca.sitemap.xml
Sitemap: https://www.mcdonalds.com/ca/fr-ca.sitemap.xml
Sitemap: https://www.mcdonalds.com/om/en-om.sitemap.xml
Sitemap: https://www.mcdonalds.com/om/ar-om.sitemap.xml
Sitemap: https://www.mcdonalds.com/nl/nl-nl.sitemap.xml
Sitemap: https://www.mcdonalds.com/nl/nl-nl/McDelivery/McDelivery1.sitemap.xml
Sitemap: https://www.mcdonalds.com/ae/en-ae.sitemap.xml
Sitemap: https://www.mcdonalds.com/ae/ar-ae.sitemap.xml
Sitemap: https://www.mcdonalds.com/de/de-de.sitemap.xml
Sitemap: https://www.mcdonalds.com/fi/fi-fi.sitemap.xml
Sitemap: https://www.mcdonalds.com/dk/da-dk.sitemap.xml
Sitemap: https://www.mcdonalds.com/se/sv-se.sitemap.xml
Sitemap: https://www.mcdonalds.com/ch/de-ch.sitemap.xml
Sitemap: https://www.mcdonalds.com/ch/fr-ch.sitemap.xml
Sitemap: https://www.mcdonalds.com/ch/it-ch.sitemap.xml
Sitemap: https://www.mcdonalds.com/bh/en-bh.sitemap.xml
Sitemap: https://www.mcdonalds.com/bh/ar-bh.sitemap.xml
Sitemap: https://www.mcdonalds.com/qa/en-qa.sitemap.xml
Sitemap: https://www.mcdonalds.com/qa/ar-qa.sitemap.xml
Sitemap: https://www.mcdonalds.com/ua/uk-ua.sitemap.xml
Sitemap: https://www.mcdonalds.com/kw/en-kw.sitemap.xml
Sitemap: https://www.mcdonalds.com/kw/ar-kw.sitemap.xml
Sitemap: https://www.mcdonalds.com/au/en-au.sitemap.xml
Sitemap: https://www.mcdonalds.com/hu/hu-hu.sitemap.xml

A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

302https://www.mcdonalds.com/
200https://mcdonalds.com/

Preferred variant: non-www

HTTP → HTTPS

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

Consistent

A
Domain Intelligence
mcdonalds.com — via CSC Corporate Domains, Inc., 32 years, 2 months old, hosted on AWS
PASS
mcdonalds.com — via CSC Corporate Domains, Inc., 32 years, 2 months old, hosted on AWS
Warning::
Domain expires in 80 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Jul 11, 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: CSC Corporate Domains, 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: AS14618
Domain expiry

EXPIRED

July 11, 2026

SSL certificate

111 days

Issued by DigiCert Inc

Domain age

32 years, 2 months

Registered July 12, 1994

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS14618

44.208.147.61

Registrar

CSC Corporate Domains, 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 CSC Corporate Domains, Inc.
Created July 12, 1994 (32 years, 2 months ago)
Expires July 11, 2026 (2 months)
Last Updated July 7, 2025
Name Servers ns-1445.awsdns-52.org, ns-1685.awsdns-18.co.uk, ns-76.awsdns-09.com, ns-840.awsdns-41.net
DNSSEC Not enabled
Hosting
IP Address 44.208.147.61
ASN AS14618 (AMAZON-AES - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.2s)

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

Connection waterfall

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