dpser.com - dns.ninja
dpser.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=1786285534 | ||||||
Same first word
dpser.com |
Similar names
DNS History
10 records (7 active, 3 former)
●NSdns1.registrar-servers.com2026-03-25 → 2026-08-09 · 3 obs
● 2026-03-25 16:52:28
● 2026-08-09 14:53:46
●NSdns2.registrar-servers.com2026-03-25 → 2026-08-09 · 3 obs
● 2026-03-25 16:52:28
● 2026-08-09 14:53:46
○NSns31.domaincontrol.com2015-08-03 → 2015-08-03 · 3 obs
○ 2026-03-25 16:52:28
○ 2026-08-09 14:53:46
○NSns32.domaincontrol.com2015-08-03 → 2015-08-03 · 3 obs
○ 2026-03-25 16:52:28
○ 2026-08-09 14:53:46
●MXalt1.aspmx.l.google.com2015-08-03 → 2026-08-09 · 2 obs
● 2026-08-09 14:53:46
●MXalt2.aspmx.l.google.com2015-08-03 → 2026-08-09 · 2 obs
● 2026-08-09 14:53:46
●MXaspmx.l.google.com2015-08-03 → 2026-08-09 · 2 obs
● 2026-08-09 14:53:46
●MXaspmx2.googlemail.com2015-08-03 → 2026-08-09 · 2 obs
● 2026-08-09 14:53:46
●MXaspmx3.googlemail.com2015-08-03 → 2026-08-09 · 2 obs
● 2026-08-09 14:53:46
○A50.63.202.152015-08-03 → 2015-08-03 · 3 obs
○ 2026-03-25 16:52:28
○ 2026-08-09 14:53:46
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | g.gtld-servers.net, e.gtld-servers.net, i.gtld-servers.net, k.gtld-servers.net... | - |
| dpser.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 dpser.com (unsigned zone)
⏱️ Timing
Total: 908ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| 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)... |
| TXT | 1 | google-site-verification=yVr0PAe0REXwqC9 |
| 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
Name Servers
dpser.com uses two name servers for its delegation: dns1.registrar-servers.com and dns2.registrar-servers.com.
The name server configuration of dpser.com is shared with other domains, for instance lavie.biz, xn--hy1b91gg6mxkl8mh.com, materuel.com and two others.
The name servers for dpser.com overlap at least in part with those of other domains, including prunehub.com and ngluten.com.
The two host names dns1.registrar-servers.com and dns2.registrar-servers.com each have a pair of IP addresses: dns1.registrar-servers.com has 156.154.132.200 and 2610:a1:1024::200, and dns2.registrar-servers.com has 156.154.133.200 and 2610:a1:1025::200.
Mail Servers
Five mail servers handle dpser.com: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
At least some of the mail servers used by dpser.com are shared with other domains: ns500734.ns500699.ns500699.ns500693.ns500588.ns500693.ns500612.ns500588.ns500588.ns500632.ns500588.ns500588.ns500588.dtrkdll.com, ns500698.ns500758.ns500698.ns500758.ns500758.ns500735.ns500735.ns500736.ns500698.ns500698.ns500576.ns500619.ns500698.ns500652.ns500576.trackreceptor.com, ns500699.ns500734.ns500734.ns500693.ns500699.ns500693.ns500699.ns500699.ns500588.ns500693.ns500699.ns500693.ns500612.ns500632.ns500588.ns500588.ns500588.dtrkdll.com and two others among them.
These mail servers are often deployed together with alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 other mail servers.
Host names pointing to two IP addresses:
aspmx2.googlemail.com directs traffic to 192.178.234.27 and 2800:3f0:4003:c14::1a.
aspmx3.googlemail.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1b.
aspmx.l.google.com directs traffic to 142.250.31.26 and 2607:f8b0:4004:c23::1b.
alt1.aspmx.l.google.com directs traffic to 192.178.234.26 and 2800:3f0:4003:c14::1b.
alt2.aspmx.l.google.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1b.
Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 2a00:1450:400b:c02::1b IP addresses each.