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

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
89
GRADE
B
FIX
0
REVIEW
4
PASS
5
INFO
0
Probed from Sao Paulo, Brazil
200 OK
Checks
9
5 PASS 4 REVIEW
B
DNS Records
1 A records, 129 ms lookup
REVIEW
1 A records, 129 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 34.149.46.130
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: web-gcp.api.sc-gw.com
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: 129 ms
Got: 129 ms
A34.149.46.130
AAAA
CNAMEweb-gcp.api.sc-gw.com
NS
MX
TXT
CAALookup not available with standard resolver
Resolved in 129 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
192 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

192
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
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+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.snapchat.com

https://www.snapchat.com

18 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.snapchat.com20018 msHTTP/1.1API Gateway
A+
Crawlability
robots.txt present, sitemap with 21 URLs
PASS
robots.txt present, sitemap with 21 URLs
Info::
robots.txt is present
Got: 4254 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 21 entries
Info::
Sitemap index with 21 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 4254 B Sitemaps referenced 21 User-agents OAI-SearchBot, omgili, PetalBot, SemrushBot-OCOB, AI2Bot, Ai2Bot-Dolma, anthropic-ai, Applebot-Extended, Crawlspace, SemrushBot-SWA, *, Meta-ExternalFetcher, GoogleOther, GoogleOther-Video, img2dataset, ISSCyberRiskCrawler, Kangaroo Bot, PerplexityBot, DuckAssistBot, Google-Extended, ICC-Crawler, PanguBot, YouBot, GoogleOther-Image, Meta-WebIndexer, Claude-Web, cohere-ai, Diffbot, FacebookBot, Webzio-Extended, Meta-ExternalAgent, CCBot, ChatGPT-User, cohere-training-data-crawler, FriendlyCrawler, VelenPublicWebCrawler, ClaudeBot, Googlebot, GPTBot, ImagesiftBot, omgilibot, Timpibot, Perplexity‑User, Scrapy, Sidetrade indexer bot, Amazonbot, Brightbot 1.0, Bytespider, iaskspider/2.0 Blocking No — crawling allowed
# *
User-agent: *
Disallow: /verificationofemployment
Disallow: /static_files/deletion_request.pdf
Disallow: /static/gla/
Disallow: /invite/

# Meta-WebIndexer
User-agent: Meta-WebIndexer
Allow: /

# Meta-ExternalAgent
User-agent: Meta-ExternalAgent
Disallow: /

# Meta-ExternalFetcher
User-agent: Meta-ExternalFetcher
Disallow: /

# AI2Bot
User-agent: AI2Bot
Disallow: /

# Ai2Bot-Dolma
User-agent: Ai2Bot-Dolma
Disallow: /

# Amazonbot
User-agent: Amazonbot
Disallow: /

# anthropic-ai
User-agent: anthropic-ai
Disallow: /

# Applebot-Extended
User-agent: Applebot-Extended
Disallow: /

# Brightbot 1.0
User-agent: Brightbot 1.0
Disallow: /

# Bytespider
User-agent: Bytespider
Disallow: /

# CCBot
User-agent: CCBot
Disallow: /

# ChatGPT-User
User-agent: ChatGPT-User
Disallow: /

# Claude-Web
User-agent: Claude-Web
Disallow: /

# ClaudeBot
User-agent: ClaudeBot
Disallow: /

# cohere-ai
User-agent: cohere-ai
Disallow: /

# cohere-training-data-crawler
User-agent: cohere-training-data-crawler
Disallow: /

# Crawlspace
User-agent: Crawlspace
Disallow: /

# Diffbot
User-agent: Diffbot
Disallow: /

# DuckAssistBot
User-agent: DuckAssistBot
Disallow: /

# FacebookBot
User-agent: FacebookBot
Disallow: /

# FriendlyCrawler
User-agent: FriendlyCrawler
Disallow: /

# Googlebot
User-agent: Googlebot
Disallow: /getreplies
Disallow: /explore/

# Google-Extended
User-agent: Google-Extended
Disallow: /

# GoogleOther
User-agent: GoogleOther
Disallow: /

# GoogleOther-Image
User-agent: GoogleOther-Image
Disallow: /

# GoogleOther-Video
User-agent: GoogleOther-Video
Disallow: /

# GPTBot
User-agent: GPTBot
Disallow: /

# iaskspider/2.0
User-agent: iaskspider/2.0
Disallow: /

# ICC-Crawler
User-agent: ICC-Crawler
Disallow: /

# ImagesiftBot
User-agent: ImagesiftBot
Disallow: /

# img2dataset
User-agent: img2dataset
Disallow: /

# ISSCyberRiskCrawler
User-agent: ISSCyberRiskCrawler
Disallow: /

# Kangaroo Bot
User-agent: Kangaroo Bot
Disallow: /

# OAI-SearchBot
User-agent: OAI-SearchBot
Disallow: /

# omgili
User-agent: omgili
Disallow: /

# omgilibot
User-agent: omgilibot
Disallow: /

# PanguBot
User-agent: PanguBot
Disallow: /

# PerplexityBot
User-agent: PerplexityBot
Disallow: /

# Perplexity‑User
User-agent: Perplexity‑User
Disallow: /

# PetalBot
User-agent: PetalBot
Disallow: /

# Scrapy
User-agent: Scrapy
Disallow: /

# SemrushBot-OCOB
User-agent: SemrushBot-OCOB
Disallow: /

# SemrushBot-SWA
User-agent: SemrushBot-SWA
Disallow: /

# Sidetrade indexer bot
User-agent: Sidetrade indexer bot
Disallow: /

# Timpibot
User-agent: Timpibot
Disallow: /

# VelenPublicWebCrawler
User-agent: VelenPublicWebCrawler
Disallow: /

# Webzio-Extended
User-agent: Webzio-Extended
Disallow: /

# YouBot
User-agent: YouBot
Disallow: /

# Host
Host: https://www.snapchat.com

# Sitemaps
Sitemap: https://www.snapchat.com/sitemap.xml
Sitemap: https://www.snapchat.com/lens/sitemap.xml
Sitemap: https://www.snapchat.com/add/sitemap.xml
Sitemap: https://www.snapchat.com/p/sitemap.xml
Sitemap: https://www.snapchat.com/sitemaps/place/sitemap-index.xml
Sitemap: https://www.snapchat.com/sitemaps/add/sitemap-index.xml
Sitemap: https://www.snapchat.com/sitemaps/p/sitemap-index.xml
Sitemap: https://www.snapchat.com/sitemaps/tag/sitemap-index.xml
Sitemap: https://www.snapchat.com/sitemaps/topic/sitemap-index.xml
Sitemap: https://www.snapchat.com/sitemaps/curated_topic/sitemap-index.xml
Sitemap: https://www.snapchat.com/sitemaps/extended_curated_topic/sitemap-index.xml
Sitemap: https://www.snapchat.com/sitemaps/ddb_topic_all/sitemap-index.xml
Sitemap: https://www.snapchat.com/sitemaps/ddb_topic_eight_plus/sitemap-index.xml
Sitemap: https://www.snapchat.com/sitemaps/ddb_topic_up_to_eight/sitemap-index.xml
Sitemap: https://www.snapchat.com/sitemaps/top_spotlights/sitemap-index.xml
Sitemap: https://www.snapchat.com/sitemaps/mit_tier1_legacy/sitemap-index.xml
Sitemap: https://www.snapchat.com/sitemaps/mit_tier1_new/sitemap-index.xml
Sitemap: https://www.snapchat.com/sitemaps/mit_tier1_mix/sitemap-index.xml
Sitemap: https://www.snapchat.com/sitemaps/mit_tier2_legacy/sitemap-index.xml
Sitemap: https://www.snapchat.com/sitemaps/mit_tier2_new/sitemap-index.xml
Sitemap: https://www.snapchat.com/sitemaps/mit_tier2_mix/sitemap-index.xml

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.snapchat.com/
301https://snapchat.com/

Preferred variant: www

HTTP → HTTPS

301http://www.snapchat.com/ https://www.snapchat.com:443/

Consistent

A+
Domain Intelligence
snapchat.com — via MarkMonitor Inc., 14 years, 3 months old, hosted on Google Cloud
PASS
snapchat.com — via MarkMonitor Inc., 14 years, 3 months old, hosted on Google Cloud
Info::
Domain registered until Feb 28, 2034 (8 years 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.
Info::
Hosting: Google Cloud
Got: AS396982
Domain expiry

2817 days

February 28, 2034

SSL certificate

192 days

Issued by DigiCert Inc

Domain age

14 years, 3 months

Registered February 28, 2012

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Google Cloud

ASN AS396982

34.149.46.130

Registrar

MarkMonitor Inc.

Lock status unknown 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
Registrar MarkMonitor Inc.
Created February 28, 2012 (14 years, 3 months ago)
Expires February 28, 2034 (8 years)
Last Updated January 28, 2026
Name Servers ns-1468.awsdns-55.org, ns-1892.awsdns-44.co.uk, ns-220.awsdns-27.com, ns-530.awsdns-02.net
DNSSEC Not enabled
Hosting
IP Address 34.149.46.130
ASN AS396982 (GOOGLE-CLOUD-PLATFORM - Google LLC, US)
Provider Google Cloud
Data source: rdap (0.6s)

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

Connection waterfall

DNS Lookup 5 ms TCP Connect 2 ms TLS Handshake 5 ms Server Processing 5 ms Content Transfer 2 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback