wanproxy.net - dns.ninja
wanproxy.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=1786576794 | ||||||
Same first word
DNS History
19 records (7 active, 12 former)
●NSdns1.registrar-servers.com2015-05-31 → 2026-08-12 · 5 obs
● 2016-01-14 03:44:32
○ 2016-04-07 13:37:42
● 2017-04-19 19:18:38
● 2026-08-12 23:37:50
○NSdns1.registrar-servers.com,2016-04-07 → 2017-04-19 · 5 obs
● 2016-04-07 13:37:42
● 2017-04-19 19:18:38
○ 2026-07-07 21:07:14
○ 2026-08-12 23:37:50
●NSdns2.registrar-servers.com2015-05-31 → 2026-08-12 · 2 obs
● 2026-08-12 23:37:50
○NSdns3.registrar-servers.com2015-05-31 → 2017-04-19 · 4 obs
● 2017-04-19 19:18:38
○ 2026-07-07 21:07:14
○ 2026-08-12 23:37:50
○NSdns4.registrar-servers.com2015-05-31 → 2017-04-19 · 4 obs
● 2017-04-19 19:18:38
○ 2026-07-07 21:07:14
○ 2026-08-12 23:37:50
○NSdns5.registrar-servers.com2015-05-31 → 2017-04-19 · 4 obs
● 2017-04-19 19:18:38
○ 2026-07-07 21:07:14
○ 2026-08-12 23:37:50
●MXalt1.aspmx.l.google.com2026-07-07 → 2026-08-12 · 3 obs
● 2026-07-07 21:07:14
● 2026-08-12 23:37:50
●MXalt2.aspmx.l.google.com2026-07-07 → 2026-08-12 · 3 obs
● 2026-07-07 21:07:14
● 2026-08-12 23:37:50
●MXaspmx.l.google.com2026-07-07 → 2026-08-12 · 3 obs
● 2026-07-07 21:07:14
● 2026-08-12 23:37:50
●MXaspmx2.googlemail.com2026-07-07 → 2026-08-12 · 3 obs
● 2026-07-07 21:07:14
● 2026-08-12 23:37:50
●MXaspmx3.googlemail.com2026-07-07 → 2026-08-12 · 3 obs
● 2026-07-07 21:07:14
● 2026-08-12 23:37:50
○MXeforward1.registrar-servers.com2015-05-31 → 2017-04-19 · 4 obs
● 2017-04-19 19:18:38
○ 2026-07-07 21:07:14
○ 2026-08-12 23:37:50
○MXeforward2.registrar-servers.com2015-05-31 → 2017-04-19 · 4 obs
● 2017-04-19 19:18:38
○ 2026-07-07 21:07:14
○ 2026-08-12 23:37:50
○MXeforward3.registrar-servers.com2015-05-31 → 2017-04-19 · 4 obs
● 2017-04-19 19:18:38
○ 2026-07-07 21:07:14
○ 2026-08-12 23:37:50
○MXeforward4.registrar-servers.com2015-05-31 → 2017-04-19 · 4 obs
● 2017-04-19 19:18:38
○ 2026-07-07 21:07:14
○ 2026-08-12 23:37:50
○MXeforward5.registrar-servers.com2015-05-31 → 2017-04-19 · 4 obs
● 2017-04-19 19:18:38
○ 2026-07-07 21:07:14
○ 2026-08-12 23:37:50
○A162.255.119.2512015-12-28 → 2016-01-14 · 5 obs
● 2015-12-28 16:43:06
● 2016-01-14 03:44:32
○ 2016-04-07 13:37:42
○ 2026-08-12 23:37:50
○A162.255.119.52015-05-31 → 2015-10-20 · 4 obs
● 2015-10-20 08:51:26
○ 2015-12-28 16:43:06
○ 2026-08-12 23:37:50
○A192.64.119.1272016-04-07 → 2017-04-19 · 5 obs
● 2016-04-07 13:37:42
● 2017-04-19 19:18:38
○ 2026-07-07 21:07:14
○ 2026-08-12 23:37:50
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| net | m.gtld-servers.net, k.gtld-servers.net, b.gtld-servers.net, f.gtld-servers.net... | - |
| wanproxy.net | dns1.registrar-servers.com, dns2.registrar-servers.com | - |
✅ Authoritative Response
Server:156.154.133.200
NS records: dns1.registrar-servers.com, dns2.registrar-servers.com
🔒 DNSSEC Status
🔐 Secure (DNSSEC validated)
Chain of trust verified from root to domain
⏱️ Timing
Total: 783ms | 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=SjDN7vqLpH43Jzp |
| SOA | 1 | dns1.registrar-servers.com hostmaster.re |
Analysis
Name Servers
wanproxy.net has two authoritative name servers — dns1.registrar-servers.com and dns2.registrar-servers.com.
wanproxy.net uses the same name servers as several other domains — among them performxx.com, ohhlook.com, feedyourbodythebest.net and two more.
wanproxy.net has overlapping name servers with several other domains — among them toescompanyness.com, exquad.com, kikalekki.com and wylvera.com.
The name servers dns3.registrar-servers.com, dns4.registrar-servers.com and dns5.registrar-servers.com are commonly seen alongside these name servers.
Both dns1.registrar-servers.com and dns2.registrar-servers.com have two IP addresses each. dns1.registrar-servers.com resolves to 156.154.132.200 and 2610:a1:1024::200; dns2.registrar-servers.com resolves to 156.154.133.200 and 2610:a1:1025::200.
Mail Servers
Five mail servers handle wanproxy.net: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
wanproxy.net has at least partial mail server overlap with other domains such as ns500759.ns500758.ns500758.ns500758.ns500759.ns500735.ns500698.ns500735.ns500698.ns500735.ns500576.ns500698.ns500708.ns500576.ns500652.ns500576.trackreceptor.com, ns500765.ns500734.ns500734.ns500693.ns500734.ns500693.ns500699.ns500632.ns500683.ns500683.ns500632.ns500632.ns500612.dtrkdll.com, ns500759.ns500758.ns500758.ns500698.ns500758.ns500698.ns500735.ns500698.ns500698.ns500698.ns500576.ns500652.trackreceptor.com and two more.
These mail servers commonly co-occur with mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 others.
Hostnames that resolve to two IP addresses:
aspmx2.googlemail.com resolves to 192.178.234.26 and 2800:3f0:4003:c14::1b.
aspmx3.googlemail.com resolves to 172.253.116.27 and 2a00:1450:400b:c02::1b.
aspmx.l.google.com resolves to 192.179.18.26 and 2607:f8b0:4004:c29::1a.
alt1.aspmx.l.google.com resolves to 192.178.234.27 and 2800:3f0:4003:c14::1b.
alt2.aspmx.l.google.com resolves to 172.253.116.27 and 2a00:1450:400b:c02::1a.
The host names aspmx2.googlemail.com and alt1.aspmx.l.google.com both resolve to 2800:3f0:4003:c14::1b IP addresses.
The host names aspmx3.googlemail.com and alt2.aspmx.l.google.com both resolve to 172.253.116.27 IP addresses.