fullproxy.cloud - dns.ninja
fullproxy.cloud
| DNSSEC | ⚠️ Not signed | ||||||
| NS | pns31.cloudns.net ⭐ | ||||||
| A | 2a06:fb00:1::1:66🇧🇬 CLOUDNSNET2a06:fb00:1::/48 ClouDNS | ||||||
| PTR | pns31.cloudns.net | ||||||
| A | 185.136.96.66🇺🇸 CLOUDNSNET185.136.96.0/24 Cloud DNS Ltd | ||||||
| PTR | pns31.cloudns.net | ||||||
| NS | pns32.cloudns.net | ||||||
| A | 2a06:fb00:1::2:66🇧🇬 CLOUDNSNET2a06:fb00:1::/48 ClouDNS | ||||||
| PTR | pns32.cloudns.net | ||||||
| A | 185.136.97.66CLOUDNSNET185.136.97.0/24 Cloud DNS Ltd | ||||||
| PTR | pns32.cloudns.net | ||||||
| NS | pns33.cloudns.net | ||||||
| A | 2a06:fb00:1::3:66🇧🇬 CLOUDNSNET2a06:fb00:1::/48 ClouDNS | ||||||
| PTR | pns33.cloudns.net | ||||||
| A | 185.136.98.66🇺🇸 CLOUDNSNET185.136.98.0/24 Cloud DNS Ltd | ||||||
| PTR | pns33.cloudns.net | ||||||
| NS | pns34.cloudns.net | ||||||
| A | 2a06:fb00:1::4:66🇧🇬 CLOUDNSNET2a06:fb00:1::/48 ClouDNS | ||||||
| PTR | pns34.cloudns.net | ||||||
| A | 185.136.99.66CLOUDNSNET185.136.99.0/24 Cloud DNS Ltd | ||||||
| PTR | pns34.cloudns.net | ||||||
| TXT | v=spf1 include: ip4:43.228.184.0/22 ip4:66.235.120.0/21 ip4:103.2.140.0/22 ip... | ||||||
| SOA | pns31.cloudns.netsupport@cloudns.net 2026-06-20 #4 | ||||||
cloud
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns01.trs-dns.com ⭐ | ||||||
| NS | ns.trs-dns.com | ||||||
| NS | ns01.trs-dns.net | ||||||
| NS | ns10.trs-dns.info | ||||||
| NS | ns10.trs-dns.org | ||||||
| SOA | ns.trs-dns.comtrs-ops@tucows.com serial=1782729328 | ||||||
Same first word
fullproxy.com |
fullproxy.cloud |
Similar names
DNS History
4 records (4 active, 0 former)
●NSpns31.cloudns.net2026-03-25 → 2026-06-29 · 2 obs
● 2026-06-29 11:10:46
●NSpns32.cloudns.net2026-03-25 → 2026-06-29 · 2 obs
● 2026-06-29 11:10:46
●NSpns33.cloudns.net2026-03-25 → 2026-06-29 · 2 obs
● 2026-06-29 11:10:46
●NSpns34.cloudns.net2026-03-25 → 2026-06-29 · 2 obs
● 2026-06-29 11:10:46
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| cloud | ns01.trs-dns.net, ns01.trs-dns.com, ns10.trs-dns.info, ns10.trs-dns.org | - |
| fullproxy.cloud | pns31.cloudns.net, pns32.cloudns.net, pns33.cloudns.net, pns34.cloudns.net | - |
✅ Authoritative Response
Server:185.136.98.66
NS records: pns31.cloudns.net, pns32.cloudns.net, pns33.cloudns.net, pns34.cloudns.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for fullproxy.cloud (unsigned zone)
⏱️ Timing
Total: 325ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | pns34.cloudns.net, pns32.cloudns.net... |
| TXT | 1 | v=spf1 include: ip4:43.228.184.0/22 ip4: |
| SOA | 1 | pns31.cloudns.net support.cloudns.net |
Analysis
Name Servers
The domain fullproxy.cloud is delegated to these four name servers: pns31.cloudns.net, pns32.cloudns.net, pns33.cloudns.net and pns34.cloudns.net.
fullproxy.cloud partially shares its NS delegation with several other domains, including irksails.ru, 27.100.245.172.in-addr.arpa, bestfindikzade.com and two others.
In DNS configurations, these name servers often share authority with ns31.cloudns.net, ns32.cloudns.net, ns34.cloudns.net and 3 other name servers.
pns31.cloudns.net, pns32.cloudns.net, pns33.cloudns.net and pns34.cloudns.net each carry two IP addresses. pns31.cloudns.net has 185.136.96.66 and 2a06:fb00:1::1:66; pns32.cloudns.net has 185.136.97.66 and 2a06:fb00:1::2:66; pns33.cloudns.net has 185.136.98.66 and 2a06:fb00:1::3:66; pns34.cloudns.net has 185.136.99.66 and 2a06:fb00:1::4:66.