targetproxy.com - robtex.com
targetproxy.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=1776053067 | ||||||
Same first word
targetproxy.com |
Similar names
DNS History
5 records (5 active, 0 former)
●MXmx1.hosting.reg.ru2026-04-12 → 2026-04-13 · 2 obs
● 2026-04-13 04:07:28
●MXmx2.hosting.reg.ru2026-04-12 → 2026-04-13 · 2 obs
● 2026-04-13 04:07:28
●A51.158.162.372026-04-12 → 2026-04-13 · 2 obs
● 2026-04-13 04:07:28
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net... | - |
| targetproxy.com | ns1.reg.ru, ns2.reg.ru | - |
✅ Authoritative Response
Server:176.99.13.11
NS records: ns1.reg.ru, ns2.reg.ru
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for targetproxy.com (unsigned zone)
⏱️ Timing
Total: 829ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 51.158.162.37 |
| NS | 2 | ns1.reg.ru, ns2.reg.ru |
| MX | 2 | mx1.hosting.reg.ru (pri: 10), mx2.hosting.reg.ru (pri: 15) |
| TXT | 2 | google-site-verification=AuXYCcqDtOAoHDC, v=spf1 ip4:31.31.196.47 ip4:79.143.31.15 |
| SOA | 1 | ns1.reg.ru hostmaster.ns1.reg.ru |
Analysis
IP Addresses
targetproxy.com resolves to one IP number: 51.158.162.37.
Name Servers
targetproxy.com is delegated to two name servers ns1.reg.ru and ns2.reg.ru.
targetproxy.com shares the same name server setup as other domains, for instance rta-moscow.com, nikitko.ru, gwy.ru, bayu.ru and atlanty.net.
Host names with ten IP numbers: ns1.reg.ru points to: 2a00:f940:9::1:1, 2a00:f940:9::2:1, 176.99.13.11, 176.99.13.13, 176.99.13.15, 176.99.13.17, 194.58.117.11, 194.58.117.13, 194.58.117.15 and 194.58.117.17. ns2.reg.ru points to: 2a00:f940:9::1:2, 2a00:f940:9::2:2, 176.99.13.12, 176.99.13.14, 176.99.13.16, 176.99.13.18, 194.58.117.12, 194.58.117.14, 194.58.117.16 and 194.58.117.18.
Mail Servers
Two mail servers handle targetproxy.com: mx1.hosting.reg.ru and mx2.hosting.reg.ru.
targetproxy.com shares the same mail server setup as other domains, for instance ai-2.ru, 7diet.ru, boson.su, duetalnik.com and card-printer.ru.
targetproxy.com shares some mail servers with other domains, at least partially, for instance praktika-m.ru, finkom.ru, hotelhistory.ru, printgrad.com and maket-russia.ru.
these mail servers are commonly used with the mail servers mx.yandex.net.
Host names with two IP numbers:
mx1.hosting.reg.ru points to 31.31.194.240 and 31.31.194.241
mx2.hosting.reg.ru points to 31.31.194.240 and 31.31.194.241
Host names pointing to 31.31.194.240: mx1.hosting.reg.ru and mx2.hosting.reg.ru
Host names pointing to 31.31.194.241: mx1.hosting.reg.ru and mx2.hosting.reg.ru