Skip to content
https://snap.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
0
REVIEW
4
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 4 REVIEW
B
Crawlability
robots.txt present, sitemap with 841 URLs
REVIEW
robots.txt present, sitemap with 841 URLs
Info::
robots.txt is present
Got: 82 bytes
Info::
sitemap.xml is present
Warning::
sitemap.xml contains invalid XML
Search engines may not be able to parse the sitemap. Fix XML validation errors.
Info::
sitemap.xml contains 841 entries
Info::
robots.txt references sitemap

Search engines may not be able to parse the sitemap. Fix XML validation errors.

Why this matters

An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.

Learn more

Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.

Source: sitemaps.org / Google Search Central

robots.txt 200 OK
Size 82 B Sitemaps referenced 1 User-agents Blocking No — crawling allowed
# a file without rules allows all traffic


Sitemap: https://snap.com/sitemap.xml
B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.snap.com/
200https://snap.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://snap.com/ https://snap.com:443/

Consistent

B
TLS Certificate Expiry & Recommendations
44 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

44
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
B
CDN & Delivery
Google Cloud CDN
REVIEW
Google Cloud CDN
Info::
Site is served via Google Cloud CDN CDN
Got: via: 1.1 google
CDN Detected: Google Cloud CDN
Provider Google Cloud CDN Evidence via: 1.1 google
A+
DNS Records
1 A records, 157 ms lookup
PASS
1 A records, 157 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 34.120.54.238
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2600:1901:0:3527::
Info::
4 nameserver(s) configured
Got: ns-863.awsdns-43.net, ns-441.awsdns-55.com, ns-1472.awsdns-56.org, ns-1681.awsdns-18.co.uk
Info::
5 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: 157 ms
Got: 157 ms
A34.120.54.238
AAAA2600:1901:0:3527::
CNAME
NSns-863.awsdns-43.net, ns-441.awsdns-55.com, ns-1472.awsdns-56.org, ns-1681.awsdns-18.co.uk
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 aspmx3.googlemail.com
10 aspmx2.googlemail.com
TXT
atlassian-domain-verification=P7v4/0SuI03V2xsQfPTYYZLbRwBN1QkqBg4E/zqmJVvyWKraMa...
TAILSCALE-bAU9TfNGoz4iD4hioxcp
atlassian-domain-verification=TH6BFQJRvZM36e0pNbXcEI/RpTrqBb2JDxzoBsBLa3RajLrpmc...
google-site-verification=Fu4sMmFQ5qi2cdu3pIlD92IzIwyK1vTMTAd70bT9BfI
MS=F19FE092FCBD58C19A3EB49E41F5FBC6C34AD010
fng92q54lx2p79xwcpbm7kkb3j9dzr1y
docker-verification=baf1068d-985e-4ba7-ade5-6e4f4e52b9dd
google-site-verification=bN9aGB9XR24fvFAo_WuhfwP8FWMhyVcObZ2t8z-odUE
m43l0x1d2fsnr3s4b4gdhv9fv35krqfp
google-site-verification=xWf_xBWraQNU-UfYtg1qgmoGBR7--ZX1p6hT32-hBGY
smartsheet-site-validation=vpz_czbc5htXdum8y-ede2x48h1TxaUF
atlassian-domain-verification=t2mP/OxdJvz/S28h3o/5egOc105U1aKneVRngll9cfhI4Un8gQ...
_57a4l3113lsz5nbjk2m71qnriqtwlu1
dropbox-domain-verification=9qj8jzvk1dgv
apple-domain-verification=z0ZiJ8oPQdCG7sNB
MS=ms43386075
SPF v=spf1 include:_spf.google.com include:mail.zendesk.com include:aspmx.pardot.com...
miro-verification=b341b9dfb098865b7517b6c662e94e5538603be4
docusign=802eeaa9-c5d2-42bd-98dc-e42cf6ad7a1d
adobe-idp-site-verification=1b7089e1333b1302c4f425ff60baae967ac377d76fb6aa7bb61c...
CAALookup not available with standard resolver
Resolved in 157 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
Redirect Chain
1 redirect(s), 161 ms total
PASS
1 redirect(s), 161 ms total
Info::
Single redirect
Got: https://snap.com → https://www.snap.com/ (301)
Info::
WWW normalization redirect

https://snap.com

57 ms · HTTP/1.1

301

https://www.snap.com/

103 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://snap.com30157 msHTTP/1.1Google Frontend
2https://www.snap.com/200103 msHTTP/1.1Google Frontend

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2600:1901:0:3527::
Got: 17 ms connect
IPv6 Ready
AAAA Records 2600:1901:0:3527:: Connection Reachable (17 ms)
A+
Domain Intelligence
snap.com — via MarkMonitor Inc., 29 years, 7 months old
PASS
snap.com — via MarkMonitor Inc., 29 years, 7 months old
Info::
Domain registered until Feb 21, 2027 (10 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: MarkMonitor 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.
Domain expiry

250 days

February 21, 2027

SSL certificate

44 days

Issued by Google Trust Services

Domain age

29 years, 7 months

Registered February 20, 1997

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2600:1901:0:3527::

Registrar

MarkMonitor Inc.

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 MarkMonitor Inc.
Created February 20, 1997 (29 years, 7 months ago)
Expires February 21, 2027 (10 months)
Last Updated January 20, 2025
Name Servers ns-1472.awsdns-56.org, ns-1681.awsdns-18.co.uk, ns-441.awsdns-55.com, ns-863.awsdns-43.net
DNSSEC Not enabled
Hosting
IP Address 2600:1901:0:3527::
Data source: rdap (0.1s)

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

Connection waterfall

DNS Lookup 46 ms TCP Connect 17 ms TLS Handshake 22 ms Server Processing 61 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