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

D

CDN & Delivery

Action

No CDN detected

FIX

No CDN detected

A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.

No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

B

DNS Records

1 A records, 114 ms lookup

REVIEW

1 A records, 114 ms lookup

Resolves to 1 IPv4 address(es)

Got: 162.125.81.18

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

Has 1 IPv6 (AAAA) record(s)

Got: 2620:100:6031:18::a27d:5112

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: www-env.dropbox-dns.com

No NS records found

No MX records — email not configured via DNS

CAA records not checked

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

No SPF record found in TXT records

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

DNS resolution time: 114 ms

Got: 114 ms

A	162.125.81.18
AAAA	2620:100:6031:18::a27d:5112
CNAME	www-env.dropbox-dns.com
NS	—
MX	—
TXT	—
CAA	Lookup not available with standard resolver

Resolved in 114 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)

B

HTTP Probe Timing

Total 908 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

REVIEW

DNS Lookup

2 ms

TCP Connect

1 ms

TLS Handshake

5 ms

Time to First Byte

275 ms

Total Time

908 ms

Connection waterfall

DNS Lookup 2 ms TCP Connect 1 ms TLS Handshake 5 ms Server Processing 267 ms Content Transfer 633 ms

B

TLS Certificate Expiry & Recommendations

190 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

190

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

A+

Redirect Chain

No redirects — direct access

PASS

No redirects — direct access

Got: https://www.dropbox.com

https://www.dropbox.com

261 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://www.dropbox.com	200	261 ms	HTTP/1.1	envoy

A+

IPv6 Readiness

IPv6 reachable (1 ms)

PASS

IPv6 reachable (1 ms)

IPv6 is configured and reachable at 2620:100:6031:18::a27d:5112

Got: 1 ms connect

IPv6 Ready

AAAA Records 2620:100:6031:18::a27d:5112 Connection Reachable (1 ms)

A+

Crawlability

robots.txt present, sitemap with 10 URLs

PASS

robots.txt present, sitemap with 10 URLs

robots.txt is present

Got: 829 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 10 entries

Sitemap index with 10 child sitemaps

robots.txt references sitemap

robots.txt 200 OK

Size 829 B Sitemaps referenced 1 User-agents facebookexternalhit, *, Twitterbot Blocking No — crawling allowed

User-agent: Twitterbot
Disallow:

User-agent: facebookexternalhit
Allow: /s/
Allow: /sh/
Allow: /scl/
Allow: /sc/

User-agent: *
Allow: /static/css/
Allow: /static/images/
Allow: /static/js/
Allow: /llms.txt
Disallow: /static/
Disallow: /password_expired
Disallow: /help/sl
Disallow: /help/vodafone
Disallow: /home*
Disallow: /package_files_uploaded_via_chrome
Disallow: /photos/app_store_link/
Disallow: /recover*
Disallow: /sharing/*
Disallow: /sharing/folders*
Disallow: /sharing/files*
Disallow: /requests*
Disallow: /account*
Disallow: /referrals*
Disallow: /downgrade*
Disallow: /developers-v1
Disallow: /developers/downloads/sdks/
Disallow: /developers/whats_new
Disallow: /reengageoptout/*
Disallow: /preview/
Disallow: /s/
Disallow: /sh/
Disallow: /scl/
Disallow: /sc/


Sitemap: https://www.dropbox.com/sitemapindex.xml

sitemap.xml 200 OK

Type Sitemap Index URLs 10 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 301-redirects to HTTPS

www / non-www

200https://www.dropbox.com/

301https://dropbox.com/

Preferred variant: www

HTTP → HTTPS

301http://www.dropbox.com/ → https://www.dropbox.com/

Consistent

A+

Domain Intelligence

dropbox.com — via MarkMonitor Inc., 31 years, 2 months old

PASS

dropbox.com — via MarkMonitor Inc., 31 years, 2 months old

Domain registered until Jun 27, 2027 (1 years, 2 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.

Domain expiry

376 days

June 27, 2027

SSL certificate

190 days

Issued by DigiCert Inc

Domain age

31 years, 2 months

Registered June 28, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2620:100:6040:18::a27d:f812

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 June 28, 1995 (31 years, 2 months ago)

Expires June 27, 2027 (1 years, 2 months)

Last Updated May 26, 2025

Name Servers ns-1162.awsdns-17.org, ns-1949.awsdns-51.co.uk, ns-315.awsdns-39.com, ns-564.awsdns-06.net

DNSSEC Not enabled

Hosting

IP Address 2620:100:6040:18::a27d:f812

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