Skip to content
https://www.marriott.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
0
REVIEW
4
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 4 REVIEW
B
DNS Records
1 A records, 33 ms lookup
REVIEW
1 A records, 33 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 2.22.208.105
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Warning::
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: cn-www.marriott.com.edgekey.net
Info::
No NS records found
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: 33 ms
Got: 33 ms
A2.22.208.105
AAAA
CNAMEcn-www.marriott.com.edgekey.net
NS
MX
TXT
CAALookup not available with standard resolver
Resolved in 33 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

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)

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
304 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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
Akamai
REVIEW
Akamai
Info::
Site is served via Akamai CDN
Got: server header
CDN Detected: Akamai
Provider Akamai Evidence server header
A
Redirect Chain
1 redirect(s), 465 ms total
PASS
1 redirect(s), 465 ms total
Info::
Single redirect
Got: https://www.marriott.com → https://www.marriott.com/default.mi (301)

https://www.marriott.com

38 ms · HTTP/1.1

301

https://www.marriott.com/default.mi

426 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.marriott.com30138 msHTTP/1.1AkamaiGHost
2https://www.marriott.com/default.mi200426 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 112 URLs
PASS
robots.txt present, sitemap with 112 URLs
Info::
robots.txt is present
Got: 2643 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 112 entries
Info::
Sitemap index with 112 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 2643 B Sitemaps referenced 1 User-agents Baiduspider, * Blocking No — crawling allowed
# Robots.txt file for HTTPS Marriott.com

#

Sitemap: https://www.marriott.com/sitemap-index.xml

#

User-agent: Baiduspider 

Disallow: /


#

User-agent: *

Disallow: /zh/

Disallow: /einterface/

Disallow: /hotels/newAdaptiveRoomTypePhotoViewer

Disallow: /reservation/availabilitySearch.mi

Disallow: /aries-search/

Disallow: /offers/preview/

Disallow: /search/

Disallow: /en-gb/search/

Disallow: /es/search/

Disallow: /fr/search/

Disallow: /pt-br/search/

Disallow: /id/search/

Disallow: /zh-hk/search/

Disallow: /ja/search/

Disallow: /ko/search/

Disallow: /th/search/

Disallow: /vi/search/

Disallow: /ar/search/

Disallow: /he/search/

Disallow: /da/search/

Disallow: /de/search/

Disallow: /el/search/

Disallow: /it/search/

Disallow: /nl/search/

Disallow: /no/search/

Disallow: /ru/search/

Disallow: /pl-pl/search/

Disallow: /fi/search/

Disallow: /sv/search/

Disallow: /tr-tr/search/

Disallow: /hi/search/

Allow: /search/default.mi

Allow: /en-gb/search/default.mi

Allow: /es/search/default.mi

Allow: /fr/search/default.mi

Allow: /pt-br/search/default.mi

Allow: /id/search/default.mi

Allow: /zh-hk/search/default.mi

Allow: /ja/search/default.mi

Allow: /ko/search/default.mi

Allow: /th/search/default.mi

Allow: /vi/search/default.mi

Allow: /ar/search/default.mi

Allow: /he/search/default.mi

Allow: /da/search/default.mi

Allow: /de/search/default.mi

Allow: /el/search/default.mi

Allow: /it/search/default.mi

Allow: /nl/search/default.mi

Allow: /no/search/default.mi

Allow: /ru/search/default.mi

Allow: /pl-pl/search/default.mi

Allow: /fi/search/default.mi

Allow: /sv/search/default.mi

Allow: /tr-tr/search/default.mi

Allow: /hi/search/default.mi


#

#    /$$      /$$                               /$$             /$$     /$$            /$$$$$$  /$$$$$$$$  /$$$$$$ 

#   | $$$    /$$$                              |__/            | $$    | $$           /$$__  $$| $$_____/ /$$__  $$

#   | $$$$  /$$$$  /$$$$$$   /$$$$$$   /$$$$$$  /$$  /$$$$$$  /$$$$$$ /$$$$$$        | $$  \__/| $$      | $$  \ $$

#   | $$ $$/$$ $$ |____  $$ /$$__  $$ /$$__  $$| $$ /$$__  $$|_  $$_/|_  $$_/        |  $$$$$$ | $$$$$   | $$  | $$

#   | $$  $$$| $$  /$$$$$$$| $$  \__/| $$  \__/| $$| $$  \ $$  | $$    | $$           \____  $$| $$__/   | $$  | $$

#   | $$\  $ | $$ /$$__  $$| $$      | $$      | $$| $$  | $$  | $$ /$$| $$ /$$       /$$  \ $$| $$      | $$  | $$

#   | $$ \/  | $$|  $$$$$$$| $$      | $$      | $$|  $$$$$$/  |  $$$$/|  $$$$/      |  $$$$$$/| $$$$$$$$|  $$$$$$/

#   |__/     |__/ \_______/|__/      |__/      |__/ \______/    \___/   \___/         \______/ |________/ \______/ 

#


sitemap.xml 200 OK
Type Sitemap Index URLs 112 entries Valid XML Yes
Child Sitemaps:
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: www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.marriott.com/
301https://marriott.com/

Preferred variant: www

HTTP → HTTPS

301http://www.marriott.com/ https://www.marriott.com/default.mi

Consistent

A+
Domain Intelligence
marriott.com — via CSC Corporate Domains, Inc., 33 years, 8 months old, hosted on Akamai
PASS
marriott.com — via CSC Corporate Domains, Inc., 33 years, 8 months old, hosted on Akamai
Info::
Domain registered until Jan 4, 2027 (9 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: CSC Corporate Domains, Inc.
Info::
Hosting: Akamai
Got: AS16625
Domain expiry

140 days

January 4, 2027

SSL certificate

304 days

Issued by Sectigo Limited

Domain age

33 years, 8 months

Registered January 5, 1993

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Akamai

ASN AS16625

23.46.188.102

Registrar

CSC Corporate Domains, Inc.

Lock status unknown 8 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
Registrar CSC Corporate Domains, Inc.
Created January 5, 1993 (33 years, 8 months ago)
Expires January 4, 2027 (9 months)
Last Updated December 31, 2025
Name Servers eur1.akam.net, eur3.akam.net, eur4.akam.net, ns1-22.akam.net, ns1-7.akam.net, usc1.akam.net, usc2.akam.net, use4.akam.net
DNSSEC Not enabled
Hosting
IP Address 23.46.188.102
ASN AS16625 (AKAMAI-AS - Akamai Technologies, Inc., US)
Provider Akamai
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

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

Connection waterfall

DNS Lookup 73 ms TCP Connect 1 ms TLS Handshake 6 ms Server Processing 29 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