fencing.cloud - robtex.com
fencing.cloud
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=1792889129 | ||||||
Same first word
Similar names
nefginc.com |
nefginc.info |
fengcin.net |
fengcin.xyz |
cnifeng.com |
fengcin.com |
fenginc.com |
nefginc.org |
fengcin.org |
fengcin.co |
fenicng.org |
fengcin.info |
nicfeng.com |
ifengcn.com |
Previous names
Next names
fencingsnap.cloud |
fencingstory.cloud |
fencize.cloud |
fenda.cloud |
fender.cloud |
fenders.cloud |
fendler.cloud |
fendt.cloud |
fenecse.cloud |
fenestro.cloud |
DNS History
8 records (8 active, 0 former)
●NSdns1.registrar-servers.com2026-09-12 → 2026-10-25 · 2 obs
● 2026-10-25 01:14:00
●NSdns2.registrar-servers.com2026-09-12 → 2026-10-25 · 2 obs
● 2026-10-25 01:14:00
●MXeforward1.registrar-servers.com2026-09-12 → 2026-10-25 · 2 obs
● 2026-10-25 01:14:00
●MXeforward2.registrar-servers.com2026-09-12 → 2026-10-25 · 2 obs
● 2026-10-25 01:14:00
●MXeforward3.registrar-servers.com2026-09-12 → 2026-10-25 · 2 obs
● 2026-10-25 01:14:00
●MXeforward4.registrar-servers.com2026-09-12 → 2026-10-25 · 2 obs
● 2026-10-25 01:14:00
●MXeforward5.registrar-servers.com2026-09-12 → 2026-10-25 · 2 obs
● 2026-10-25 01:14:00
●A86.32.244.1932026-09-12 → 2026-10-25 · 2 obs
● 2026-10-25 01:14:00
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| cloud | ns01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.org, ns10.trs-dns.info | - |
| fencing.cloud | dns2.registrar-servers.com, dns1.registrar-servers.com | - |
✅ Authoritative Response
Server:156.154.132.200
NS records: dns2.registrar-servers.com, dns1.registrar-servers.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for fencing.cloud (unsigned zone)
⏱️ Timing
Total: 236ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 86.32.244.193 |
| NS | 2 | dns1.registrar-servers.com, dns2.registrar-servers.com |
| MX | 5 | eforward1.registrar-servers.com (pri: 10, eforward2.registrar-servers.com (pri: 10... |
| TXT | 1 | v=spf1 include:spf.efwd.registrar-server |
| SOA | 1 | dns1.registrar-servers.com hostmaster.re |
Analysis
IP Addresses
fencing.cloud resolves to one IP address: 86.32.244.193.
Other host names share IP numbers with fencing.cloud; derezic.synology.me is one such example.
Name Servers
fencing.cloud is served by two delegated name servers, dns1.registrar-servers.com and dns2.registrar-servers.com.
fencing.cloud shares the same name server setup with other domains, for instance synqide.com, mapszy.com, pennymetric.com and two other.
Each of the two host names carries two IP addresses: dns1.registrar-servers.com points to 156.154.132.200 and 2610:a1:1024::200, and dns2.registrar-servers.com points to 156.154.133.200 and 2610:a1:1025::200.
Mail Servers
Mail for fencing.cloud is handled by five mail servers, namely eforward1.registrar-servers.com, eforward2.registrar-servers.com, eforward3.registrar-servers.com and two others.
Hosts with just one IP address:
eforward1.registrar-servers.com points to the IP address 162.255.118.51.
eforward2.registrar-servers.com points to the IP address 162.255.118.52.
eforward3.registrar-servers.com points to the IP address 162.255.118.51.
eforward4.registrar-servers.com points to the IP address 162.255.118.52.
eforward5.registrar-servers.com points to the IP address 162.255.118.51.
Host names that point to 162.255.118.51 : eforward1.registrar-servers.com, eforward3.registrar-servers.com and eforward5.registrar-servers.com.
These two host names — eforward2.registrar-servers.com and eforward4.registrar-servers.com — each point to 162.255.118.52 IP addresses.