traincontrol.com - dns.ninja
traincontrol.com
com
| 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=1782301125 | ||||||
Same first word
traincontrol.com |
Similar names
DNS History
8 records (6 active, 2 former)
●NSns23.domaincontrol.com2015-08-18 → 2026-06-24 · 2 obs
● 2026-06-24 12:01:00
●NSns24.domaincontrol.com2015-08-18 → 2026-06-24 · 2 obs
● 2026-06-24 12:01:00
●MXmx.zoho.com2026-05-09 → 2026-06-24 · 3 obs
● 2026-05-09 17:42:40
● 2026-06-24 12:01:00
○MXmx1.hostmailserver.com2015-08-18 → 2017-08-08 · 4 obs
● 2017-08-08 01:31:58
○ 2026-05-09 17:42:40
○ 2026-06-24 12:01:00
○MXmx2.hostmailserver.com2015-08-18 → 2017-08-08 · 4 obs
● 2017-08-08 01:31:58
○ 2026-05-09 17:42:40
○ 2026-06-24 12:01:00
●MXmx2.zoho.com2026-05-09 → 2026-06-24 · 3 obs
● 2026-05-09 17:42:40
● 2026-06-24 12:01:00
●MXmx3.zoho.com2026-05-09 → 2026-06-24 · 3 obs
● 2026-05-09 17:42:40
● 2026-06-24 12:01:00
●A50.57.72.482015-08-18 → 2026-06-24 · 2 obs
● 2026-06-24 12:01:00
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| traincontrol.com | ns23.domaincontrol.com, ns24.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:173.201.69.12
NS records: ns23.domaincontrol.com, ns24.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for traincontrol.com (unsigned zone)
⏱️ Timing
Total: 153ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 50.57.72.48 |
| NS | 2 | ns23.domaincontrol.com, ns24.domaincontrol.com |
| MX | 3 | mx.zoho.com (pri: 10), mx2.zoho.com (pri: 20)... |
| TXT | 1 | v=spf1 include:dc-8e814c8572._spfm.train |
| SOA | 1 | ns23.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns23.domaincontrol.com, ns23.domaincontrol.com, ns24.domaincontrol.com...)
Analysis
IP Addresses
traincontrol.com resolves to one IP address: 50.57.72.48.
Name Servers
traincontrol.com is served by two delegated name servers, ns23.domaincontrol.com and ns24.domaincontrol.com.
traincontrol.com uses the same name servers as several other domains — among them myfacebut.com, dambaugh.com, bonedryproducts.com and two more.
The DNS delegation for traincontrol.com at least partly coincides with that of other domains, sciasciagambaccini.com being one example.
Each of the two host names carries two IP addresses: ns23.domaincontrol.com points to 97.74.101.12 and 2603:5:2151::c, and ns24.domaincontrol.com points to 173.201.69.12 and 2603:5:2251::c.
Mail Servers
traincontrol.com uses three mail servers — mx2.zoho.com, mx3.zoho.com and mx.zoho.com.
traincontrol.com has at least partial mail server overlap with other domains such as mobile-synergy.com, e4india.com, andreacamillo.com and two more.
mx2.zoho.com resolves to 204.141.33.44. Notably, mx3.zoho.com and mx.zoho.com share the same IP address, 204.141.43.44.
These two host names — mx3.zoho.com and mx.zoho.com — each point to 204.141.43.44 IP addresses.