readysteadygo.co - robtex.com
readysteadygo.co
co
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns0.centralnic.net ⭐ | ||||||
| NS | a.registrydns.co | ||||||
| NS | b.registrydns.co | ||||||
| NS | c.registrydns.co | ||||||
| NS | d.registrydns.co | ||||||
| SOA | ns0.centralnic.nethostmaster@centralnic.net serial=1759709592 | ||||||
Same first word
readysteadygo.co |
DNS History
14 records (5 active, 9 former)
●NSdns1.registrar-servers.com2026-02-26 → 2026-07-19 · 3 obs
● 2026-02-26 07:02:24
● 2026-07-19 03:38:54
●NSdns2.registrar-servers.com2026-02-26 → 2026-07-19 · 3 obs
● 2026-02-26 07:02:24
● 2026-07-19 03:38:54
○NSns39.domaincontrol.com2015-08-22 → 2015-12-08 · 4 obs
● 2015-12-08 08:45:02
○ 2016-03-12 23:47:02
○ 2026-07-19 03:38:54
○NSns40.domaincontrol.com2015-08-22 → 2015-12-08 · 4 obs
● 2015-12-08 08:45:02
○ 2016-03-12 23:47:02
○ 2026-07-19 03:38:54
○MXmailstore1.secureserver.net2015-08-22 → 2015-12-08 · 4 obs
● 2015-12-08 08:45:02
○ 2016-03-12 23:47:02
○ 2026-07-19 03:38:54
●MXmx1.privateemail.com2026-02-26 → 2026-07-19 · 3 obs
● 2026-02-26 07:02:24
● 2026-07-19 03:38:54
●MXmx2.privateemail.com2026-02-26 → 2026-07-19 · 3 obs
● 2026-02-26 07:02:24
● 2026-07-19 03:38:54
○MXsmtp.secureserver.net2015-08-22 → 2015-12-08 · 4 obs
● 2015-12-08 08:45:02
○ 2016-03-12 23:47:02
○ 2026-07-19 03:38:54
●A162.255.119.1792026-02-26 → 2026-07-19 · 3 obs
● 2026-02-26 07:02:24
● 2026-07-19 03:38:54
○A198.71.232.32015-08-22 → 2015-12-08 · 4 obs
● 2015-12-08 08:45:02
○ 2016-03-12 23:47:02
○ 2026-07-19 03:38:54
○A52.73.190.1332016-03-12 → 2016-03-12 · 4 obs
● 2016-03-12 23:47:02
○ 2016-07-13 19:45:28
○ 2026-07-19 03:38:54
○A72.167.191.692015-08-22 → 2015-08-22 · 3 obs
○ 2017-07-01 02:24:36
○ 2026-07-19 03:38:54
○CNAMEpr-co-suspensions.neuweb.biz2016-03-12 → 2016-03-12 · 3 obs
○ 2016-07-13 19:45:28
○ 2026-07-19 03:38:54
○CNAMEws-pr-web-suspensionpages-1962938698.us-east-1.elb.amazonaws.com2016-03-12 → 2016-03-12 · 3 obs
○ 2016-07-13 19:45:28
○ 2026-07-19 03:38:54
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| co | a.registrydns.co, b.registrydns.co, c.registrydns.co, d.registrydns.co | - |
| readysteadygo.co | 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 readysteadygo.co (unsigned zone)
⏱️ Timing
Total: 307ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 162.255.119.179 |
| NS | 2 | dns1.registrar-servers.com, dns2.registrar-servers.com |
| MX | 2 | mx1.privateemail.com (pri: 10), mx2.privateemail.com (pri: 10) |
| TXT | 1 | v=spf1 include:spf.privateemail.com ~all |
| SOA | 1 | dns1.registrar-servers.com hostmaster.re |
Analysis
IP Addresses
readysteadygo.co points to a single IP number: 162.255.119.179.
Additional host names — moops.us, pimiq.com, dabooms.com and two others — share IP numbers with readysteadygo.co.
Name Servers
The NS records for readysteadygo.co delegate to dns1.registrar-servers.com and dns2.registrar-servers.com.
readysteadygo.co shares its name server setup with other domains, including prologmultimedia.com, godsplanforman.com, sbirro.com and two others.
readysteadygo.co has overlapping name servers with several other domains — among them mormonhealthcoach.com, bowersusa.com, bebemehr.com and techyield.com.
The name servers dns3.registrar-servers.com, dns4.registrar-servers.com and dns5.registrar-servers.com are commonly seen alongside these name servers.
dns1.registrar-servers.com resolves to 156.154.132.200 and 2610:a1:1024::200. Likewise, dns2.registrar-servers.com resolves to 156.154.133.200 and 2610:a1:1025::200 — two IP addresses apiece.
Mail Servers
readysteadygo.co has two mail servers: mx1.privateemail.com and mx2.privateemail.com.
readysteadygo.co shares the same mail server setup as other domains, including balonso.com, tsanmiguel.cl, industry4g.com and two others.
readysteadygo.co has mail servers in common with other domains — a7la7p.com being one example.
Both mx1.privateemail.com and mx2.privateemail.com have a single IP address each — mx1.privateemail.com resolves to 162.255.118.7 while mx2.privateemail.com resolves to 162.255.118.8.