cloudproxy.in - dns.ninja
cloudproxy.in
in
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns.trs-dns.com ⭐ | ||||||
| NS | ns1.registry.in | ||||||
| NS | ns2.registry.in | ||||||
| NS | ns3.registry.in | ||||||
| NS | ns4.registry.in | ||||||
| SOA | ns.trs-dns.comtrs-ops@tucows.com serial=1783735550 | ||||||
Subdomains
www.cloudproxy.in |
Same first word
cloudproxy.app |
cloudproxy.link |
cloudproxy.ca |
cloudproxy.digital |
cloudproxy.info |
cloudproxy.xyz |
cloudproxy.in |
cloudproxy.org |
Similar names
DNS History
13 records (11 active, 2 former)
●NSdemi.ns.cloudflare.com2026-04-03 → 2026-07-11 · 2 obs
● 2026-07-11 02:41:48
●NSleland.ns.cloudflare.com2026-04-03 → 2026-07-11 · 2 obs
● 2026-07-11 02:41:48
●MXalt1.aspmx.l.google.com2026-04-03 → 2026-07-11 · 2 obs
● 2026-07-11 02:41:48
●MXalt2.aspmx.l.google.com2026-04-03 → 2026-07-11 · 2 obs
● 2026-07-11 02:41:48
●MXalt3.aspmx.l.google.com2026-04-03 → 2026-07-11 · 2 obs
● 2026-07-11 02:41:48
●MXalt4.aspmx.l.google.com2026-04-03 → 2026-07-11 · 2 obs
● 2026-07-11 02:41:48
●MXaspmx.l.google.com2026-04-03 → 2026-07-11 · 2 obs
● 2026-07-11 02:41:48
●A104.21.53.32026-04-03 → 2026-07-11 · 2 obs
● 2026-07-11 02:41:48
●A172.67.206.1422026-04-03 → 2026-07-11 · 2 obs
● 2026-07-11 02:41:48
○A2606:4700:3032::6815:35032026-04-03 → 2026-06-15 · 4 obs
● 2026-06-15 12:20:20
○ 2026-06-24 06:40:44
○ 2026-07-11 02:41:48
●A2606:4700:3032::ac43:ce8e2026-06-24 → 2026-07-11 · 3 obs
● 2026-06-24 06:40:44
● 2026-07-11 02:41:48
○A2606:4700:3034::ac43:ce8e2026-04-03 → 2026-06-15 · 4 obs
● 2026-06-15 12:20:20
○ 2026-06-24 06:40:44
○ 2026-07-11 02:41:48
●A2606:4700:3035::6815:35032026-06-24 → 2026-07-11 · 3 obs
● 2026-06-24 06:40:44
● 2026-07-11 02:41:48
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| in | ns2.registry.in, ns1.registry.in, ns4.registry.in, ns3.registry.in | - |
| cloudproxy.in | demi.ns.cloudflare.com, leland.ns.cloudflare.com | - |
✅ Authoritative Response
Server:172.64.32.95
NS records: demi.ns.cloudflare.com, leland.ns.cloudflare.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for cloudproxy.in (unsigned zone)
⏱️ Timing
Total: 512ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 172.67.206.142, 104.21.53.3 |
| AAAA | 2 | 2606:4700:3035::6815:3503, 2606:4700:3032::ac43:ce8e |
| NS | 2 | demi.ns.cloudflare.com, leland.ns.cloudflare.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)... |
| TXT | 3 | MS=ms63830406, google-site-verification=Hp5CB_NoJaw0EPI... |
| HTTPS | 1 | {"priority":1,"target":".","alpn":["h3", |
| SOA | 1 | demi.ns.cloudflare.com dns.cloudflare.co |
Analysis
Hierarchy
www.cloudproxy.in is delegated beneath cloudproxy.in.
IP Addresses
cloudproxy.in points to the four IP addresses 104.21.53.3, 172.67.206.142, 2606:4700:3032::ac43:ce8e and 2606:4700:3035::6815:3503.
schliferclinic.com, favbet555.com, locaacademiafamiliar.com and two other host names share IP numbers with cloudproxy.in.
Name Servers
cloudproxy.in has two authoritative name servers — demi.ns.cloudflare.com and leland.ns.cloudflare.com.
cloudproxy.in uses the same name servers as several other domains — among them fourseasonsportal.com, votingportals.com, brickellhouseportal.com and two more.
There is at least partial name server overlap between cloudproxy.in and other domains — vino-divino.it, joearcher.ca, rudraksha-gemstones.com and two more among them.
These name servers are routinely deployed together with the name servers fay.ns.cloudflare.com.
Hostnames that resolve to 6 IP addresses:
demi.ns.cloudflare.com points to 108.162.192.95, 172.64.32.95, 173.245.58.95 and 3 other IP addresses.
leland.ns.cloudflare.com points to 108.162.195.8, 162.159.44.8, 172.64.35.8 and 3 other IP addresses.
Mail Servers
cloudproxy.in has five mail servers, which are aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
cloudproxy.in has at least partial mail server overlap with other domains such as grupocalf.com, ns500758.ns500698.ns500758.ns500758.ns500698.ns500736.ns500735.ns500735.ns500698.ns500735.ns500708.ns500698.ns500576.ns500698.ns500652.ns500652.trackreceptor.com, ns500671.ns500754.ns500731.ns500754.ns500742.ns500731.ns500704.ns500731.ns500704.ns500705.ns500704.ns500704.ns500704.ns500666.ns500666.ns500153.tenderladiesbz.com and two more.
These mail servers commonly co-occur with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 others.
Hostnames that resolve to two IP addresses:
aspmx.l.google.com resolves to 64.233.180.27 and 2607:f8b0:4004:c27::1b.
alt1.aspmx.l.google.com resolves to 108.177.123.26 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com resolves to 172.253.116.27 and 2a00:1450:400b:c02::1a.
alt3.aspmx.l.google.com resolves to 192.178.223.27 and 2a00:1450:4009:c0f::1a.
alt4.aspmx.l.google.com resolves to 172.253.157.26 and 2a00:1450:400c:c23::1b.