leadcode.build - robtex.com
leadcode.build
build
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns0.centralnic.net ⭐ | ||||||
| NS | a.nic.build | ||||||
| NS | b.nic.build | ||||||
| NS | c.nic.build | ||||||
| NS | d.nic.build | ||||||
| SOA | ns0.centralnic.nethostmaster@centralnic.net serial=1788120788 | ||||||
Same first word
Similar names
Previous names
Next names
DNS History
8 records (8 active, 0 former)
●NSpdns1.registrar-servers.com2026-08-26 → 2026-08-30 · 2 obs
● 2026-08-30 20:31:10
●NSpdns2.registrar-servers.com2026-08-26 → 2026-08-30 · 2 obs
● 2026-08-30 20:31:10
●MXeforward1.registrar-servers.com2026-08-26 → 2026-08-30 · 2 obs
● 2026-08-30 20:31:10
●MXeforward2.registrar-servers.com2026-08-26 → 2026-08-30 · 2 obs
● 2026-08-30 20:31:10
●MXeforward3.registrar-servers.com2026-08-26 → 2026-08-30 · 2 obs
● 2026-08-30 20:31:10
●MXeforward4.registrar-servers.com2026-08-26 → 2026-08-30 · 2 obs
● 2026-08-30 20:31:10
●MXeforward5.registrar-servers.com2026-08-26 → 2026-08-30 · 2 obs
● 2026-08-30 20:31:10
●A199.36.158.1002026-08-26 → 2026-08-30 · 2 obs
● 2026-08-30 20:31:10
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| build | c.nic.build, b.nic.build, a.nic.build, d.nic.build | 8 records |
| leadcode.build | pdns1.registrar-servers.com, pdns2.registrar-servers.com | - |
✅ Authoritative Response
Server:156.154.133.100
NS records: pdns1.registrar-servers.com, pdns2.registrar-servers.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for leadcode.build (unsigned zone)
⏱️ Timing
Total: 631ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 199.36.158.100 |
| NS | 2 | pdns1.registrar-servers.com, pdns2.registrar-servers.com |
| MX | 5 | eforward1.registrar-servers.com (pri: 10, eforward2.registrar-servers.com (pri: 10... |
| TXT | 3 | hosting-site=leadcode-ai, v=spf1 include:spf.efwd.registrar-server... |
| SOA | 1 | pdns1.registrar-servers.com hostmaster.r |
📌 Glue Records Collected
Total: 8
In-bailiwick: 8 (a.nic.build, b.nic.build, c.nic.build...)
Analysis
IP Addresses
leadcode.build resolves to just one IP address, 199.36.158.100.
Two other host names, along with gigto.in, jffgjgmcmb.web.app and fb-restriction-case-ac669.web.app, also share IP numbers with leadcode.build.
Name Servers
The NS records for leadcode.build delegate to pdns1.registrar-servers.com and pdns2.registrar-servers.com.
leadcode.build shares its NS records with other domains, for example enracine-fr.com, axcim.com, queer.sh and two others.
leadcode.build and other domains like cgm-cpa.com share at least a portion of their name servers.
pdns1.registrar-servers.com resolves to 156.154.132.100 and 2610:a1:1024::100. Likewise, pdns2.registrar-servers.com resolves to 156.154.133.100 and 2610:a1:1025::100 — two IP addresses apiece.
Mail Servers
Five mail servers handle leadcode.build: eforward1.registrar-servers.com, eforward2.registrar-servers.com, eforward3.registrar-servers.com and two others.
There is at least a partial MX overlap between leadcode.build and other domains, including mxc1s.com, jobwhiz.org, jleeillustration.com and two others.
These mail servers are routinely seen in conjunction with the mail servers eforward5.registrar-servers.com and eforward4.registrar-servers.com.
Host names that point to one IP address:
eforward1.registrar-servers.com resolves to the IP address 162.255.118.51.
eforward2.registrar-servers.com resolves to the IP address 162.255.118.52.
eforward3.registrar-servers.com resolves to the IP address 162.255.118.51.
eforward4.registrar-servers.com resolves to the IP address 162.255.118.52.
eforward5.registrar-servers.com resolves to the IP address 162.255.118.51.
Each of eforward1.registrar-servers.com, eforward3.registrar-servers.com and eforward5.registrar-servers.com resolves to 162.255.118.51.
eforward2.registrar-servers.com and eforward4.registrar-servers.com each have 162.255.118.52 IP addresses.