datagend.com - robtex.com
datagend.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 18.208.88.157🇺🇸 Amazon18.208.0.0/13 EC2 IAD prefix | ||||||
| PTR | ec2-18-208-88-157.compute-1.amazonaws.com | ||||||
| A | 98.84.224.111🇺🇸 Amazon98.80.0.0/13 EC2 IAD Prefix | ||||||
| NS | dns1.p01.nsone.net ⭐ | ||||||
| A | 2620:4d:4000:6259:7:1:0:1🇺🇸 NSONE2620:4d:4000::/48 2620:4D:4000::/48 | ||||||
| PTR | dns1.p01.nsone.net | ||||||
| A | 198.51.44.1🇺🇸 NSONE198.51.44.0/24 198.51.44.0 | ||||||
| PTR | dns1.p01.nsone.net | ||||||
| NS | dns2.p01.nsone.net 🔒 | ||||||
| A | 2a00:edc0:6259:7:1::2🇺🇸 NSONE2a00:edc0:6259::/48 NS1-2 | ||||||
| PTR | dns2.p01.nsone.net | ||||||
| A | 198.51.45.1🇺🇸 NSONE198.51.45.0/24 198.51.45.0 | ||||||
| PTR | dns2.p01.nsone.net | ||||||
| NS | dns3.p01.nsone.net 🔒 | ||||||
| A | 2620:4d:4000:6259:7:1:0:3🇺🇸 NSONE2620:4d:4000::/48 2620:4D:4000::/48 | ||||||
| PTR | dns3.p01.nsone.net | ||||||
| A | 198.51.44.65🇺🇸 NSONE198.51.44.0/24 198.51.44.0 | ||||||
| PTR | dns3.p01.nsone.net | ||||||
| NS | dns4.p01.nsone.net ⚠️ Not in parent delegation | ||||||
| A | 2a00:edc0:6259:7:1::4🇺🇸 NSONE2a00:edc0:6259::/48 NS1-2 | ||||||
| PTR | dns4.p01.nsone.net | ||||||
| A | 198.51.45.65🇺🇸 NSONE198.51.45.0/24 198.51.45.0 | ||||||
| PTR | dns4.p01.nsone.net | ||||||
| SOA | dns1.p01.nsone.netdomains+netlify@netlify.com serial=1677757346 | ||||||
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=1771291435 | ||||||
Same first word
datagend.com |
DNS History
21 records (6 active, 15 former)
○NSdns1.name-services.com2019-12-17 → 2019-12-17 · 3 obs
○ 2026-03-15 03:59:00
○ 2026-03-23 13:15:08
●NSdns1.p01.nsone.net2026-03-15 → 2026-03-23 · 3 obs
● 2026-03-15 03:59:00
● 2026-03-23 13:15:08
○NSdns2.name-services.com2019-12-17 → 2019-12-17 · 3 obs
○ 2026-03-15 03:59:00
○ 2026-03-23 13:15:08
●NSdns2.p01.nsone.net2026-03-15 → 2026-03-23 · 3 obs
● 2026-03-15 03:59:00
● 2026-03-23 13:15:08
○NSdns3.name-services.com2019-12-17 → 2019-12-17 · 3 obs
○ 2026-03-15 03:59:00
○ 2026-03-23 13:15:08
●NSdns3.p01.nsone.net2026-03-15 → 2026-03-23 · 3 obs
● 2026-03-15 03:59:00
● 2026-03-23 13:15:08
○NSdns4.name-services.com2019-12-17 → 2019-12-17 · 3 obs
○ 2026-03-15 03:59:00
○ 2026-03-23 13:15:08
●NSdns4.p01.nsone.net2026-03-15 → 2026-03-23 · 3 obs
● 2026-03-15 03:59:00
● 2026-03-23 13:15:08
○NSdns5.name-services.com2019-12-17 → 2019-12-17 · 3 obs
○ 2026-03-15 03:59:00
○ 2026-03-23 13:15:08
○MXalt1.aspmx.l.google.com2019-12-17 → 2019-12-17 · 3 obs
○ 2026-03-15 03:59:00
○ 2026-03-23 13:15:08
○MXalt2.aspmx.l.google.com2019-12-17 → 2019-12-17 · 3 obs
○ 2026-03-15 03:59:00
○ 2026-03-23 13:15:08
○MXalt3.aspmx.l.google.com2019-12-17 → 2019-12-17 · 3 obs
○ 2026-03-15 03:59:00
○ 2026-03-23 13:15:08
○MXalt4.aspmx.l.google.com2019-12-17 → 2019-12-17 · 3 obs
○ 2026-03-15 03:59:00
○ 2026-03-23 13:15:08
○MXaspmx.l.google.com2019-12-17 → 2019-12-17 · 3 obs
○ 2026-03-15 03:59:00
○ 2026-03-23 13:15:08
○A13.52.188.952026-03-17 → 2026-03-17 · 4 obs
● 2026-03-17 08:04:22
○ 2026-03-18 12:28:48
○ 2026-03-23 13:15:08
●A18.208.88.1572026-03-15 → 2026-03-23 · 5 obs
● 2026-03-15 03:59:00
○ 2026-03-17 08:04:22
○ 2026-03-18 12:28:48
● 2026-03-23 13:15:08
○A35.157.26.1352026-03-18 → 2026-03-18 · 4 obs
○ 2026-03-17 08:04:22
● 2026-03-18 12:28:48
○ 2026-03-23 13:15:08
○A52.52.192.1912026-03-17 → 2026-03-17 · 4 obs
● 2026-03-17 08:04:22
○ 2026-03-18 12:28:48
○ 2026-03-23 13:15:08
○A52.8.83.1872019-12-17 → 2019-12-17 · 3 obs
○ 2026-03-15 03:59:00
○ 2026-03-23 13:15:08
○A63.176.8.2182026-03-18 → 2026-03-18 · 4 obs
○ 2026-03-17 08:04:22
● 2026-03-18 12:28:48
○ 2026-03-23 13:15:08
●A98.84.224.1112026-03-15 → 2026-03-23 · 5 obs
● 2026-03-15 03:59:00
○ 2026-03-17 08:04:22
○ 2026-03-18 12:28:48
● 2026-03-23 13:15:08
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| datagend.com | dns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net | - |
✅ Authoritative Response
Server:198.51.44.65
NS records: dns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for datagend.com (unsigned zone)
⏱️ Timing
Total: 452ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 98.84.224.111, 18.208.88.157 |
| NS | 4 | dns1.p01.nsone.net, dns2.p01.nsone.net... |
| SOA | 1 | dns1.p01.nsone.net domains+netlify.netli |
Analysis
IP Addresses
datagend.com has two IP numbers: 18.208.88.157 and 98.84.224.111.
Other host names, for instance makeupbymar.com, femipero.com, ulen.me, wallet-helpdesk.netlify.app and caes.mx share IP numbers with datagend.com.
Name Servers
datagend.com delegates to four name servers: dns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net and dns4.p01.nsone.net.
datagend.com at least partially shares name servers with other domains, including bigrolexwatches.com, janssen.com, alldesign.com, kodak9.com and therolexinstitute.net.
These name servers are commonly used with ns01.squarespacedns.com, ns02.squarespacedns.com, ns03.squarespacedns.com, ns04.squarespacedns.com, ns01.jnjdns.com, ns02.jnjdns.com, ns03.jnjdns.com, ns04.jnjdns.com, dns1.p03.nsone.net and dns2.p03.nsone.net.
Host names with two IP numbers: dns1.p01.nsone.net points to 2620:4d:4000:6259:7:1:0:1 and 198.51.44.1; dns2.p01.nsone.net points to 2a00:edc0:6259:7:1::2 and 198.51.45.1; dns3.p01.nsone.net points to 2620:4d:4000:6259:7:1:0:3 and 198.51.44.65; dns4.p01.nsone.net points to 2a00:edc0:6259:7:1::4 and 198.51.45.65.