Skip to content
https://mediafire.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
0
REVIEW
9
PASS
8
INFO
0
Probed from Madrid, Spain
403 Forbidden
Checks
17
8 PASS 9 REVIEW
C
Reverse DNS
Action
0/2 IPs match cert SAN
REVIEW
0/2 IPs match cert SAN
Info::
PTR lookup failed for 104.18.213.225: lookup 104.18.213.225: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 104.18.214.225: lookup 104.18.214.225: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
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
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 212 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more ▾

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 212 B Sitemaps referenced 0 User-agents ia_archiver, * Blocking No — crawling allowed
User-agent: ia_archiver
Disallow: /

User-agent: *
Disallow: /dynamic/
Disallow: /dropbox/
Disallow: /templates/
Disallow: /myaccount/
Disallow: /api/
Disallow: /basicapi/
Disallow: /filedrop/
Disallow: /cdn-cgi/
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 403 Expected: 301 redirect to HTTPS

www / non-www

403https://www.mediafire.com/
200https://mediafire.com/

HTTP → HTTPS

403http://mediafire.com/

HTTP version does not redirect to HTTPS

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

Certificate validity

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

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
B
CDN & Delivery
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: a2e1b3ed9a36d51e-CDG
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: a2e1b3ed9a36d51e-CDG
B
CDN Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
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
Info::
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.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.
A+
DNS Records
2 A records, 30 ms lookup
PASS
2 A records, 30 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.18.213.225, 104.18.214.225
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: ken.ns.cloudflare.com, lisa.ns.cloudflare.com
Info::
5 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 30 ms
Got: 30 ms
A104.18.213.225, 104.18.214.225
AAAA—
CNAME—
NSken.ns.cloudflare.com, lisa.ns.cloudflare.com
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 alt4.aspmx.l.google.com
10 alt3.aspmx.l.google.com
TXT
facebook-domain-verification=dcrdstbacm7lya00lby6c3t8cfhov6
facebook-domain-verification=7013nxzoo8yooycncjcprys8wakasp
SPF v=spf1 include:email-secure.mediafire.com include:_spf.google.com include:spf.se...
stripe-verification=E05AE9B012072FD7247E0526190AB4D63222742C0C66889CE700CDEF3E86...
stripe-verification=641fa251ed29bd9396b7b1e8870d7c005eec221e7c74adb4bec07ef0040e...
Sendinblue-code:0e1b0689bf616ee1b3858d37db89dc41
ahrefs-site-verification_f9a61f3b67e1dc2c6d0c26cccde18e26025778b7851a12c8179d80a...
gridinsoft-verify=a12lasg2a2coqalpzpo4vxvxiw0hdm5i4kdouyze6xz3mvalo1meh5an2ci6th...
CAALookup not available with standard resolver
Resolved in 30 ms
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
DNSSEC
Signed and validating
PASS
Signed and validating
Info::
DNSSEC fully signed and chain validates (ECDSAP256SHA256)
A
CAA Records
issue: comodoca.com, digicert.com, letsencrypt.org, pki.goog, sectigo.com, ssl.com | issuewild: comodoca.com, digicert.com, letsencrypt.org, pki.goog, sectigo.com, ssl.com
PASS
issue: comodoca.com, digicert.com, letsencrypt.org, pki.goog, sectigo.com, ssl.com | issuewild: comodoca.com, digicert.com, letsencrypt.org, pki.goog, sectigo.com, ssl.com
Info::
CAA issue tag present — authorized CA(s): comodoca.com, digicert.com, letsencrypt.org, pki.goog, sectigo.com, ssl.com
Info::
No CAA iodef tag — won't be notified of failed issuance attempts
Add `0 iodef "mailto:security@example.com"` to receive notifications when a CA refuses issuance because it doesn't match your CAA policy. Useful signal for detecting issuance attempts by unauthorized CAs.
A+
Multi-Resolver DNS Speed
Mean 16ms across 3 resolvers (spread 23ms)
PASS
Mean 16ms across 3 resolvers (spread 23ms)
Info::
Quad9: 3ms
Got: 3ms via 9.9.9.9:53
Info::
Cloudflare: 21ms
Got: 21ms via 1.1.1.1:53
Info::
Google: 26ms
Got: 26ms via 8.8.8.8:53
A+
Redirect Chain
0 redirect(s), 62 ms total
PASS
0 redirect(s), 62 ms total

https://mediafire.com

62 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://mediafire.com40362 msHTTP/1.1cloudflare
A+
Domain Intelligence
mediafire.com — via Cloudflare, Inc., 24 years, 4 months old, hosted on Cloudflare
PASS
mediafire.com — via Cloudflare, Inc., 24 years, 4 months old, hosted on Cloudflare
Info::
Domain registered until Aug 11, 2031 (5 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

1811 days

August 11, 2031

SSL certificate

174 days

Issued by Sectigo Limited

Domain age

24 years, 4 months

Registered August 11, 2002

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

104.18.214.225

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 August 11, 2002 (24 years, 4 months ago)
Expires August 11, 2031 (5 years)
Last Updated February 11, 2026
Name Servers ken.ns.cloudflare.com, lisa.ns.cloudflare.com
DNSSEC Enabled
Hosting
IP Address 104.18.214.225
ASN AS13335 (CLOUDFLARENET - Cloudflare, Inc., US)
Provider Cloudflare
Data source: rdap (0.7s)

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

Connection waterfall

DNS Lookup 27 ms TCP Connect 17 ms TLS Handshake 28 ms Server Processing 27 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