ns2.stdregistry.com - dns.ninja
ns2.stdregistry.com
| CNAME | stdregistry.com | ||||||
| DNSSEC | ⚠️ Not signed | ||||||
| A | 134.209.82.82🇳🇱 DIGITALOCEAN134.209.80.0/20 DigitalOcean | ||||||
| NS | ns1.mysecurecloudhost.com ⭐ | ||||||
| A | 13.248.158.180🇺🇸 Amazon13.248.144.0/20 | ||||||
| PTR | a79764cc55c0ac9c0.awsglobalaccelerator.com | ||||||
| NS | ns2.mysecurecloudhost.com | ||||||
| A | 75.2.118.134🇺🇸 Amazon75.2.112.0/20 | ||||||
| PTR | abc65dd9a44b5332f.awsglobalaccelerator.com | ||||||
| NS | ns3.mysecurecloudhost.com | ||||||
| A | 76.223.26.245🇺🇸 Amazon76.223.16.0/20 | ||||||
| PTR | a79764cc55c0ac9c0.awsglobalaccelerator.com | ||||||
| NS | ns4.mysecurecloudhost.com | ||||||
| A | 99.83.147.209🇺🇸 Amazon99.83.144.0/20 | ||||||
| PTR | abc65dd9a44b5332f.awsglobalaccelerator.com | ||||||
| MX | stdregistry.com ⭐ | ||||||
| A | 134.209.82.82🇳🇱 DIGITALOCEAN134.209.80.0/20 DigitalOcean | ||||||
| TXT | v=spf1 +a +mx +ip4:192.250.229.176 include:spf.mysecurecloudhost.com ~all | ||||||
| SOA | ns1.mysecurecloudhost.comservers@mysecurecloudhost.com 2026-01-06 #0 | ||||||
stdregistry.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 134.209.82.82🇳🇱 DIGITALOCEAN134.209.80.0/20 DigitalOcean | ||||||
| NS | ns1.mysecurecloudhost.com ⭐ | ||||||
| NS | ns2.mysecurecloudhost.com | ||||||
| NS | ns3.mysecurecloudhost.com | ||||||
| NS | ns4.mysecurecloudhost.com | ||||||
| MX | stdregistry.com ⭐ | ||||||
| TXT | v=spf1 +a +mx +ip4:192.250.229.176 include:spf.mysecurecloudhost.com ~all | ||||||
| SOA | ns1.mysecurecloudhost.comservers@mysecurecloudhost.com 2026-01-06 #0 | ||||||
Previously NS for
Same first word
Similar names
DNS History
3 records (1 active, 2 former)
○NSns1.namebrightdns.com2016-05-07 → 2016-05-07 · 3 obs
○ 2016-08-09 11:08:38
○ 2026-08-07 23:24:10
○NSns2.namebrightdns.com2016-05-07 → 2016-05-07 · 3 obs
○ 2016-08-09 11:08:38
○ 2026-08-07 23:24:10
●CNAMEstdregistry.com2026-04-29 → 2026-08-07 · 2 obs
● 2026-08-07 23:24:10
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | g.gtld-servers.net, a.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net... | - |
| stdregistry.com | ns1.mysecurecloudhost.com, ns2.mysecurecloudhost.com, ns3.mysecurecloudhost.com, ns4.mysecurecloudhost.com | 4 records |
✅ Authoritative Response
Server:99.83.147.209
NS records: ns1.mysecurecloudhost.com, ns2.mysecurecloudhost.com, ns3.mysecurecloudhost.com, ns4.mysecurecloudhost.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for stdregistry.com (unsigned zone)
⏱️ Timing
Total: 237ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| CNAME | 1 | stdregistry.com |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns1.mysecurecloudhost.com, ns2.mysecurecloudhost.com, ns3.mysecurecloudhost.com...)
Analysis
IP Addresses
ns2.stdregistry.com has exactly one IP address — 134.209.82.82.
Host names like stdregistry.com are further examples that share IP numbers with ns2.stdregistry.com.
Name Servers
Four name servers handle the delegation for ns2.stdregistry.com: ns1.mysecurecloudhost.com, ns2.mysecurecloudhost.com, ns3.mysecurecloudhost.com and ns4.mysecurecloudhost.com.
The name servers of ns2.stdregistry.com overlap at least partially with those of other domains — among them grupologo.com.mx, hostingwheels.net, sitcr.com and two more.
These name servers commonly appear alongside the name servers cns7.my-hosting-panel.com and cns8.my-hosting-panel.com.
Four host names, each with one IP address: ns1.mysecurecloudhost.com has 13.248.158.180, ns2.mysecurecloudhost.com has 75.2.118.134, ns3.mysecurecloudhost.com has 76.223.26.245 and ns4.mysecurecloudhost.com has 99.83.147.209.
Mail Servers
ns2.stdregistry.com uses one mail server — stdregistry.com.
ns2.stdregistry.com uses the same mail servers as other domains, including stdregistry.com.
stdregistry.com carries a single IP number, which is 134.209.82.82.