registry-to.com - robtex.com
registry-to.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | ::1 | ||||||
| A | 127.0.0.1 | ||||||
| NS | ns1.register.to ⚠️ Not in zone NS records | ||||||
| A | 2a06:fb00:1::1:155🇧🇬 CLOUDNSNET2a06:fb00:1::/48 ClouDNS | ||||||
| PTR | ns1.mjrcc.net | ||||||
| A | 185.136.96.155🇺🇸 CLOUDNSNET185.136.96.0/24 Cloud DNS Ltd | ||||||
| PTR | ns1.mjrcc.net | ||||||
| NS | ns2.register.to ⚠️ Not in zone NS records | ||||||
| A | 2a06:fb00:1::2:155🇧🇬 CLOUDNSNET2a06:fb00:1::/48 ClouDNS | ||||||
| PTR | ns2.mjrcc.net | ||||||
| A | 185.136.97.155CLOUDNSNET185.136.97.0/24 Cloud DNS Ltd | ||||||
| PTR | ns2.mjrcc.net | ||||||
| NS | ns3.register.to ⚠️ Not in zone NS records | ||||||
| A | 2a06:fb00:1::3:155🇧🇬 CLOUDNSNET2a06:fb00:1::/48 ClouDNS | ||||||
| PTR | ns3.mjrcc.net | ||||||
| A | 185.136.98.155🇺🇸 CLOUDNSNET185.136.98.0/24 Cloud DNS Ltd | ||||||
| PTR | ns3.mjrcc.net | ||||||
| NS | ns4.register.to ⚠️ Not in zone NS records | ||||||
| A | 2a06:fb00:1::4:155🇧🇬 CLOUDNSNET2a06:fb00:1::/48 ClouDNS | ||||||
| PTR | ns4.mjrcc.net | ||||||
| A | 185.136.99.155CLOUDNSNET185.136.99.0/24 Cloud DNS Ltd | ||||||
| PTR | ns4.mjrcc.net | ||||||
| MX | localhost ⭐ | ||||||
| TXT | expired | ||||||
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=1777003561 | ||||||
Same first word
registry-to.com |
Similar names
DNS History
11 records (7 active, 4 former)
○NSns1.afternic.com2015-06-10 → 2017-02-16 · 4 obs
● 2017-02-16 06:46:26
○ 2019-01-18 07:36:40
○ 2026-04-24 04:27:36
○NSns1.namefind.com2019-01-18 → 2019-01-18 · 4 obs
● 2019-01-18 07:36:40
○ 2026-02-14 22:43:42
○ 2026-04-24 04:27:36
●NSns1.register.to2026-02-14 → 2026-04-24 · 3 obs
● 2026-02-14 22:43:42
● 2026-04-24 04:27:36
○NSns2.namefind.com2019-01-18 → 2019-01-18 · 4 obs
● 2019-01-18 07:36:40
○ 2026-02-14 22:43:42
○ 2026-04-24 04:27:36
●NSns2.register.to2026-02-14 → 2026-04-24 · 3 obs
● 2026-02-14 22:43:42
● 2026-04-24 04:27:36
●NSns3.register.to2026-02-14 → 2026-04-24 · 3 obs
● 2026-02-14 22:43:42
● 2026-04-24 04:27:36
●NSns4.register.to2026-02-14 → 2026-04-24 · 3 obs
● 2026-02-14 22:43:42
● 2026-04-24 04:27:36
●MXlocalhost2026-02-14 → 2026-04-24 · 2 obs
● 2026-04-24 04:27:36
●A::12026-02-14 → 2026-04-24 · 3 obs
● 2026-02-14 22:43:42
● 2026-04-24 04:27:36
●A127.0.0.12026-02-14 → 2026-04-24 · 3 obs
● 2026-02-14 22:43:42
● 2026-04-24 04:27:36
○A184.168.221.1042015-06-10 → 2019-01-18 · 4 obs
● 2019-01-18 07:36:40
○ 2026-02-14 22:43:42
○ 2026-04-24 04:27:36
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net... | - |
| registry-to.com | ns1.register.to, ns2.register.to, ns3.register.to, ns4.register.to | - |
✅ Authoritative Response
Server:185.136.98.155
NS records: ns1.register.to, ns2.register.to, ns3.register.to, ns4.register.to
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for registry-to.com (unsigned zone)
⏱️ Timing
Total: 546ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 127.0.0.1 |
| AAAA | 1 | ::1 |
| MX | 1 | localhost (pri: 0) |
| TXT | 1 | expired |
Analysis
IP Addresses
registry-to.com resolves to two IP numbers: ::1 and 127.0.0.1.
Other host names, for instance 254.244.38.static.quadranet.com, 223.60.188.dynamic.wline.res.cust.swisscom.ch, mail.milanpass.it, www.sakbark.com and 1918056059.localhost share IP numbers with registry-to.com.
Name Servers
registry-to.com's delegation is handled by four name servers: ns1.register.to, ns2.register.to, ns3.register.to and ns4.register.to.
registry-to.com partially shares name servers with other domains; examples include pizda.to, toregistry.com, registertoronto.com, registryto.com and torontoregister.com.
These name servers are often used with the name servers ns71.domaincontrol.com and ns72.domaincontrol.com.
Host names with two IPs:
ns1.register.to points to 2a06:fb00:1::1:155 and 185.136.96.155
ns2.register.to points to 2a06:fb00:1::2:155 and 185.136.97.155
ns3.register.to points to 2a06:fb00:1::3:155 and 185.136.98.155
ns4.register.to points to 2a06:fb00:1::4:155 and 185.136.99.155
Mail Servers
registry-to.com is handled by a single mail server, localhost.
registry-to.com has the same mail server setup as other domains, including partycheckin.de, cleverino.de, 6075.de, nettspace.de and kalju.fi.