Skip to content
https://viator.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Madrid, Spain
308 Permanent Redirect
Checks
9
6 PASS 3 REVIEW
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
Crawlability
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

C
TLS Certificate Expiry & Recommendations
Action
20 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

20
days left
0d 30d 60d 90d+
Renew soon — under 30 days remaining

Recommended actions

  • Renew certificate — 20 days remaining
  • 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
4 A records, 2 ms lookup
PASS
4 A records, 2 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 151.101.65.91, 151.101.1.91, 151.101.193.91, 151.101.129.91
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1767.awsdns-28.co.uk, ns-47.awsdns-05.com, ns-1163.awsdns-17.org, ns-604.awsdns-11.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: 2 ms
Got: 2 ms
A151.101.65.91, 151.101.1.91, 151.101.193.91, 151.101.129.91
AAAA
CNAME
NSns-1767.awsdns-28.co.uk, ns-47.awsdns-05.com, ns-1163.awsdns-17.org, ns-604.awsdns-11.net
MX
10 smtp.google.com
TXT
google-site-verification=tbzf9IDMO5HZhEbN1KJRHGibEaNSc7K3iLb9npVzeyM
google-site-verification=8Wr1Tj3E1LXzKgnUsKdw327kU61WVETiOL1MzDPjcJY
MS=ms44102608
google-site-verification=n6lIuLvvH0NGV8Iw0ChO7HhteIDvX6ua88x9vQgb73A
atlassian-domain-verification=w2N0fg0r/RRZCQ7UgNfpKKFXJH1kvCtLacvj/HzML7VZYyhEDT...
_o1tvyo0ny2o26is5kvf3id9sm3boinx
datadome-domain-verify=LtwSY8f9UsuWkflYriVEN5xJW7jb1OGB
SPF v=spf1 include:_spf.tripadvisor.com include:amazonses.com include:mktomail.com i...
perplexity-ai-domain-verification-w8b83e=JnXnWPWhOnlCA796S1QbnXtPw
facebook-domain-verification=23ac8apxyt8ivq3rhi55lamrrk061n
google-site-verification=bF_EKOCH0CZXfqFkPrhE9xr5JZx4OowLwBdqPsV9HZQ
globalsign-domain-verification=3B-TQ8Y-5z1xF00CEQ3ZvrIR1VspPn7dyAno-wqZv-
yandex-verification: 238924f7875846f9
google-site-verification=cNyo6d8r5dF5SjCn90JtyDn224TreGw3EiF8vTHMruQ
BC99FcKfYn6MaOBhqIca7w
MS=6CE5940CCAB23124331A1CDA1EB5188E0B4352DC
miro-verification=6ff1de40e337f458d05086183318e55305c99fe1
CAALookup not available with standard resolver
Resolved in 2 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
Redirect Chain
1 redirect(s), 84 ms total
PASS
1 redirect(s), 84 ms total
Info::
Single redirect
Got: https://viator.com → https://www.viator.com/ (308)
Info::
WWW normalization redirect

https://viator.com

4 ms · HTTP/1.1

308

https://www.viator.com/

80 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://viator.com3084 msHTTP/1.1Varnish
2https://www.viator.com/40380 msHTTP/1.1DataDome

See the visual redirect chain in the HTTP Probe tab →

A
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

403https://www.viator.com/
200https://viator.com/

HTTP → HTTPS

308http://viator.com/ https://www.viator.com/

Use 301 (permanent) instead of 302 (temporary)

A+
Domain Intelligence
viator.com — via CSC Corporate Domains, Inc., 27 years, 7 months old, hosted on Fastly
PASS
viator.com — via CSC Corporate Domains, Inc., 27 years, 7 months old, hosted on Fastly
Info::
Domain registered until Jan 17, 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.
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

182 days

January 17, 2027

SSL certificate

20 days

Issued by Certainly

Domain age

27 years, 7 months

Registered January 17, 1999

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Fastly

ASN AS54113

151.101.1.91

Registrar

CSC Corporate Domains, Inc.

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the TLS certificate or verify auto-renewal is working
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar CSC Corporate Domains, Inc.
Created January 17, 1999 (27 years, 7 months ago)
Expires January 17, 2027 (9 months)
Last Updated January 13, 2026
Name Servers ns-1163.awsdns-17.org, ns-1767.awsdns-28.co.uk, ns-47.awsdns-05.com, ns-604.awsdns-11.net
DNSSEC Not enabled
Hosting
IP Address 151.101.1.91
ASN AS54113 (FASTLY - Fastly, Inc., US)
Provider Fastly
Data source: rdap (0.2s)

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 4 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
1 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.
2 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
4 ms
Total Time Total request time from DNS lookup through full response.
5 ms

Connection waterfall

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

Send Feedback