Skip to content
https://mediafire.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
0
REVIEW
5
PASS
4
INFO
0
Probed from Madrid, Spain
403 Forbidden
Checks
9
4 PASS 5 REVIEW
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::
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.mediafire.com/
200https://mediafire.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://mediafire.com/ https://www.mediafire.com/

Consistent

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

Certificate validity

105
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: CDG)
Got: cf-ray: 9ed5181dc8547033-CDG
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9ed5181dc8547033-CDG
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.17.147.83, 104.17.148.83
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::
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: 30 ms
Got: 30 ms
A104.17.147.83, 104.17.148.83
AAAA
CNAME
NSken.ns.cloudflare.com, lisa.ns.cloudflare.com
MX
1 aspmx.l.google.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
10 alt3.aspmx.l.google.com
10 alt4.aspmx.l.google.com
TXT
facebook-domain-verification=7013nxzoo8yooycncjcprys8wakasp
stripe-verification=641fa251ed29bd9396b7b1e8870d7c005eec221e7c74adb4bec07ef0040e...
SPF v=spf1 include:email-secure.mediafire.com include:_spf.google.com include:spf.se...
stripe-verification=E05AE9B012072FD7247E0526190AB4D63222742C0C66889CE700CDEF3E86...
Sendinblue-code:0e1b0689bf616ee1b3858d37db89dc41
facebook-domain-verification=dcrdstbacm7lya00lby6c3t8cfhov6
ahrefs-site-verification_f9a61f3b67e1dc2c6d0c26cccde18e26025778b7851a12c8179d80a...
CAALookup not available with standard resolver
Resolved in 30 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), 707 ms total
PASS
1 redirect(s), 707 ms total
Info::
Single redirect
Got: https://mediafire.com → https://www.mediafire.com/ (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://mediafire.com
Info::
Redirect overhead: 707 ms total
Got: 707 ms

https://mediafire.com

205 ms · HTTP/1.1

302

https://www.mediafire.com/

502 ms · HTTP/1.1 FINAL

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

1855 days

August 11, 2031

SSL certificate

105 days

Issued by Sectigo Limited

Domain age

24 years

Registered August 11, 2002

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

104.17.147.83

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

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 101 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
31 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.
23 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
102 ms
Total Time Total request time from DNS lookup through full response.
102 ms

Connection waterfall

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