mega.to - dns.ninja
mega.to
to
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns01.trs-dns.com ⭐ | ||||||
| NS | ns.trs-dns.com | ||||||
| NS | ns01.trs-dns.net | ||||||
| NS | ns10.trs-dns.info | ||||||
| NS | ns10.trs-dns.org | ||||||
| SOA | ns.trs-dns.comtrs-ops@tucows.com serial=1786750817 | ||||||
Same first word
Similar names
DNS History
8 records (3 active, 5 former)
●NSa.dns.park.io2019-08-13 → 2026-08-15 · 3 obs
● 2019-08-13 05:27:42
● 2026-08-15 00:10:42
●NSb.dns.park.io2026-03-21 → 2026-08-15 · 3 obs
● 2026-03-21 21:02:04
● 2026-08-15 00:10:42
○NSns1.mega.to2009-01-14 → 2017-08-20 · 4 obs
● 2017-08-20 10:41:32
○ 2019-08-13 05:27:42
○ 2026-08-15 00:10:42
○NSns2.mega.to2009-01-14 → 2017-08-20 · 4 obs
● 2017-08-20 10:41:32
○ 2019-08-13 05:27:42
○ 2026-08-15 00:10:42
○MXmail.mega.to2009-01-14 → 2009-01-14 · 3 obs
○ 2015-08-22 23:07:14
○ 2026-08-15 00:10:42
○A66.234.10.242009-01-14 → 2009-01-14 · 3 obs
○ 2015-08-22 23:07:14
○ 2026-08-15 00:10:42
○A72.51.37.462015-08-22 → 2017-08-20 · 5 obs
● 2015-08-22 23:07:14
● 2017-08-20 10:41:32
○ 2019-08-13 05:27:42
○ 2026-08-15 00:10:42
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| to | ns10.trs-dns.org, ns01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.info | 8 records |
| mega.to | a.dns.park.io, b.dns.park.io | - |
✅ Authoritative Response
Server:54.225.121.213
NS records: a.dns.park.io, b.dns.park.io
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for to (unsigned zone)
⏱️ Timing
Total: 1175ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| CNAME | 1 | park.io |
| SOA | 1 | a.dns.park.io 2014070706 |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns10.trs-dns.org, ns10.trs-dns.org, ns01.trs-dns.com...)
Analysis
IP Addresses
mega.to resolves to the IP addresses 34.207.2.9 and 100.50.238.73
app.park.io and park.io, along with other host names, share IP addresses with mega.to.
Name Servers
mega.to has four authoritative name servers: ns-441.awsdns-55.com, ns-672.awsdns-20.net, ns-1348.awsdns-40.org and ns-1624.awsdns-11.co.uk.
mega.to partially shares its NS delegation with several other domains, including buyerlink.cloud, d1e40ja0gytjxt.cloudfront.net, unrwa.es and two others.
ns-441.awsdns-55.com, ns-672.awsdns-20.net, ns-1348.awsdns-40.org and ns-1624.awsdns-11.co.uk each carry two IP addresses. ns-441.awsdns-55.com has 205.251.193.185 and 2600:9000:5301:b900::1; ns-672.awsdns-20.net has 205.251.194.160 and 2600:9000:5302:a000::1; ns-1348.awsdns-40.org has 205.251.197.68 and 2600:9000:5305:4400::1; ns-1624.awsdns-11.co.uk has 205.251.198.88 and 2600:9000:5306:5800::1.
Mail Servers
mega.to is handled by five mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
mega.to shares mail servers — at least in part — with other domains, including empear.com, lossrunsolutions.com, ditch-magnets.com and two others.
These mail servers are frequently used alongside mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 other.
Host names with two IP numbers:
aspmx2.googlemail.com resolves to two addresses: 192.178.234.27 and 2800:3f0:4003:c14::1b.
aspmx3.googlemail.com resolves to two addresses: 172.253.116.27 and 2a00:1450:400b:c02::1b.
aspmx.l.google.com resolves to two addresses: 142.251.16.27 and 2607:f8b0:4004:c29::1b.
alt1.aspmx.l.google.com resolves to two addresses: 192.178.234.27 and 2800:3f0:4003:c14::1b.
alt2.aspmx.l.google.com resolves to two addresses: 172.253.116.27 and 2a00:1450:400b:c02::1b.
aspmx2.googlemail.com along with alt1.aspmx.l.google.com each resolve to 2800:3f0:4003:c14::1b IP addresses.
aspmx2.googlemail.com along with alt1.aspmx.l.google.com each resolve to 192.178.234.27 IP addresses.
aspmx3.googlemail.com along with alt2.aspmx.l.google.com each resolve to 2a00:1450:400b:c02::1b IP addresses.
aspmx3.googlemail.com along with alt2.aspmx.l.google.com each resolve to 172.253.116.27 IP addresses.