reachcode.net - robtex.com
reachcode.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=1789284348 | ||||||
Same first word
Similar names
Previous names
Next names
DNS History
8 records (8 active, 0 former)
●NSdns1.registrar-servers.com2026-09-08 → 2026-09-13 · 2 obs
● 2026-09-13 07:31:30
●NSdns2.registrar-servers.com2026-09-08 → 2026-09-13 · 2 obs
● 2026-09-13 07:31:30
●MXeforward1.registrar-servers.com2026-09-08 → 2026-09-13 · 2 obs
● 2026-09-13 07:31:30
●MXeforward2.registrar-servers.com2026-09-08 → 2026-09-13 · 2 obs
● 2026-09-13 07:31:30
●MXeforward3.registrar-servers.com2026-09-08 → 2026-09-13 · 2 obs
● 2026-09-13 07:31:30
●MXeforward4.registrar-servers.com2026-09-08 → 2026-09-13 · 2 obs
● 2026-09-13 07:31:30
●MXeforward5.registrar-servers.com2026-09-08 → 2026-09-13 · 2 obs
● 2026-09-13 07:31:30
●A65.108.239.1492026-09-08 → 2026-09-13 · 2 obs
● 2026-09-13 07:31:30
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| net | m.gtld-servers.net, k.gtld-servers.net, b.gtld-servers.net, f.gtld-servers.net... | - |
| reachcode.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
⚠️ Insecure (no DNSSEC)
No DS record for reachcode.net (unsigned zone)
⏱️ Timing
Total: 2895ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 65.108.239.149 |
| 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
reachcode.net has exactly one IP address — 65.108.239.149.
neuzinahuntingtours.com, www.weimaranerpedigrees.com, autoeling.com and weimaranerpedigrees.com are examples of host names that share IP numbers with reachcode.net.
Name Servers
Two name servers handle the delegation for reachcode.net: dns1.registrar-servers.com and dns2.registrar-servers.com.
The name server configuration of reachcode.net is shared with other domains, for instance magika.ai, daytradepub.com, leadmagnetstogo.com and two others.
reachcode.net partially shares its name servers with domains like gltr.us and purepeakanalytics.com.
Mail Servers
reachcode.net is handled by five mail servers: eforward1.registrar-servers.com, eforward2.registrar-servers.com, eforward3.registrar-servers.com and two others.
At least some of the mail servers used by reachcode.net are shared with other domains: cancelinstantcheckmate.net, pearl.realty, spudulike.uk and two others among them.
The mail servers eforward4.registrar-servers.com and eforward5.registrar-servers.com regularly co-occur with these mail servers.
Host names resolving to a single IP address:
The hostname eforward1.registrar-servers.com resolves to 162.255.118.51.
The hostname eforward2.registrar-servers.com resolves to 162.255.118.52.
The hostname eforward3.registrar-servers.com resolves to 162.255.118.51.
The hostname eforward4.registrar-servers.com resolves to 162.255.118.52.
The hostname eforward5.registrar-servers.com resolves to 162.255.118.51.
Three host names point to 162.255.118.51: eforward1.registrar-servers.com, eforward3.registrar-servers.com and eforward5.registrar-servers.com.
eforward2.registrar-servers.com along with eforward4.registrar-servers.com each resolve to 162.255.118.52 IP addresses.