Infrastructure - https://www.snapchat.com BeaverCheck Audit

B

DNS Records

1 A records, 42 ms lookup

REVIEW

1 A records, 42 ms lookup

Resolves to 1 IPv4 address(es)

Got: 34.149.46.130

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

No IPv6 (AAAA) records

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.snapchat.com

No NS records found

No MX records — email not configured via DNS

No SPF record found in TXT records

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

DNS resolution time: 42 ms

Got: 42 ms

A	34.149.46.130
AAAA	—
CNAME	web-gcp.api.snapchat.com
NS	—
MX	—
TXT	—
CAA	Lookup not available with standard resolver

Resolved in 42 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

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)

B

DNSSEC

Unsigned (DNSSEC not deployed)

REVIEW

Unsigned (DNSSEC not deployed)

DNSSEC is not deployed

The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).

B

CAA Records

No CAA records (any CA may issue certificates)

REVIEW

No CAA records (any CA may issue certificates)

No CAA records published

Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.

B

Reverse DNS

0/1 IPs match cert SAN

REVIEW

0/1 IPs match cert SAN

PTR for 34.149.46.130 does not match any cert SAN: 130.46.149.34.bc.googleusercontent.com

Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.

C

IPv6 Readiness

Action

No IPv6 support

REVIEW

No IPv6 support

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

151 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

151

days left

0d 30d 60d 90d+

Recommended actions

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

Document on Google Cloud CDN; assets also on AWS CloudFront

REVIEW

Document on Google Cloud CDN; assets also on AWS CloudFront

Document is served via Google Cloud CDN CDN

Got: via: 1.1 google, 1.1 google

Assets on AWS CloudFront: static.snapchat.com (assets: 34), cache Hit from cloudfront

Got: delegation d1h99r20nnwifw.cloudfront.net

Document served via CDN: Google Cloud CDN

Provider Google Cloud CDN Evidence via: 1.1 google, 1.1 google

Asset hosts on a CDN

static.snapchat.com — AWS CloudFront · assets: 34 · Cache Status: Hit from cloudfront

B

CDN Cache Observability

No CDN cache-status headers in the response

REVIEW

No CDN cache-status headers in the response

Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.

B

Operational Status Page

No status page link detected

REVIEW

No status page link detected

No operational status page link detected

Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.

A+

Subdomain Takeover

No subdomain takeover risk detected

PASS

No subdomain takeover risk detected

CNAME does not point at a known takeover-able service

A+

Multi-Resolver DNS Speed

Mean 12ms across 3 resolvers (spread 18ms)

PASS

Mean 12ms across 3 resolvers (spread 18ms)

Quad9: 1ms

Got: 1ms via 9.9.9.9:53

Google: 16ms

Got: 16ms via 8.8.8.8:53

Cloudflare: 19ms

Got: 19ms via 1.1.1.1:53

A+

Redirect Chain

No redirects — direct access

PASS

No redirects — direct access

Got: https://www.snapchat.com

https://www.snapchat.com

269 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://www.snapchat.com	200	269 ms	HTTP/1.1	API Gateway

A+

Crawlability

robots.txt present, sitemap with 13 URLs

PASS

robots.txt present, sitemap with 13 URLs

robots.txt is present

Got: 4072 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 13 entries

Sitemap index with 13 child sitemaps

robots.txt references sitemap

robots.txt 200 OK

Size 4072 B Sitemaps referenced 13 User-agents Scrapy, Sidetrade indexer bot, Timpibot, YouBot, Meta-ExternalAgent, cohere-training-data-crawler, Webzio-Extended, Meta-ExternalFetcher, Bytespider, Claude-Web, FriendlyCrawler, iaskspider/2.0, FacebookBot, Googlebot, Perplexity-User, ClaudeBot, GoogleOther, GoogleOther-Image, ICC-Crawler, PetalBot, OAI-SearchBot, Claude-SearchBot, DuckAssistBot, Crawlspace, Google-Extended, GPTBot, SemrushBot-OCOB, SemrushBot-SWA, Applebot-Extended, cohere-ai, img2dataset, ISSCyberRiskCrawler, VelenPublicWebCrawler, *, anthropic-ai, Diffbot, GoogleOther-Video, ImagesiftBot, Kangaroo Bot, Meta-WebIndexer, ChatGPT-User, Claude-User, AI2Bot, Amazonbot, Brightbot 1.0, omgilibot, PanguBot, PerplexityBot, Ai2Bot-Dolma, CCBot, omgili 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: /

# OAI-SearchBot
User-agent: OAI-SearchBot
Allow: /
Disallow: /getreplies
Disallow: /explore/

# ChatGPT-User
User-agent: ChatGPT-User
Allow: /
Disallow: /getreplies
Disallow: /explore/

# PerplexityBot
User-agent: PerplexityBot
Allow: /
Disallow: /getreplies
Disallow: /explore/

# Perplexity-User
User-agent: Perplexity-User
Allow: /
Disallow: /getreplies
Disallow: /explore/

# Claude-SearchBot
User-agent: Claude-SearchBot
Allow: /
Disallow: /getreplies
Disallow: /explore/

# Claude-User
User-agent: Claude-User
Allow: /
Disallow: /getreplies
Disallow: /explore/

# DuckAssistBot
User-agent: DuckAssistBot
Allow: /
Disallow: /getreplies
Disallow: /explore/

# 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: /

# 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: /

# 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: /

# omgili
User-agent: omgili
Disallow: /

# omgilibot
User-agent: omgilibot
Disallow: /

# PanguBot
User-agent: PanguBot
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/sitemaps/place/sitemap-index.xml
Sitemap: https://www.snapchat.com/sitemaps/profile/sitemap-index.xml
Sitemap: https://www.snapchat.com/sitemaps/p/sitemap-index.xml
Sitemap: https://www.snapchat.com/sitemaps/lens_creators/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/entertainment_funny/sitemap-index.xml
Sitemap: https://www.snapchat.com/sitemaps/top_spotlights/sitemap-index.xml
Sitemap: https://www.snapchat.com/sitemaps/local_city_leaf/sitemap-index.xml
Sitemap: https://www.snapchat.com/sitemaps/local_nbhd_leaf/sitemap-index.xml
Sitemap: https://www.snapchat.com/sitemaps/local_city_hub/sitemap-index.xml

sitemap.xml 200 OK

Type Sitemap Index URLs 13 entries Valid XML Yes

Child Sitemaps:

A+

URL Variants

www/non-www, trailing slash, HTTP→HTTPS

PASS

www/non-www, trailing slash, HTTP→HTTPS

www/non-www redirect configured correctly (preferred: www)

HTTP correctly redirects to HTTPS permanently

Got: HTTP 301

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, 10 months old, hosted on Google Cloud

PASS

snapchat.com — via MarkMonitor Inc., 14 years, 10 months old, hosted on Google Cloud

Domain registered until Feb 28, 2034 (7 years, 4 months remaining)

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.

Registrar: MarkMonitor Inc.

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.

Hosting: Google Cloud

Got: AS396982

Domain expiry

2665 days

February 28, 2034

SSL certificate

151 days

Issued by DigiCert Inc

Domain age

14 years, 10 months

Registered February 28, 2012

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Google Cloud

ASN AS396982

34.149.46.130

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 28, 2012 (14 years, 10 months ago)

Expires February 28, 2034 (7 years, 4 months)

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.3s)

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 242 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

PASS

DNS Lookup

43 ms

TCP Connect

17 ms

TLS Handshake

21 ms

Time to First Byte

220 ms

Total Time

243 ms

Connection waterfall

DNS Lookup 43 ms TCP Connect 17 ms TLS Handshake 21 ms Server Processing 139 ms Content Transfer 22 ms

A+

Health Check Endpoint

Health endpoint at https://www.snapchat.com/ping (HTTP 200)

PASS

Health endpoint at https://www.snapchat.com/ping (HTTP 200)

Public health endpoint at https://www.snapchat.com/ping

Got: https://www.snapchat.com/ping