mylavishevent.com - robtex.com
mylavishevent.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=1777007261 | ||||||
Same first word
mylavishevent.com |
DNS History
12 records (8 active, 4 former)
○NSbuy.internettraffic.com2015-05-20 → 2015-05-20 · 3 obs
○ 2015-10-21 00:55:22
○ 2026-04-24 05:28:18
●NSdns1.registrar-servers.com2017-06-07 → 2026-04-24 · 3 obs
● 2017-06-07 11:56:00
● 2026-04-24 05:28:18
●NSdns2.registrar-servers.com2017-06-07 → 2026-04-24 · 3 obs
● 2017-06-07 11:56:00
● 2026-04-24 05:28:18
○NSsell.internettraffic.com2015-05-20 → 2015-05-20 · 3 obs
○ 2015-10-21 00:55:22
○ 2026-04-24 05:28:18
●MXalt1.aspmx.l.google.com2017-06-07 → 2026-04-24 · 2 obs
● 2026-04-24 05:28:18
●MXalt2.aspmx.l.google.com2017-06-07 → 2026-04-24 · 2 obs
● 2026-04-24 05:28:18
●MXalt3.aspmx.l.google.com2017-06-07 → 2026-04-24 · 2 obs
● 2026-04-24 05:28:18
●MXalt4.aspmx.l.google.com2017-06-07 → 2026-04-24 · 2 obs
● 2026-04-24 05:28:18
●MXaspmx.l.google.com2017-06-07 → 2026-04-24 · 2 obs
● 2026-04-24 05:28:18
●A162.241.30.482026-03-05 → 2026-04-24 · 3 obs
● 2026-03-05 14:02:10
● 2026-04-24 05:28:18
○A192.64.119.1352017-06-07 → 2017-06-07 · 4 obs
● 2017-06-07 11:56:00
○ 2026-03-05 14:02:10
○ 2026-04-24 05:28:18
○A69.172.201.2082015-05-20 → 2015-05-20 · 3 obs
○ 2015-10-21 00:55:22
○ 2026-04-24 05:28:18
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | d.gtld-servers.net, f.gtld-servers.net, m.gtld-servers.net, l.gtld-servers.net... | - |
| mylavishevent.com | dns1.registrar-servers.com, dns2.registrar-servers.com | 4 records |
✅ Authoritative Response
Server:156.154.133.200
NS records: dns1.registrar-servers.com, dns2.registrar-servers.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for mylavishevent.com (unsigned zone)
⏱️ Timing
Total: 212ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 162.241.30.48 |
| NS | 2 | dns1.registrar-servers.com, dns2.registrar-servers.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)... |
| SOA | 1 | dns1.registrar-servers.com hostmaster.re |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (dns1.registrar-servers.com, dns1.registrar-servers.com, dns2.registrar-servers.com...)
Analysis
IP Addresses
mylavishevent.com points to IP number 162.241.30.48.
For instance, other host names phillyfork.com, ftp.glasssystems.biz, primoak.com, prognozai.com and campbayou.org share IP numbers with mylavishevent.com.
Name Servers
mylavishevent.com is delegated to two name servers: dns1.registrar-servers.com and dns2.registrar-servers.com.
mylavishevent.com uses the same name server setup as other domains such as beerbadge.net, lottosonline.net, tanball.com, mangaking.net and crochet-blankets.com.
mylavishevent.com shares name servers with other domains at least partially, for example codenameverity.com, bradsohn.net, ratemyhaiku.com, fedorets.com and berlindermatology.net.
These name servers are commonly used with dns3.registrar-servers.com, dns4.registrar-servers.com and dns5.registrar-servers.com.
Host names with two IP numbers:
dns1.registrar-servers.com points to 2610:a1:1024::200 and 156.154.132.200; dns2.registrar-servers.com points to 2610:a1:1025::200 and 156.154.133.200.
Mail Servers
Five mail servers handle mylavishevent.com: 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.
mylavishevent.com shares mail servers with other domains at least partially; for instance orange-ed.org, ns500699.ns500699.ns500734.ns500699.ns500693.ns500699.ns500734.ns500734.ns500588.ns500632.ns500632.ns500588.ns500602.ns500578.ns500110.dtrkdll.com, royalmovingco.com, turi.co and toporets.ru.
These mail servers are often used alongside 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:4004:c06::1b and 192.178.155.27
alt1.aspmx.l.google.com points to 2800:3f0:4003:c0f::1b and 108.177.123.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 2a00:1450:4009:c0f::1b and 192.178.223.26
alt4.aspmx.l.google.com points to 2a00:1450:400c:c00::1a and 173.194.76.27