regiment.dev - robtex.com
regiment.dev
dev
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns-tld1.charlestonroadregistry.com ⭐ | ||||||
| NS | ns-tld2.charlestonroadregistry.com | ||||||
| NS | ns-tld3.charlestonroadregistry.com | ||||||
| NS | ns-tld4.charlestonroadregistry.com | ||||||
| NS | ns-tld5.charlestonroadregistry.com | ||||||
| SOA | ns-tld1.charlestonroadregistry.comcloud-dns-hostmaster@google.com serial=1 | ||||||
Same first word
Similar names
Previous names
Next names
DNS History
8 records (8 active, 0 former)
●NSns-cloud-b1.googledomains.com2026-09-24 → 2026-11-22 · 2 obs
● 2026-11-22 01:18:58
●NSns-cloud-b2.googledomains.com2026-09-24 → 2026-11-22 · 2 obs
● 2026-11-22 01:18:58
●NSns-cloud-b3.googledomains.com2026-09-24 → 2026-11-22 · 2 obs
● 2026-11-22 01:18:58
●NSns-cloud-b4.googledomains.com2026-09-24 → 2026-11-22 · 2 obs
● 2026-11-22 01:18:58
●A34.111.179.2082026-09-24 → 2026-11-22 · 2 obs
● 2026-11-22 01:18:58
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| dev | ns-tld1.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com... | - |
| regiment.dev | ns-cloud-b4.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b1.googledomains.com | - |
✅ Authoritative Response
Server:216.239.38.107
NS records: ns-cloud-b4.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b1.googledomains.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for regiment.dev (unsigned zone)
⏱️ Timing
Total: 639ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 34.111.179.208 |
| NS | 4 | ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com... |
| MX | 3 | mx3.zoho.com (pri: 50), mx2.zoho.com (pri: 20)... |
| TXT | 2 | replit-verify=00d43cae-9ab9-49f8-a897-68, v=spf1 include:zohomail.com ~all |
| SOA | 1 | ns-cloud-b1.googledomains.com cloud-dns- |
Analysis
IP Addresses
regiment.dev points to a single IP number: 34.111.179.208.
Additional host names — sarochapakeenuya.com, vitalityplususa.com, ribeiroschmidt.com.br and two others — share IP numbers with regiment.dev.
Name Servers
regiment.dev has four authoritative name servers: ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com and ns-cloud-b4.googledomains.com.
The name servers of regiment.dev overlap at least partially with those of other domains — among them emilyazzano.com, insurancegrowthconference.com, webuyyourcouch.com and two more.
Each of the four hosts ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com and ns-cloud-b4.googledomains.com has two IP addresses. ns-cloud-b1.googledomains.com points to 216.239.32.107 and 2001:4860:4802:32::6b. ns-cloud-b2.googledomains.com points to 216.239.34.107 and 2001:4860:4802:34::6b. ns-cloud-b3.googledomains.com points to 216.239.36.107 and 2001:4860:4802:36::6b. ns-cloud-b4.googledomains.com points to 216.239.38.107 and 2001:4860:4802:38::6b.
Mail Servers
Mail for regiment.dev is routed through three mail servers — mx2.zoho.com, mx3.zoho.com and mx.zoho.com.
regiment.dev shares mail servers — at least in part — with other domains, including fminstitute.org, gostudybug.com, onitsuga.com and two others.
All three hosts carry a single IP: mx2.zoho.com directs to 136.143.191.44, while mx3.zoho.com and mx.zoho.com both direct to 136.143.183.44.
mx3.zoho.com and mx.zoho.com each have 136.143.183.44 IP addresses.