Skip to content
https://tumblr.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
86
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from New York, United Stated
301 Moved Permanently
Checks
9
5 PASS 3 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
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.

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
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.tumblr.com/
200https://tumblr.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://tumblr.com/ https://tumblr.com/

Consistent

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

Certificate validity

52
days left
0d 30d 60d 90d+

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • 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
1 A records, 6 ms lookup
PASS
1 A records, 6 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 192.0.77.40
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns3.tumblr.com, ns4.tumblr.com, ns1.tumblr.com, ns2.tumblr.com
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: 6 ms
Got: 6 ms
A192.0.77.40
AAAA
CNAME
NSns3.tumblr.com, ns4.tumblr.com, ns1.tumblr.com, ns2.tumblr.com
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 aspmx2.googlemail.com
10 aspmx3.googlemail.com
TXT
dropbox-domain-verification=gsvpgz511vsp
SPF v=spf1 include:_spf.google.com include:_spf.automattic.com include:sendgrid.net ...
figma-domain-verification=a2e41510ac6b0c5745595c76770385bfd602709c6d04e80ef830c9...
mailru-verification: c8b795f0ae1cbc3f
896862773-6204718
wtcg10h9bh0nrxglf6zc3p8mxy5t3mw9
google-site-verification=evUIJKvsT_rKVFCun0dPbCRHgQqDz1L3f36AjHyVuL4
docusign=89f952a7-e765-4f50-a3d7-9de3cd65cac4
f050f00fa3c941ea9ee3f76fc6562a11
yahoo-verification-key=+HOWRlDLIp3tUwSLvdfWrcKzs6tWS/LkZFYp8XGzC6k=
google-site-verification=CnMcqJES0ObJWvPivA5DBJFXKOryg0I9rA5JPro-Sdc
google-site-verification=p3225uNj2Zmz4RRSuvITsVPAlTsPcdN0JAm8QJ5sii4
atlassian-domain-verification=HLvi8VknRfLwuOZ7TmiaKM8GgOgai45SxxeWZddVaOBMgWielc...
google-site-verification=juLeQVndZxEsqhKFQS09fSxOZ3d2Jx2BWZqaLXakugw
google-site-verification=49CbL4sd1lOCXXoGx4wSFD87B5_Py3QGacMNlrWK4Tw
CAALookup not available with standard resolver
Resolved in 6 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), 419 ms total
PASS
1 redirect(s), 419 ms total
Info::
Single redirect
Got: https://tumblr.com → https://www.tumblr.com/ (301)
Info::
WWW normalization redirect

https://tumblr.com

31 ms · HTTP/1.1

301

https://www.tumblr.com/

388 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://tumblr.com30131 msHTTP/1.1nginx
2https://www.tumblr.com/200388 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 3 URLs
PASS
robots.txt present, sitemap with 3 URLs
Info::
robots.txt is present
Got: 3288 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 3 entries
Info::
Sitemap index with 3 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 3288 B Sitemaps referenced 1 User-agents ImagesiftBot, Slurp, FacebookBot, anthropic-ai, meta-externalagent, msnbot, *, sentibot, Googlebot, Yandex, omgili, Amazonbot, ClaudeBot, Applebot-Extended, TurnitinBot, CCBot, Google-Extended, omgilibot Blocking No — crawling allowed
Sitemap: https://www.tumblr.com/sitemap.xml

# Google Search Engine Robot
User-agent: Googlebot
Disallow: /radar
Disallow: /audio_file
Disallow: /video_file
Disallow: /dashboard
Disallow: /x
Disallow: /svc/account
Disallow: /dashboard/notes
Disallow: /customize
Disallow: /impixu
Disallow: /liked
Disallow: /search/*?before=*
Disallow: /search/*?language=*
Disallow: /tagged/*+*
Disallow: /tagged/*?before=*
Disallow: /tagged/*?language=*
Disallow: /open
Disallow: /link_to
Disallow: /sticky-ad-iframe.html
Disallow: /privacy/consent

# Yahoo! Search Engine Robot
User-agent: Slurp
Disallow: /radar
Disallow: /audio_file
Disallow: /video_file
Disallow: /dashboard
Disallow: /x
Disallow: /svc/account
Disallow: /dashboard/notes
Disallow: /customize
Disallow: /impixu
Disallow: /liked
Disallow: /search/*?before=*
Disallow: /search/*?language=*
Disallow: /tagged/*+*
Disallow: /tagged/*?before=*
Disallow: /tagged/*?language=*
Disallow: /open
Disallow: /link_to
Disallow: /sticky-ad-iframe.html
Disallow: /privacy/consent

# Yandex Search Engine Robot
User-agent: Yandex
Disallow: /radar
Disallow: /audio_file
Disallow: /video_file
Disallow: /dashboard
Disallow: /x
Disallow: /svc/account
Disallow: /dashboard/notes
Disallow: /customize
Disallow: /impixu
Disallow: /liked
Disallow: /search/*?before=*
Disallow: /search/*?language=*
Disallow: /tagged/*+*
Disallow: /tagged/*?before=*
Disallow: /tagged/*?language=*
Disallow: /open
Disallow: /link_to
Disallow: /sticky-ad-iframe.html
Disallow: /privacy/consent

# Microsoft Search Engine Robot
User-agent: msnbot
Disallow: /radar
Disallow: /audio_file
Disallow: /video_file
Disallow: /dashboard
Disallow: /x
Disallow: /svc/account
Disallow: /dashboard/notes
Disallow: /customize
Disallow: /impixu
Disallow: /liked
Disallow: /search/*?before=*
Disallow: /search/*?language=*
Disallow: /tagged/*+*
Disallow: /tagged/*?before=*
Disallow: /tagged/*?language=*
Disallow: /open
Disallow: /link_to
Disallow: /sticky-ad-iframe.html
Disallow: /privacy/consent

# Every bot that might possibly read and respect this file.
User-agent: *
Disallow: /radar
Disallow: /audio_file
Disallow: /video_file
Disallow: /dashboard
Disallow: /x
Disallow: /svc/account
Disallow: /dashboard/notes
Disallow: /customize
Disallow: /impixu
Disallow: /liked
Disallow: /search/*?before=*
Disallow: /search/*?language=*
Disallow: /tagged/*+*
Disallow: /tagged/*?before=*
Disallow: /tagged/*?language=*
Disallow: /open
Disallow: /link_to
Disallow: /sticky-ad-iframe.html
Disallow: /privacy/consent
Crawl-delay: 1

# Common Crawl's crawler
User-agent: CCBot
Disallow: /

# SentiBot's crawler
User-agent: sentibot
Disallow: /

# Google Bard's crawler
User-agent: Google-Extended
Disallow: /

# Facebook's crawler
User-agent: FacebookBot
Disallow: /

# webz.io's crawler
User-agent: omgili
Disallow: /

# webz.io's crawler
User-agent: omgilibot
Disallow: /

# Amazon's crawler
User-agent: Amazonbot
Disallow: /

# ClaudeBot's crawler
User-agent: ClaudeBot
Disallow: /

# anthropic-ai's crawler
User-agent: anthropic-ai
Disallow: /

# ImageSift's AI crawler
User-agent: ImagesiftBot
Disallow: /

# Apple's AI crawler
User-agent: Applebot-Extended
Disallow: /

# TurnitinBot crawler
User-agent: TurnitinBot
Disallow: /

# Meta AI crawler
User-agent: meta-externalagent
Disallow: /

A+
Domain Intelligence
tumblr.com — via MarkMonitor Inc., 20 years, 1 months old, hosted on WordPress.com (Automattic)
PASS
tumblr.com — via MarkMonitor Inc., 20 years, 1 months old, hosted on WordPress.com (Automattic)
Info::
Domain registered until Jun 8, 2027 (1 years, 1 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.
Info::
Hosting: WordPress.com (Automattic)
Got: AS2635
Domain expiry

330 days

June 8, 2027

SSL certificate

52 days

Issued by Let's Encrypt

Domain age

20 years, 1 months

Registered June 8, 2006

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

WordPress.com (Automattic)

ASN AS2635

192.0.77.40

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 June 8, 2006 (20 years, 1 months ago)
Expires June 8, 2027 (1 years, 1 months)
Last Updated May 7, 2025
Name Servers ns1.tumblr.com, ns2.tumblr.com, ns3.tumblr.com, ns4.tumblr.com
DNSSEC Not enabled
Hosting
IP Address 192.0.77.40
ASN AS2635 (AUTOMATTIC - Automattic, Inc, US)
Provider WordPress.com (Automattic)
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 28 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
3 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
3 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
29 ms
Total Time Total request time from DNS lookup through full response.
29 ms

Connection waterfall

DNS Lookup 3 ms TCP Connect 1 ms TLS Handshake 3 ms Server Processing 22 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