eventsateg.com - robtex.com
eventsateg.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=1774609697 | ||||||
Same first word
eventsateg.com |
Similar names
DNS History
13 records (13 active, 0 former)
●NSdns1.p02.nsone.net2026-03-03 → 2026-03-27 · 2 obs
● 2026-03-27 11:15:46
●NSdns2.p02.nsone.net2026-03-03 → 2026-03-27 · 2 obs
● 2026-03-27 11:15:46
●NSdns3.p02.nsone.net2026-03-03 → 2026-03-27 · 2 obs
● 2026-03-27 11:15:46
●NSdns4.p02.nsone.net2026-03-03 → 2026-03-27 · 2 obs
● 2026-03-27 11:15:46
●MXalt1.aspmx.l.google.com2026-03-03 → 2026-03-27 · 2 obs
● 2026-03-27 11:15:46
●MXalt2.aspmx.l.google.com2026-03-03 → 2026-03-27 · 2 obs
● 2026-03-27 11:15:46
●MXalt3.aspmx.l.google.com2026-03-03 → 2026-03-27 · 2 obs
● 2026-03-27 11:15:46
●MXalt4.aspmx.l.google.com2026-03-03 → 2026-03-27 · 2 obs
● 2026-03-27 11:15:46
●MXaspmx.l.google.com2026-03-03 → 2026-03-27 · 2 obs
● 2026-03-27 11:15:46
●A198.185.159.1442026-03-03 → 2026-03-27 · 2 obs
● 2026-03-27 11:15:46
●A198.185.159.1452026-03-03 → 2026-03-27 · 2 obs
● 2026-03-27 11:15:46
●A198.49.23.1442026-03-03 → 2026-03-27 · 2 obs
● 2026-03-27 11:15:46
●A198.49.23.1452026-03-03 → 2026-03-27 · 2 obs
● 2026-03-27 11:15:46
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, h.gtld-servers.net... | - |
| eventsateg.com | dns1.p02.nsone.net, dns2.p02.nsone.net, dns3.p02.nsone.net, dns4.p02.nsone.net | - |
✅ Authoritative Response
Server:198.51.44.66
NS records: dns1.p02.nsone.net, dns2.p02.nsone.net, dns3.p02.nsone.net, dns4.p02.nsone.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for eventsateg.com (unsigned zone)
⏱️ Timing
Total: 443ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 4 | 198.185.159.145, 198.49.23.144... |
| NS | 4 | dns1.p02.nsone.net, dns2.p02.nsone.net... |
| MX | 5 | alt1.aspmx.l.google.com (pri: 5), alt4.aspmx.l.google.com (pri: 10)... |
| TXT | 1 | v=spf1 include:_spf.google.com ~all |
| SOA | 1 | dns1.p02.nsone.net hostmaster.nsone.net |
Analysis
IP Addresses
eventsateg.com maps to four IP numbers: 198.49.23.144, 198.49.23.145, 198.185.159.144 and 198.185.159.145.
Other host names, for instance american-sepsis-alliance.com, thelogosuites.com, work-around.com, forgenw.com and clmedicine.com share IP numbers with eventsateg.com.
Name Servers
eventsateg.com's delegation is handled by four name servers: dns1.p02.nsone.net, dns2.p02.nsone.net, dns3.p02.nsone.net and dns4.p02.nsone.net.
eventsateg.com partially shares name servers with other domains; examples include xn--ztt861f.xn--fiq228c5hs, hadoophelp.com, tudorpelagos.it, joesfriendlytavern.com and whiteglovescleaninghq.com.
These name servers are commonly used alongside ns01.squarespacedns.com, ns02.squarespacedns.com, ns03.squarespacedns.com, ns04.squarespacedns.com, dns1.p01.nsone.net, connect1.squarespacedns.com, connect2.squarespacedns.com, dns2.p01.nsone.net, dns3.p01.nsone.net and dns4.p01.nsone.net.
Host names with two IPs:
dns1.p02.nsone.net points to 2620:4d:4000:6259:7:2:0:1 and 198.51.44.2
dns2.p02.nsone.net points to 2a00:edc0:6259:7:2::2 and 198.51.45.2
dns3.p02.nsone.net points to 2620:4d:4000:6259:7:2:0:3 and 198.51.44.66
dns4.p02.nsone.net points to 2a00:edc0:6259:7:2::4 and 198.51.45.66
Mail Servers
Five mail servers handle eventsateg.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.
eventsateg.com shares some mail servers with other domains, at least partially, such as ns500671.ns500742.ns500754.ns500754.ns500731.ns500705.ns500671.ns500688.ns500688.ns500678.ns500291.ns500649.tenderladiesbz.com, ns500765.ns500693.ns500734.ns500699.ns500734.ns500699.ns500699.ns500693.ns500588.ns500699.ns500588.ns500699.ns500693.ns500632.ns500632.ns500110.dtrkdll.com, ns500742.ns500754.ns500742.ns500754.ns500731.ns500705.ns500704.ns500671.ns500671.ns500291.ns500649.ns500142.lusty(0x736c7574)z.com, ns500699.ns500734.ns500699.ns500734.ns500734.ns500734.ns500734.ns500683.ns500699.ns500683.ns500588.ns500588.ns500612.ns500588.ns500578.ns500110.dtrkdll.com and ns500742.ns500671.ns500754.ns500731.ns500742.ns500754.ns500731.ns500742.ns500704.ns500671.ns500671.ns500704.ns500678.ns500678.ns500688.ns500671.ns500649.lustychickser.com.
These mail servers are often 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::1a and 74.125.137.26
alt1.aspmx.l.google.com points to: 2607:f8b0:4023:2801::1a and 192.178.128.26
alt2.aspmx.l.google.com points to: 2607:f8b0:4023:1015::1b and 172.253.135.26
alt3.aspmx.l.google.com points to: 2607:f8b0:4023:3003::1b and 172.253.145.26
alt4.aspmx.l.google.com points to: 2607:f8b0:4003:c4a::1a and 142.251.96.26