eparent.com - dns.ninja
eparent.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=1783724382 | ||||||
rank #233055 in the tld
WOT: SAFE (60/100)
Same first word
Similar names
DNS History
9 records (8 active, 1 former)
●NSns37.domaincontrol.com2015-05-30 → 2026-07-10 · 2 obs
● 2026-07-10 23:09:04
●NSns38.domaincontrol.com2015-05-30 → 2026-07-10 · 2 obs
● 2026-07-10 23:09:04
●MXalt1.aspmx.l.google.com2015-05-30 → 2026-07-10 · 2 obs
● 2026-07-10 23:09:04
●MXalt2.aspmx.l.google.com2015-05-30 → 2026-07-10 · 2 obs
● 2026-07-10 23:09:04
●MXaspmx.l.google.com2015-05-30 → 2026-07-10 · 2 obs
● 2026-07-10 23:09:04
●MXaspmx2.googlemail.com2015-05-30 → 2026-07-10 · 2 obs
● 2026-07-10 23:09:04
●MXaspmx3.googlemail.com2015-05-30 → 2026-07-10 · 2 obs
● 2026-07-10 23:09:04
○A160.153.92.322015-05-30 → 2017-12-27 · 4 obs
● 2017-12-27 19:38:32
○ 2026-03-09 09:11:50
○ 2026-07-10 23:09:04
●A192.124.249.122026-03-09 → 2026-07-10 · 3 obs
● 2026-03-09 09:11:50
● 2026-07-10 23:09:04
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net... | - |
| eparent.com | ns37.domaincontrol.com, ns38.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:173.201.76.19
NS records: ns37.domaincontrol.com, ns38.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for eparent.com (unsigned zone)
⏱️ Timing
Total: 1396ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 192.124.249.12 |
| NS | 2 | ns37.domaincontrol.com, ns38.domaincontrol.com |
| MX | 5 | alt1.aspmx.l.google.com (pri: 5), alt2.aspmx.l.google.com (pri: 5)... |
| TXT | 3 | google-site-verification=ZM62GJ8Mtm8yLP5, v=spf1 a mx ptr include:_spf.emailcampai... |
| SOA | 1 | ns37.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns37.domaincontrol.com, ns37.domaincontrol.com, ns38.domaincontrol.com...)
Analysis
IP Addresses
eparent.com resolves to just one IP address, 192.124.249.12.
Two other host names, along with airwipes.com, romacasual.com and calloway-assoc.com, also share IP numbers with eparent.com.
Name Servers
eparent.com uses two name servers for its delegation: ns37.domaincontrol.com and ns38.domaincontrol.com.
eparent.com shares its NS records with other domains, for example quickseating.com, freshpurple.com, malonegorgeousnails.com and two others.
The two host names ns37.domaincontrol.com and ns38.domaincontrol.com each have a pair of IP addresses: ns37.domaincontrol.com has 97.74.108.19 and 2603:5:21c1::13, and ns38.domaincontrol.com has 173.201.76.19 and 2603:5:22c1::13.
Mail Servers
eparent.com is handled by five mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
There is at least a partial MX overlap between eparent.com and other domains, including ns500693.ns500734.ns500699.ns500734.ns500734.ns500699.ns500588.ns500588.ns500588.ns500588.ns500612.ns500632.ns500588.ns500632.ns500632.ns500110.dtrkdll.com, ns500754.ns500671.ns500754.ns500704.ns500742.ns500704.ns500742.ns500704.ns500649.ns500688.ns500671.ns500649.lustychickser.com, ns500758.ns500758.ns500759.ns500758.ns500759.ns500735.ns500735.ns500736.ns500652.ns500615.tracksymphony.com and two others.
These mail servers tend to appear in combination with mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 others.
Host names that have two IP addresses:
aspmx2.googlemail.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1b.
aspmx3.googlemail.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1b.
aspmx.l.google.com directs traffic to 192.178.155.27 and 2607:f8b0:4004:c1d::1a.
alt1.aspmx.l.google.com directs traffic to 108.177.123.27 and 2800:3f0:4003:c0f::1b.
alt2.aspmx.l.google.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1b.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 2800:3f0:4003:c0f::1b IP addresses each.
Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 2a00:1450:400b:c02::1b IP addresses each.
Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 172.253.116.26 IP addresses each.