dprweb.net - dns.ninja
dprweb.net
net
| 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=1786916604 | ||||||
Same first word
dprweb.net |
Similar names
rpbdwe.lol |
prdweb.com |
rdpweb.com.ar |
webpdr.org |
rdpweb.com |
rpdweb.org |
rdpweb.net |
webprd.com |
webrdp.com |
pdrweb.com |
rpdweb.de |
webdrp.net |
DNS History
9 records (8 active, 1 former)
●NSns1.netnames.net2015-07-16 → 2026-08-16 · 2 obs
● 2026-08-16 21:53:50
●NSns2.netnames.net2015-07-16 → 2026-08-16 · 2 obs
● 2026-08-16 21:53:50
●NSns5.netnames.net2015-07-16 → 2026-08-16 · 2 obs
● 2026-08-16 21:53:50
●NSns6.netnames.net2015-07-16 → 2026-08-16 · 2 obs
● 2026-08-16 21:53:50
●MXrelay1.netnames.net2015-07-16 → 2026-08-16 · 2 obs
● 2026-08-16 21:53:50
●MXrelay2.netnames.net2015-07-16 → 2026-08-16 · 2 obs
● 2026-08-16 21:53:50
●A165.160.13.202026-03-08 → 2026-08-16 · 3 obs
● 2026-03-08 07:52:42
● 2026-08-16 21:53:50
●A165.160.15.202026-03-08 → 2026-08-16 · 3 obs
● 2026-03-08 07:52:42
● 2026-08-16 21:53:50
○A185.26.230.1292015-07-16 → 2017-06-06 · 4 obs
● 2017-06-06 16:53:06
○ 2026-03-08 07:52:42
○ 2026-08-16 21:53:50
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| net | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| dprweb.net | ns2.netnames.net, ns1.netnames.net, ns5.netnames.net, ns6.netnames.net | 8 records |
✅ Authoritative Response
Server:156.154.131.100
NS records: ns2.netnames.net, ns1.netnames.net, ns5.netnames.net, ns6.netnames.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for dprweb.net (unsigned zone)
⏱️ Timing
Total: 354ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 165.160.15.20, 165.160.13.20 |
| NS | 4 | ns1.netnames.net, ns2.netnames.net... |
| MX | 2 | relay1.netnames.net (pri: 10), relay2.netnames.net (pri: 20) |
| TXT | 1 | v=spf1 -all |
| SOA | 1 | ns1.netnames.net hostmaster.cscdns.net |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns2.netnames.net, ns2.netnames.net, ns1.netnames.net...)
Analysis
IP Addresses
dprweb.net points to the IP addresses 165.160.13.20 and 165.160.15.20
Additional host names — truistwachoviaproposal.com, envoygroupairwayssuck.com, rideradvantage.com and two others — share IP numbers with dprweb.net.
Name Servers
dprweb.net has four authoritative name servers: ns1.netnames.net, ns2.netnames.net, ns5.netnames.net and ns6.netnames.net.
The name servers of dprweb.net overlap at least partially with those of other domains — among them k-tradefair.com, x-ingredient.com, frenchconnection.cz and two more.
ns1.netnames.net, ns2.netnames.net, ns5.netnames.net and ns6.netnames.net each have two IP addresses. Specifically, ns1.netnames.net resolves to 156.154.130.100 and 2610:a1:1022::100, ns2.netnames.net resolves to 156.154.131.100 and 2610:a1:1023::100, ns5.netnames.net resolves to 156.154.130.100 and 2610:a1:1022::100 and ns6.netnames.net resolves to 156.154.131.100 and 2610:a1:1023::100.
Host names pointing to 2610:a1:1022::100 IP addresses: ns1.netnames.net and ns5.netnames.net.
Host names pointing to 156.154.130.100 IP addresses: ns1.netnames.net and ns5.netnames.net.
Host names pointing to 2610:a1:1023::100 IP addresses: ns2.netnames.net and ns6.netnames.net.
Host names pointing to 156.154.131.100 IP addresses: ns2.netnames.net and ns6.netnames.net.
Mail Servers
dprweb.net has two mail servers: relay1.netnames.net and relay2.netnames.net.
dprweb.net shares the same mail server setup as other domains, including healthcareassistance.co, sovaldi.be, hublot-classicfusion.com.sg and two others.
dprweb.net has mail servers in common with other domains — aah-point.co.uk being one example.
Both relay1.netnames.net and relay2.netnames.net have a single IP address each — relay1.netnames.net resolves to 185.26.230.83 while relay2.netnames.net resolves to 185.26.230.89.