Skip to content
https://mega.nz

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
93
GRADE
A
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
6 PASS 2 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
Crawlability
Action
robots.txt present, sitemap with 30 URLs
REVIEW
robots.txt present, sitemap with 30 URLs
Info::
robots.txt is present
Got: 1798 bytes
Critical::
robots.txt blocks all crawlers
Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 30 entries
Info::
robots.txt references sitemap

Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.

Why this matters

Disallow: / in robots.txt blocks every search crawler — the site becomes invisible in organic search.

Learn more

Common deployment mistake: a staging robots.txt with `User-agent: * / Disallow: /` ships to prod. The site falls out of search results within days. Verify your robots.txt is the production-intended version. If this is intentional (private site), no action needed.

Source: Google Search Central

robots.txt 200 OK
Size 1798 B Sitemaps referenced 3 User-agents facebookexternalhit, *, Twitterbot Blocking Yes — all crawlers blocked
User-agent: Twitterbot
Allow: /file
Allow: /folder
Allow: /chat
Allow: /objectstorage

User-agent: facebookexternalhit
Allow: /file
Allow: /folder
Allow: /chat
Allow: /objectstorage

User-agent: *
Disallow: /
Allow: /$
Allow: /start
Allow: /business
Allow: /mobile
Allow: /ios
Allow: /android
Allow: /sync
Allow: /cmd
Allow: /extensions
Allow: /chrome
Allow: /edge
Allow: /firefox
Allow: /bird
Allow: /desktop
Allow: /secureboot
Allow: /favicon
Allow: /manifest.json
Allow: /*.css
Allow: /*.js
Allow: /*.json
Allow: /*.png
Allow: /*.svg
Allow: /nas
Allow: /help
Allow: /about
Allow: /developers
Allow: /uwp
Allow: /linux
Allow: /pro
Allow: /resellers
Allow: /corporate
Allow: /contact
Allow: /blog
Allow: /security
Allow: /collaboration
Allow: /securechat
Allow: /cookie
Allow: /storage
Allow: /credits
Allow: /terms
Allow: /privacy
Allow: /copyright
Allow: /takedown
Allow: /gdpr
Allow: /sourcecode
Allow: /sdk
Allow: /doc
Allow: /refer
Allow: /wp$
Allow: /downloadapp
Allow: /register
Allow: /recovery
Allow: /dev
Allow: /disputenotice
Allow: /login
Allow: /achievements
Allow: /registerb
Allow: /register
Allow: /cookie
Allow: /dispute
Allow: /sdkterms
Allow: /objectstorage
Allow: /Mega_Transparency_Report*
Allow: /*sitemap*
Allow: /ads.txt
Allow: /lang_*
Allow: /?ar
Allow: /?br
Allow: /?cn
Allow: /?ct
Allow: /?de
Allow: /?en
Allow: /?en-ph
Allow: /?es
Allow: /?fr
Allow: /?id
Allow: /?it
Allow: /?ja
Allow: /?jp
Allow: /?ko
Allow: /?kr
Allow: /?nl
Allow: /?pl
Allow: /?pt
Allow: /?pt-br
Allow: /?ro
Allow: /?ru
Allow: /?ru-mo
Allow: /?th
Allow: /?vn
Allow: /?vi
Allow: /?zh
Allow: /?zh-cn
Allow: /?zh-hk
Allow: /?zh-sg
Allow: /?zh-tw
Allow: /?nz=1

sitemap: https://mega.nz/sitemap.xml
sitemap: https://cms2.mega.nz/unsigned/sitemap-help.xml
sitemap: https://cms2.mega.nz/unsigned/blog.xml

sitemap.xml 200 OK
C
TLS Certificate Expiry & Recommendations
Action
21 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

21
days left
0d 30d 60d 90d+
Renew soon — under 30 days remaining

Recommended actions

  • Renew certificate — 21 days remaining
  • 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
2 A records, 33 ms lookup
PASS
2 A records, 33 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 31.216.145.5, 31.216.144.5
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2a0b:e46:1:145::5, 2a0b:e46:1:144::5
Info::
4 nameserver(s) configured
Got: nsnl2.mega.nz, nsnl1.mega.nz, nslu1.mega.nz, nslu2.mega.nz
Info::
1 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: 33 ms
Got: 33 ms
A31.216.145.5, 31.216.144.5
AAAA2a0b:e46:1:145::5, 2a0b:e46:1:144::5
CNAME
NSnsnl2.mega.nz, nsnl1.mega.nz, nslu1.mega.nz, nslu2.mega.nz
MX
10 mail.mega.co.nz
TXT
6b9a442bef678c91ce4aaf66dfb6c438
SPF v=spf1 ip4:122.56.56.210 ip4:31.216.147.132/30 ip4:31.216.147.136/31 ip4:31.216....
google-site-verification=eYzEf0tV_bQerKRYO3PwDptch5jNR_isXfhbxn7EM0A
CAALookup not available with standard resolver
Resolved in 33 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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://mega.nz

https://mega.nz

84 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://mega.nz20084 msHTTP/1.1
A+
IPv6 Readiness
IPv6 reachable (27 ms)
PASS
IPv6 reachable (27 ms)
Info::
IPv6 is configured and reachable at 2a0b:e46:1:145::5, 2a0b:e46:1:144::5
Got: 27 ms connect
IPv6 Ready
AAAA Records 2a0b:e46:1:145::5, 2a0b:e46:1:144::5 Connection Reachable (27 ms)
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.mega.nz/
200https://mega.nz/

Preferred variant: non-www

HTTP → HTTPS

301http://mega.nz/ https://mega.nz

Consistent

A+
Domain Intelligence
mega.nz — via Instra Corporation Pty Ltd., 11 years, 8 months old
PASS
mega.nz — via Instra Corporation Pty Ltd., 11 years, 8 months old
Info::
Registrar: Instra Corporation Pty Ltd.
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.
Domain expiry

Unknown

SSL certificate

21 days

Issued by Let's Encrypt

Domain age

11 years, 8 months

Registered October 1, 2014

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Unknown

2a0b:e46:1:144::5

Registrar

Instra Corporation Pty Ltd.

Unlocked 4 NS records
Expiry timeline
Today
+1 year
SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the TLS certificate or verify auto-renewal is working
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Instra Corporation Pty Ltd.
Created October 1, 2014 (11 years, 8 months ago)
Last Updated November 22, 2025
Name Servers nslu1.mega.nz, nslu2.mega.nz, nsnl1.mega.nz, nsnl2.mega.nz
Hosting
IP Address 2a0b:e46:1:144::5
Data source: whois (1.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 109 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
21 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
29 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
30 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
109 ms
Total Time Total request time from DNS lookup through full response.
110 ms

Connection waterfall

DNS Lookup 21 ms TCP Connect 29 ms TLS Handshake 30 ms Server Processing 29 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