megaad.com - dns.ninja
megaad.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=1782636305 | ||||||
Same first word
Similar names
DNS History
14 records (13 active, 1 former)
●NSdns1.name-services.com2015-06-20 → 2026-06-28 · 2 obs
● 2026-06-28 09:07:46
●NSdns2.name-services.com2015-06-20 → 2026-06-28 · 2 obs
● 2026-06-28 09:07:46
●NSdns3.name-services.com2015-06-20 → 2026-06-28 · 2 obs
● 2026-06-28 09:07:46
●NSdns4.name-services.com2015-06-20 → 2026-06-28 · 2 obs
● 2026-06-28 09:07:46
●NSdns5.name-services.com2015-06-20 → 2026-06-28 · 2 obs
● 2026-06-28 09:07:46
●MXalt1.aspmx.l.google.com2015-06-20 → 2026-06-28 · 2 obs
● 2026-06-28 09:07:46
●MXalt2.aspmx.l.google.com2015-06-20 → 2026-06-28 · 2 obs
● 2026-06-28 09:07:46
●MXaspmx.l.google.com2015-06-20 → 2026-06-28 · 2 obs
● 2026-06-28 09:07:46
●MXaspmx2.googlemail.com2015-06-20 → 2026-06-28 · 2 obs
● 2026-06-28 09:07:46
●MXaspmx3.googlemail.com2015-06-20 → 2026-06-28 · 2 obs
● 2026-06-28 09:07:46
●MXaspmx4.googlemail.com2015-06-20 → 2026-06-28 · 2 obs
● 2026-06-28 09:07:46
●MXaspmx5.googlemail.com2015-06-20 → 2026-06-28 · 2 obs
● 2026-06-28 09:07:46
○A173.192.31.1002015-06-20 → 2017-11-13 · 4 obs
● 2017-11-13 07:49:02
○ 2026-02-21 09:34:50
○ 2026-06-28 09:07:46
●A68.189.90.1212026-02-21 → 2026-06-28 · 3 obs
● 2026-02-21 09:34:50
● 2026-06-28 09:07:46
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| megaad.com | dns1.name-services.com, dns2.name-services.com, dns3.name-services.com, dns4.name-services.com... | 10 records |
✅ Authoritative Response
Server:216.40.47.202
NS records: dns1.name-services.com, dns2.name-services.com, dns3.name-services.com, dns4.name-services.com, dns5.name-services.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for megaad.com (unsigned zone)
⏱️ Timing
Total: 296ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 68.189.90.121 |
| NS | 5 | dns5.name-services.com, dns1.name-services.com... |
| MX | 7 | ASPMX.L.GOOGLE.com (pri: 10), ASPMX4.GOOGLEMAIL.com (pri: 30)... |
| TXT | 1 | google-site-verification=rnI00_Tj-qhXExk |
| SOA | 1 | dns1.name-services.com info.name-service |
📌 Glue Records Collected
Total: 10
Out-of-bailiwick: 10 (dns1.name-services.com, dns1.name-services.com, dns2.name-services.com...)
Analysis
IP Addresses
megaad.com resolves to just one IP address, 68.189.90.121.
Host names like syn-068-189-090-121.biz.spectrum.com are further examples that share IP numbers with megaad.com.
Name Servers
megaad.com delegates to five name servers: dns1.name-services.com, dns2.name-services.com, dns3.name-services.com and two others.
megaad.com shares at least some of its name servers with other domains, including bandbtheaters.com, actionpokerclub.com, daricz.com and two others.
These name servers are frequently paired with the name servers dns4.name-services.com and dns5.name-services.com.
Host names that have two IP addresses:
dns1.name-services.com resolves to two addresses: 64.98.148.137 and 2604:4000:2800:2000:64:98:148:137.
dns2.name-services.com resolves to two addresses: 216.40.47.201 and 2604:4000:0:d:216:40:47:201.
dns3.name-services.com resolves to two addresses: 64.98.148.138 and 2604:4000:2800:2000:64:98:148:138.
dns4.name-services.com resolves to two addresses: 216.40.47.202 and 2604:4000:0:d:216:40:47:202.
dns5.name-services.com resolves to two addresses: 64.98.148.139 and 2604:4000:2800:2000:64:98:148:139.
Mail Servers
megaad.com is handled by 7 mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx4.googlemail.com and 4 other.
There is at least a partial MX overlap between megaad.com and other domains, including ns500758.ns500759.ns500759.ns500736.ns500698.ns500698.ns500735.ns500698.ns500708.ns500619.ns500686.ns500619.trackreceptor.com, ns500731.ns500671.ns500742.ns500754.ns500671.ns500705.ns500671.ns500688.ns500688.ns500291.tenderladiesbz.com, ns500754.ns500742.ns500671.ns500671.ns500754.ns500688.ns500704.ns500671.ns500671.ns500671.lusty(0x736c7574)z.com and two others.
These mail servers tend to appear in combination with mail servers alt1.aspmx.l.google.com, aspmx.l.google.com, alt2.aspmx.l.google.com and 3 others.
Host names that have two IP addresses:
aspmx2.googlemail.com resolves to two addresses: 108.177.123.27 and 2800:3f0:4003:c0f::1b.
aspmx3.googlemail.com resolves to two addresses: 172.253.116.26 and 2a00:1450:400b:c02::1b.
aspmx4.googlemail.com resolves to two addresses: 192.178.223.27 and 2a00:1450:4009:c0f::1a.
aspmx5.googlemail.com resolves to two addresses: 172.253.157.26 and 2a00:1450:400c:c23::1b.
aspmx.l.google.com resolves to two addresses: 142.251.179.26 and 2607:f8b0:4004:c1d::1a.
alt1.aspmx.l.google.com resolves to two addresses: 108.177.123.26 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com resolves to two addresses: 172.253.116.26 and 2a00:1450:400b:c02::1b.
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.26 IP addresses.