mgeventplanning.com - robtex.com
mgeventplanning.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=1778732761 | ||||||
Same first word
mgeventplanning.com |
DNS History
10 records (10 active, 0 former)
●NSns1.wordpress.com2020-04-07 → 2026-05-14 · 2 obs
● 2026-05-14 04:42:42
●NSns2.wordpress.com2020-04-07 → 2026-05-14 · 2 obs
● 2026-05-14 04:42:42
●NSns3.wordpress.com2020-04-07 → 2026-05-14 · 2 obs
● 2026-05-14 04:42:42
●MXalt1.aspmx.l.google.com2020-04-07 → 2026-05-14 · 2 obs
● 2026-05-14 04:42:42
●MXalt2.aspmx.l.google.com2020-04-07 → 2026-05-14 · 2 obs
● 2026-05-14 04:42:42
●MXalt3.aspmx.l.google.com2020-04-07 → 2026-05-14 · 2 obs
● 2026-05-14 04:42:42
●MXalt4.aspmx.l.google.com2020-04-07 → 2026-05-14 · 2 obs
● 2026-05-14 04:42:42
●MXaspmx.l.google.com2020-04-07 → 2026-05-14 · 2 obs
● 2026-05-14 04:42:42
●A192.0.78.242020-04-07 → 2026-05-14 · 2 obs
● 2026-05-14 04:42:42
●A192.0.78.252020-04-07 → 2026-05-14 · 2 obs
● 2026-05-14 04:42:42
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| mgeventplanning.com | ns1.wordpress.com, ns2.wordpress.com, ns3.wordpress.com | 6 records |
✅ Authoritative Response
Server:198.181.117.9
NS records: ns1.wordpress.com, ns2.wordpress.com, ns3.wordpress.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for mgeventplanning.com (unsigned zone)
⏱️ Timing
Total: 276ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 192.0.78.24, 192.0.78.25 |
| NS | 3 | ns1.wordpress.com, ns3.wordpress.com... |
| MX | 5 | alt2.aspmx.l.google.com (pri: 5), aspmx.l.google.com (pri: 1)... |
| TXT | 1 | v=spf1 include:_spf.wpcloud.com ~all |
| SOA | 1 | ns1.wordpress.com hostmaster.wordpress.c |
📌 Glue Records Collected
Total: 6
Out-of-bailiwick: 6 (ns1.wordpress.com, ns1.wordpress.com, ns2.wordpress.com...)
Analysis
IP Addresses
mgeventplanning.com points to two IPs: 192.0.78.24 and 192.0.78.25.
Other host names including salcadunyasi.com, t3chguybr1.com, mcgregor-alexander.com, cto-lens.com and brig7e.com share IP numbers with mgeventplanning.com.
Name Servers
mgeventplanning.com is delegated to three name servers: ns1.wordpress.com, ns2.wordpress.com and ns3.wordpress.com.
mgeventplanning.com at least partially shares name servers with other domains, including punktwissen.com, cityofchicago.com, opencrowd.com, viversempressa.com and appdop.com.
Host names with two IP numbers:
ns1.wordpress.com points to: 2a04:fa87:ffff::c6b5:7409 and 198.181.116.9
ns2.wordpress.com points to: 2a04:fa87:ffff::c6b5:7509 and 198.181.117.9
ns3.wordpress.com points to: 2620:115:c00f::c000:4a09 and 192.0.74.9
Mail Servers
mgeventplanning.com is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and alt4.aspmx.l.google.com.
The mail servers for mgeventplanning.com are shared with other domains, for instance filmybox.com, proplussourcing.com, canalcontemporaneo.art.br, maestroconsulting.co.za and ns500841.ns500794.ns500841.ns500794.ns500821.ns500821.ns500821.ns500795.ns500794.ns500821.ns500821.ns500821.ns500790.ns500795.lustypartnersfinder.com.
these mail servers are commonly used with aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx4.googlemail.com and aspmx5.googlemail.com.
Host names with two IP numbers:
aspmx.l.google.com points to 2607:f8b0:4023:c06::1b and 142.250.101.27.
alt1.aspmx.l.google.com points to 2607:f8b0:4023:2801::1a and 192.178.128.27.
alt2.aspmx.l.google.com points to 2607:f8b0:4023:3003::1a and 172.253.145.26.
alt3.aspmx.l.google.com points to 2607:f8b0:4023:1015::1b and 172.253.135.26.
alt4.aspmx.l.google.com points to 2a00:1450:400c:c00::1a and 173.194.76.26.