Skip to content
https://fairmont.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Madrid, Spain
302 Found
Checks
9
6 PASS 3 REVIEW
B
Redirect Chain
2 redirect(s), 429 ms total
REVIEW
2 redirect(s), 429 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://fairmont.com

https://fairmont.com

37 ms · HTTP/1.1

302

https://www.fairmont.com/

391 ms · HTTP/1.1

302

https://www.fairmont.com/select-country....

2 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://fairmont.com30237 msHTTP/1.1
2https://www.fairmont.com/302391 msHTTP/1.1
3https://www.fairmont.com/select-country....2002 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
109 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Add includeSubDomains to the HSTS directive
  • 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
4 A records, 75 ms lookup
PASS
4 A records, 75 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 151.101.131.10, 151.101.3.10, 151.101.67.10, 151.101.195.10
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: dns1.cscdns.net, dns2.cscdns.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: 75 ms
Got: 75 ms
A151.101.131.10, 151.101.3.10, 151.101.67.10, 151.101.195.10
AAAA
CNAME
NSdns1.cscdns.net, dns2.cscdns.net
MX
5 accor.in.tmes.trendmicro.eu
TXT
globalsign-domain-verification=7E06D1AB0AC7B62E7BD73BFA9F5ED7C0
tmes=c8f15406d13b348098a2f7640b12aa9c
_globalsign-domain-verification=3bz0D0rHsq0lC481-Mb1i1ERTrs8CSzXxTjIms2pbs
_globalsign-domain-verification=f5AujnMyBYjFvUSvCGtJD8Mg9g5Ut6K7aJjQUN2Kr2
cnnmwtscld1nszwftn8r36jgv6kj34b8
facebook-domain-verification=62yrd38udslukyy70flmulvqec6nxa
globalsign-domain-verification=62B1E744774C9738074700C10607209F
apple-domain-verification=azgX9SjfeY0eqrIY
xbxtf9l635ptf03wv6zjxtt71zkvlj4s
hpe-greenlake-domain-verification=53376b5a3867646c37776a495341694d6c6e5045445649...
_globalsign-domain-verification=deWQKCpL_k2Hn-NqPu75tcZ-kP78DXLZm3w0VPnkYI
SPF v=spf1 include:spf.accor.com include:oracle.accor.com include:spf.givex.com incl...
8418gf0gvt99sm0lcbctcgfp68x6r470
include:6310890.spf07.hubspotemail.net
google-site-verification=U3vPxCRyDeaq2uVDyapZS5RP6TYNeDwDn23CCtt4Jno
oNpCF064BihB8jOkpZmvA0Bh9O3Q38E+IVo2hXa4Sk/UHV0HhTvN+cTgiZgM10m0Gak09OgTg8SG9Yf0...
klaviyo-site-verification=KSZBe2
gAO3SMx97hC2rj22X8KXK8u0dJssVcLGEl2C3p7qbnjzhCsNAaiQcOMRNpBaEOFA3pvT3OZFH0fX9N+z...
MS=ms86906749
klaviyo-site-verification=Pec7mN
apple-domain-verification=tpXtffWYost3x5yi
CAALookup not available with standard resolver
Resolved in 75 ms

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 7 URLs
PASS
robots.txt present, sitemap with 7 URLs
Info::
robots.txt is present
Got: 815 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 7 entries
Info::
Sitemap index with 7 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 815 B Sitemaps referenced 1 User-agents *, Libwww-perl Blocking No — crawling allowed
User-agent: *
Disallow: /my-fpc/
Disallow: /workarea/
Disallow: /reservations/
Disallow: /templates/
Disallow: /nr/
Disallow: /NR/
Disallow: /fa/
Disallow: /FA/
Disallow: /ptsunset
Disallow: /ptlunch
Disallow: /rpvwine
Disallow: /ptbreakfast
Disallow: /ptdessert
Disallow: /ptdinner
Disallow: /rpvtea
Disallow: /*countryid=*
Disallow: /*country=*
Disallow: /*category=*
Disallow: /*/profil/
Disallow: /*/cancellation/
Disallow: /*/fh/
Disallow: /*.mini
Disallow: /security-certificate/
Disallow: /booking/
Disallow: /identification/
Disallow: /express/
Disallow: /*.do
Disallow: /*.action
Disallow: /*/mini.shtml
Disallow: /geo/
Disallow: /*footer-page.html
Disallow: /permalink
Disallow: /*restaurant.bar*
Disallow: /*bar.restaurant*
Sitemap:  https://fairmont.com/sitemap.xml

User-agent: Libwww-perl
Disallow: /

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.fairmont.com/
200https://fairmont.com/

Preferred variant: non-www

HTTP → HTTPS

301http://fairmont.com/ https://fairmont.com/

Consistent

A+
Domain Intelligence
fairmont.com — via CSC Corporate Domains, Inc., 31 years, 1 months old, hosted on Fastly
PASS
fairmont.com — via CSC Corporate Domains, Inc., 31 years, 1 months old, hosted on Fastly
Info::
Domain registered until Aug 30, 2026 (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: 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: Fastly
Got: AS54113
Domain expiry

75 days

August 30, 2026

SSL certificate

109 days

Issued by GlobalSign nv-sa

Domain age

31 years, 1 months

Registered August 31, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Fastly

ASN AS54113

151.101.67.10

Registrar

CSC Corporate Domains, Inc.

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar CSC Corporate Domains, Inc.
Created August 31, 1995 (31 years, 1 months ago)
Expires August 30, 2026 (4 months)
Last Updated August 26, 2025
Name Servers dns1.cscdns.net, dns2.cscdns.net
DNSSEC Not enabled
Hosting
IP Address 151.101.67.10
ASN AS54113 (FASTLY - Fastly, Inc., US)
Provider Fastly
Data source: rdap (0.4s)

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

Connection waterfall

DNS Lookup 33 ms TCP Connect 0 ms TLS Handshake 4 ms Server Processing 119 ms Content Transfer 0 ms
A
CDN & Delivery
Fastly (MISS)
PASS
Fastly (MISS)
Info::
Site is served via Fastly CDN
Got: x-served-by: cache-toj-leto2350050-TOJ
Info::
CDN cache status: MISS
CDN Detected: Fastly
Provider Fastly Cache Status MISS Evidence x-served-by: cache-toj-leto2350050-TOJ
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback