Skip to content
https://mandarinoriental.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
2
PASS
5
INFO
0
Probed from Sao Paulo, Brazil
301 Moved Permanently
Checks
9
5 PASS 2 REVIEW 2 FIX
F
Redirect Chain
Action
3 redirect(s), 1028 ms total
FIX
3 redirect(s), 1028 ms total
Warning::
3 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1028 ms total
Got: 1028 ms

https://mandarinoriental.com

63 ms · HTTP/1.1

301

https://www.mandarinoriental.com/

138 ms · HTTP/1.1

301

https://www.mandarinoriental.com/en/

6 ms · HTTP/1.1

301

https://www.mandarinoriental.com/en

821 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://mandarinoriental.com30163 msHTTP/1.1
2https://www.mandarinoriental.com/301138 msHTTP/1.1
3https://www.mandarinoriental.com/en/3016 msHTTP/1.1
4https://www.mandarinoriental.com/en200821 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

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

Certificate validity

261
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
A+
DNS Records
1 A records, 180 ms lookup
PASS
1 A records, 180 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 104.104.166.156
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: ns3.p17.dynect.net, ns2.p17.dynect.net, ns1.p17.dynect.net, ns4.p17.dynect.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: 180 ms
Got: 180 ms
A104.104.166.156
AAAA—
CNAME—
NSns3.p17.dynect.net, ns2.p17.dynect.net, ns1.p17.dynect.net, ns4.p17.dynect.net
MX
10 mail.mandarinoriental.com
TXT
SPF v=spf1 -all
d6qjbm30t8jkhf0bbod52bmj64
MS=ms72636301
ok95cmvqe65jfmh6s5bftbvlbp
CAALookup not available with standard resolver
Resolved in 180 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 19 URLs
PASS
robots.txt present, sitemap with 19 URLs
Info::
robots.txt is present
Got: 500 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 19 entries
Info::
Sitemap index with 19 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 500 B Sitemaps referenced 1 User-agents Google-HotelAdsVerifier, Google-HotelAdsVerifier/2.0, * Blocking No — crawling allowed
User-agent: Google-HotelAdsVerifier
Allow: /

User-agent: Google-HotelAdsVerifier/2.0
Allow: /

User-agent: *
Allow: /

Disallow: /*?city=
Disallow: /*?_ga=
Disallow: /*?hotel=
Disallow: /*?hotelCode=
Disallow: /*?os=
Disallow: /*?rate=
Disallow: /*?returnUrl=
Disallow: /*?shs_stream_date=
Disallow: /*?source=
Disallow: /corporate.css?v=
Disallow: /main.js?v=
Disallow: /sitecore/service/notfound.aspx
Disallow: /copy-of
Disallow: /test-pages/

Sitemap: https://www.mandarinoriental.com/sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 19 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: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

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

Preferred variant: non-www

HTTP → HTTPS

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

Consistent

A+
Domain Intelligence
mandarinoriental.com — via Network Solutions, LLC, 30 years, 1 months old, hosted on Akamai
PASS
mandarinoriental.com — via Network Solutions, LLC, 30 years, 1 months old, hosted on Akamai
Info::
Domain registered until Aug 22, 2029 (3 years, 4 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: Network Solutions, LLC
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: Akamai
Got: AS16625
Domain expiry

1165 days

August 22, 2029

SSL certificate

261 days

Issued by DigiCert Inc

Domain age

30 years, 1 months

Registered August 23, 1996

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Akamai

ASN AS16625

104.104.166.156

Registrar

Network Solutions, LLC

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 Network Solutions, LLC
Created August 23, 1996 (30 years, 1 months ago)
Expires August 22, 2029 (3 years, 4 months)
Last Updated September 14, 2023
Name Servers ns1.p17.dynect.net, ns2.p17.dynect.net, ns3.p17.dynect.net, ns4.p17.dynect.net
DNSSEC Not enabled
Hosting
IP Address 104.104.166.156
ASN AS16625 (AKAMAI-AS - Akamai Technologies, Inc., US)
Provider Akamai
Data source: rdap (0.7s)

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

Connection waterfall

DNS Lookup 669 ms TCP Connect 8 ms TLS Handshake 11 ms Server Processing 17 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