Skip to content
https://mega.co.nz

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
96
GRADE
A
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from New York, United Stated
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.

B
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 0 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 0 B Sitemaps referenced 0 User-agents Blocking No — crawling allowed
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Certificate validity

239
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
2 A records, 88 ms lookup
PASS
2 A records, 88 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 66.203.124.31, 66.203.124.30
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2a0b:e46:1:50::31, 2a0b:e46:1:50::30
Info::
4 nameserver(s) configured
Got: nslu1.mega.co.nz, nsnl1.mega.co.nz, nslu2.mega.co.nz, nsnl2.mega.co.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: 88 ms
Got: 88 ms
A66.203.124.31, 66.203.124.30
AAAA2a0b:e46:1:50::31, 2a0b:e46:1:50::30
CNAME
NSnslu1.mega.co.nz, nsnl1.mega.co.nz, nslu2.mega.co.nz, nsnl2.mega.co.nz
MX
10 mail.mega.co.nz
TXT
google-site-verification=0jBOnmEQ7qbx7Y95BUQgzzVEM0AAVbAM_q_sRRrD8RA
MS=04EFAF676E4DF3254C19CAC84E8649DFC352DE7A
SPF v=spf1 ip4:122.56.56.210 ip4:31.216.147.132/30 ip4:31.216.147.136/31 ip6:2001:67...
CAALookup not available with standard resolver
Resolved in 88 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.co.nz

https://mega.co.nz

337 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://mega.co.nz200337 msHTTP/1.1
A+
IPv6 Readiness
IPv6 reachable (81 ms)
PASS
IPv6 reachable (81 ms)
Info::
IPv6 is configured and reachable at 2a0b:e46:1:50::31, 2a0b:e46:1:50::30
Got: 81 ms connect
IPv6 Ready
AAAA Records 2a0b:e46:1:50::31, 2a0b:e46:1:50::30 Connection Reachable (81 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.co.nz/
200https://mega.co.nz/

Preferred variant: non-www

HTTP → HTTPS

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

Consistent

A+
Domain Intelligence
mega.co.nz — via Instra Corporation Pty Ltd., 13 years, 11 months old
PASS
mega.co.nz — via Instra Corporation Pty Ltd., 13 years, 11 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

239 days

Issued by Sectigo Limited

Domain age

13 years, 11 months

Registered July 25, 2012

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Unknown

2a0b:e46:1:50::31

Registrar

Instra Corporation Pty Ltd.

Unlocked 4 NS records
Expiry timeline
Today
+1 year
SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Instra Corporation Pty Ltd.
Created July 25, 2012 (13 years, 11 months ago)
Last Updated November 22, 2025
Name Servers nslu1.mega.co.nz, nslu2.mega.co.nz, nsnl1.mega.co.nz, nsnl2.mega.co.nz
Hosting
IP Address 2a0b:e46:1:50::31
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 340 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
80 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
83 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
92 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
340 ms
Total Time Total request time from DNS lookup through full response.
340 ms

Connection waterfall

DNS Lookup 80 ms TCP Connect 83 ms TLS Handshake 92 ms Server Processing 85 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