Skip to content
https://mixcloud.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
80
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Santa Clara, United States
302 Found
Checks
9
5 PASS 3 REVIEW 1 FIX
F
IPv6 Readiness
Action
IPv6 records exist but unreachable
FIX
IPv6 records exist but unreachable
Warning::
IPv6 DNS records exist but server is not reachable
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Got: 2606:4700:10::6814:424, 2606:4700:10::6814:524
Info::
IPv6 connection error
Got: dial tcp6 [2606:4700:10::6814:424]:443: connect: network is unreachable
IPv6 Misconfigured
AAAA Records 2606:4700:10::6814:424, 2606:4700:10::6814:524 Connection UNREACHABLE

Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.

Why this matters

Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.

Learn more

Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.

Source: RFC 8305 (Happy Eyeballs)

C
URL Variants
Action
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
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

200https://www.mixcloud.com/
200https://mixcloud.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

302http://mixcloud.com/ https://www.mixcloud.com/

Use 301 (permanent) instead of 302 (temporary)

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

Certificate validity

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

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
B
CDN & Delivery
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: SJC)
Got: cf-ray: 9efeb2e22dd0fa52-SJC
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9efeb2e22dd0fa52-SJC
A+
DNS Records
2 A records, 9 ms lookup
PASS
2 A records, 9 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.20.4.36, 104.20.5.36
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:10::6814:424, 2606:4700:10::6814:524
Info::
2 nameserver(s) configured
Got: miles.ns.cloudflare.com, tegan.ns.cloudflare.com
Info::
7 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: 9 ms
Got: 9 ms
A104.20.4.36, 104.20.5.36
AAAA2606:4700:10::6814:424, 2606:4700:10::6814:524
CNAME
NSmiles.ns.cloudflare.com, tegan.ns.cloudflare.com
MX
1 aspmx.l.google.com
3 alt2.aspmx.l.google.com
3 alt1.aspmx.l.google.com
5 aspmx4.googlemail.com
5 aspmx2.googlemail.com
5 aspmx5.googlemail.com
5 aspmx3.googlemail.com
TXT
apple-domain-verification=cBSzBF9wU7M8t86W
anthropic-domain-verification-f8bk6j=pjkBH2jlqaPakiBTB4Vx9e5td
google-site-verification=CB4tWZGyP2d-9jp1_q7WPJOuIGz6UUHm8nnMeY9Tsj8
google-site-verification=MIkL-g_FIR1v7JnMSJ-Ilfjqlqz6xAQtK7CP3AzlyNE
SPF v=spf1 include:_spf.google.com include:mail.zendesk.com ip4:46.23.65.217/32 -all
CAALookup not available with standard resolver
Resolved in 9 ms

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), 201 ms total
PASS
1 redirect(s), 201 ms total
Info::
Single redirect
Got: https://mixcloud.com → https://www.mixcloud.com/ (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://mixcloud.com

https://mixcloud.com

25 ms · HTTP/1.1

302

https://www.mixcloud.com/

176 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://mixcloud.com30225 msHTTP/1.1cloudflare
2https://www.mixcloud.com/200176 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

A+
Crawlability
robots.txt present, sitemap with 851 URLs
PASS
robots.txt present, sitemap with 851 URLs
Info::
robots.txt is present
Got: 1494 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 851 entries
Info::
Sitemap index with 851 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1494 B Sitemaps referenced 5 User-agents Applebot-Extended, Diffbot, *, GPTBot, GoogleExtended, anthropic-ai, AmazonBot, CCBot, omgili, cohere-ai, Google-CloudVertexBot, Meta-ExternalAgent, Bytespider, PerplexityBot, Omgilibot, ClaudeBot, FacebookBot, ImagesiftBot, Timpibot, ChatGPT-User, Claude-Web, Google-Extended Blocking No — crawling allowed
User-Agent: *
Allow: /
Disallow: /oauth/
Disallow: /short/
Disallow: /pigeon/
Disallow: /blog/wp-json/
Disallow: /blog/?rest_route=

Sitemap: https://sitemaps.mixcloud.com/sitemap_userprofile_index.xml
Sitemap: https://sitemaps.mixcloud.com/sitemap_cloudcast_index.xml
Sitemap: https://sitemaps.mixcloud.com/sitemap_tag_index.xml
Sitemap: https://sitemaps.mixcloud.com/sitemap_playlist_index.xml
Sitemap: https://www.mixcloud.com/blog/sitemap_index.xml

# Block OpenAI
User-agent: GPTBot
User-agent: ChatGPT-User

# Block Common Crawl
User-agent: CCBot

# Block Perplexity
User-agent: PerplexityBot

# Block Webz.io
User-agent: omgili
User-agent: Omgilibot

# Block Google Extended
User-agent: GoogleExtended

# Block Anthropic Anthropic
User-agent: anthropic-ai
User-agent: Claude-Web
User-agent: ClaudeBot

# Block Cohere AI
User-agent: cohere-ai

# Block Google-AI see https://blog.google/technology/ai/an-update-on-web-publisher-controls/
User-agent: Google-Extended
User-agent: Google-CloudVertexBot

# Facebook LLM see https://developers.facebook.com/docs/sharing/bot
User-Agent: FacebookBot
User-agent: Meta-ExternalAgent

# Amazon Alexa see https://developer.amazon.com/amazonbot
User-Agent: AmazonBot

# Tiktok / ByteDance
User-agent: Bytespider

# Apple
User-agent: Applebot-Extended

# imagesift.com
User-agent: ImagesiftBot

# diffbot.com
User-agent: Diffbot

# https://timpi.io/
User-agent: Timpibot

Allow: /blog/
Disallow: /
Disallow: /blog/wp-json/
Disallow: /blog/?rest_route=

sitemap.xml 200 OK
Type Sitemap Index URLs 851 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
mixcloud.com — via Cloudflare, Inc., 18 years, 3 months old, hosted on Cloudflare
PASS
mixcloud.com — via Cloudflare, Inc., 18 years, 3 months old, hosted on Cloudflare
Info::
Domain registered until Apr 11, 2033 (7 years remaining)
Info::
DNSSEC is enabled
Info::
Registrar: Cloudflare, 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: Cloudflare
Got: AS13335
Domain expiry

2462 days

April 11, 2033

SSL certificate

80 days

Issued by Let's Encrypt

Domain age

18 years, 3 months

Registered April 11, 2008

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

104.20.4.36

Registrar

Cloudflare, Inc.

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Cloudflare, Inc.
Created April 11, 2008 (18 years, 3 months ago)
Expires April 11, 2033 (7 years)
Last Updated August 11, 2025
Name Servers miles.ns.cloudflare.com, tegan.ns.cloudflare.com
DNSSEC Enabled
Hosting
IP Address 104.20.4.36
ASN AS13335 (CLOUDFLARENET - Cloudflare, Inc., US)
Provider Cloudflare
Data source: rdap (0.1s)

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

Connection waterfall

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