megango.com - dns.ninja
megango.com
com
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.gtld-servers.net ⭐ | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1786589004 | ||||||
Same first word
Similar names
gaomeng.net.cn |
gomange.com |
gongame.com |
menggao.com |
gamegon.com |
meganog.com |
megagon.ai |
gomegan.com |
ngogame.ru |
magegon.com |
megaong.com |
nogemag.ca |
gagomen.com |
DNS History
11 records (11 active, 0 former)
●NSkip.ns.cloudflare.com2026-03-07 → 2026-08-13 · 2 obs
● 2026-08-13 03:04:10
●NSzoe.ns.cloudflare.com2026-03-07 → 2026-08-13 · 2 obs
● 2026-08-13 03:04:10
●MXalt1.aspmx.l.google.com2026-03-07 → 2026-08-13 · 2 obs
● 2026-08-13 03:04:10
●MXalt2.aspmx.l.google.com2026-03-07 → 2026-08-13 · 2 obs
● 2026-08-13 03:04:10
●MXalt3.aspmx.l.google.com2026-03-07 → 2026-08-13 · 2 obs
● 2026-08-13 03:04:10
●MXalt4.aspmx.l.google.com2026-03-07 → 2026-08-13 · 2 obs
● 2026-08-13 03:04:10
●MXaspmx.l.google.com2026-03-07 → 2026-08-13 · 2 obs
● 2026-08-13 03:04:10
●A104.21.88.1762026-03-07 → 2026-08-13 · 2 obs
● 2026-08-13 03:04:10
●A172.67.151.1422026-03-07 → 2026-08-13 · 2 obs
● 2026-08-13 03:04:10
●A2606:4700:3033::6815:58b02026-03-07 → 2026-08-13 · 2 obs
● 2026-08-13 03:04:10
●A2606:4700:3037::ac43:978e2026-03-07 → 2026-08-13 · 2 obs
● 2026-08-13 03:04:10
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| megango.com | kip.ns.cloudflare.com, zoe.ns.cloudflare.com | 12 records |
✅ Authoritative Response
Server:108.162.193.128
NS records: kip.ns.cloudflare.com, zoe.ns.cloudflare.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for megango.com (unsigned zone)
⏱️ Timing
Total: 185ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 172.67.151.142, 104.21.88.176 |
| AAAA | 2 | 2606:4700:3033::6815:58b0, 2606:4700:3037::ac43:978e |
| NS | 2 | kip.ns.cloudflare.com, zoe.ns.cloudflare.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)... |
| TXT | 3 | facebook-domain-verification=6662s7xvu8e, google-site-verification=ysLwpVczgb8tdVn... |
| HTTPS | 1 | {"priority":1,"target":".","alpn":["h3", |
| SOA | 1 | kip.ns.cloudflare.com dns.cloudflare.com |
📌 Glue Records Collected
Total: 12
Out-of-bailiwick: 12 (kip.ns.cloudflare.com, kip.ns.cloudflare.com, kip.ns.cloudflare.com...)
Analysis
IP Addresses
megango.com directs to four IP numbers, which are 104.21.88.176, 172.67.151.142, 2606:4700:3033::6815:58b0 and 2606:4700:3037::ac43:978e.
Among the host names that share IP numbers with megango.com are genorman.com, adpool.hiperad.com, mrds-gw.cloud and two others.
Name Servers
The NS records for megango.com delegate to kip.ns.cloudflare.com and zoe.ns.cloudflare.com.
megango.com has the same name server delegation as a number of other domains, such as themevip.net, betonwerkenlombaert.be, hamblin.com.au and two more.
At least some of megango.com's name servers are shared with other domains, for example gousd.com, invenura.com, bed-bugs.org and two more.
These name servers tend to be used in conjunction with the name servers aiden.ns.cloudflare.com.
Host names resolving to 6 IP numbers:
kip.ns.cloudflare.com maps to 108.162.193.128, 172.64.33.128, 173.245.59.128 and 3 additional IP addresses.
zoe.ns.cloudflare.com maps to 108.162.192.149, 172.64.32.149, 173.245.58.149 and 3 additional IP addresses.
Mail Servers
Five mail servers handle megango.com: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
megango.com shares at least some of its mail servers with other domains — for example 1password.ca, st-thomashospital.com, clicks.media and two more.
It is common to find these mail servers paired with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 more.
Hosts with two IP numbers each:
The A records for aspmx.l.google.com return 172.253.122.27 and 2607:f8b0:4004:c17::1b.
The A records for alt1.aspmx.l.google.com return 192.178.234.26 and 2800:3f0:4003:c14::1b.
The A records for alt2.aspmx.l.google.com return 172.253.116.27 and 2a00:1450:400b:c02::1b.
The A records for alt3.aspmx.l.google.com return 192.178.223.27 and 2a00:1450:4009:c0f::1b.
The A records for alt4.aspmx.l.google.com return 172.253.157.26 and 2a00:1450:400c:c23::1b.