flukeproxy.com - dns.ninja
flukeproxy.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=1786468354 | ||||||
📈 Tranco rank: #674,606
Subdomains
api.flukeproxy.com |
Same first word
flukeproxy.com |
Similar names
DNS History
10 records (7 active, 3 former)
●NSpaloma.ns.cloudflare.com2026-02-23 → 2026-08-11 · 2 obs
● 2026-08-11 17:20:00
●NSryan.ns.cloudflare.com2026-02-23 → 2026-08-11 · 2 obs
● 2026-08-11 17:20:00
●MXrelay1.relay4.xyz2026-02-23 → 2026-08-11 · 2 obs
● 2026-08-11 17:20:00
●MXrelay2.relay4.xyz2026-02-23 → 2026-08-11 · 2 obs
● 2026-08-11 17:20:00
●MXrelay3.relay4.xyz2026-02-23 → 2026-08-11 · 2 obs
● 2026-08-11 17:20:00
●MXrelay4.relay4.xyz2026-02-23 → 2026-08-11 · 2 obs
● 2026-08-11 17:20:00
○A151.115.33.1802026-02-23 → 2026-02-23 · 4 obs
● 2026-02-23 18:55:30
○ 2026-03-06 02:22:52
○ 2026-08-11 17:20:00
○A151.115.72.342026-02-23 → 2026-02-23 · 4 obs
● 2026-02-23 18:55:30
○ 2026-03-06 02:22:52
○ 2026-08-11 17:20:00
●A193.168.139.1132026-03-17 → 2026-08-11 · 3 obs
● 2026-03-17 02:48:16
● 2026-08-11 17:20:00
○A195.225.111.2142026-03-06 → 2026-03-06 · 4 obs
● 2026-03-06 02:22:52
○ 2026-03-17 02:48:16
○ 2026-08-11 17:20:00
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | d.gtld-servers.net, i.gtld-servers.net, l.gtld-servers.net, g.gtld-servers.net... | - |
| flukeproxy.com | paloma.ns.cloudflare.com, ryan.ns.cloudflare.com | 12 records |
✅ Authoritative Response
Server:108.162.194.168
NS records: paloma.ns.cloudflare.com, ryan.ns.cloudflare.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for flukeproxy.com (unsigned zone)
⏱️ Timing
Total: 141ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 193.168.139.113 |
| NS | 2 | paloma.ns.cloudflare.com, ryan.ns.cloudflare.com |
| MX | 4 | relay1.relay4.xyz (pri: 10), relay2.relay4.xyz (pri: 20)... |
| SOA | 1 | paloma.ns.cloudflare.com dns.cloudflare. |
📌 Glue Records Collected
Total: 12
Out-of-bailiwick: 12 (paloma.ns.cloudflare.com, paloma.ns.cloudflare.com, paloma.ns.cloudflare.com...)
Analysis
Hierarchy
flukeproxy.com is a parent domain of api.flukeproxy.com.
IP Addresses
flukeproxy.com has exactly one IP address — 193.168.139.113.
Other host names, such as api.flukeproxy.com, share IP numbers with flukeproxy.com.
Name Servers
flukeproxy.com is delegated to two name servers: paloma.ns.cloudflare.com and ryan.ns.cloudflare.com.
The name server configuration of flukeproxy.com is shared with other domains, for instance ojbuy.com, comradebirb.com, easyminutes.com and two others.
flukeproxy.com shares at least some of its name servers with other domains, including exhotic.com, technicalworkshoplb.com, premiumpeoplecartlabusa.xyz and two others.
These name servers are frequently paired with the name servers evelyn.ns.cloudflare.com and roxy.ns.cloudflare.com.
Hosts with 6 IP addresses each:
paloma.ns.cloudflare.com resolves to 108.162.194.168, 162.159.38.168, 172.64.34.168 and 3 other IP addresses.
ryan.ns.cloudflare.com resolves to 108.162.195.229, 162.159.44.229, 172.64.35.229 and 3 other IP addresses.
Mail Servers
Four mail servers handle email for flukeproxy.com: relay1.relay4.xyz, relay2.relay4.xyz, relay3.relay4.xyz and relay4.relay4.xyz.
At least some of the mail servers used by flukeproxy.com are shared with other domains: relton.net, epigadget.com, ectlanding.com and two others among them.
relay1.relay4.xyz, relay2.relay4.xyz, relay3.relay4.xyz and relay4.relay4.xyz all resolve to the same single IP address: 185.159.81.205.
The following host names resolve to 185.159.81.205: relay1.relay4.xyz, relay2.relay4.xyz, relay3.relay4.xyz and relay4.relay4.xyz.