`radioregistry.com`

DNSSEC	⚠️ Not signed
A	2607:5300:203:90ae::^{🇨🇦 OVH2607:5300::/32 Hosting route}
		PTR	`caprm100.fastcpanelserver.com`
A	51.222.248.174^{🇨🇦 OVH51.222.0.0/16 Hosting route}
NS	`ns1.radioregistry.com` ⭐
		A	51.222.248.174^{🇨🇦 OVH51.222.0.0/16 Hosting route}
			PTR	`caprm100.fastcpanelserver.com`
NS	`ns2.radioregistry.com`
		A	51.75.64.141^{🇩🇪 OVH51.75.0.0/16}
			PTR	`secns20.fastcpanelserver.com`
MX	`radioregistry.com` ⭐
		A	2607:5300:203:90ae::^{🇨🇦 OVH2607:5300::/32 Hosting route}
			PTR	`caprm100.fastcpanelserver.com`
		A	51.222.248.174^{🇨🇦 OVH51.222.0.0/16 Hosting route}
			PTR	`caprm100.fastcpanelserver.com`
TXT	`google-site-verification=Jw0EFMUg3HYoCA9WFmIzndde0YOtyBHWjmQoecxa7fk`
TXT	`v=spf1 ip4:51.222.248.174 include:spf.hostmantis.com +a +mx ~all`
SOA	`ns1.radioregistry.com`hostmaster@radioregistry.com 2026-07-29 #2

`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.net`nstld@verisign-grs.com serial=1785317407

MX for

radioregistry.com

Same first word

radioregistry.com

Similar names

rotarydergisi.com.tr

DNS History

7 records (5 active, 2 former)

○NSdns1.cscdns.net2015-07-17 → 2016-07-10 · 4 obs

● 2015-07-17 20:43:54
● 2016-07-10 05:29:20
○ 2017-05-23 07:21:48
○ 2026-07-29 09:36:26

○NSdns2.cscdns.net2015-07-17 → 2016-07-10 · 4 obs

● 2015-07-17 20:43:54
● 2016-07-10 05:29:20
○ 2017-05-23 07:21:48
○ 2026-07-29 09:36:26

●NSns1.radioregistry.com2026-05-12 → 2026-07-29 · 3 obs

○ 2017-05-23 07:21:48
● 2026-05-12 06:01:22
● 2026-07-29 09:36:26

●NSns2.radioregistry.com2026-05-12 → 2026-07-29 · 3 obs

○ 2017-05-23 07:21:48
● 2026-05-12 06:01:22
● 2026-07-29 09:36:26

●MXradioregistry.com2026-05-12 → 2026-07-29 · 2 obs

● 2026-05-12 06:01:22
● 2026-07-29 09:36:26

●A2607:5300:203:90ae::2026-05-12 → 2026-07-29 · 2 obs

● 2026-05-12 06:01:22
● 2026-07-29 09:36:26

●A51.222.248.1742026-05-12 → 2026-07-29 · 2 obs

● 2026-05-12 06:01:22
● 2026-07-29 09:36:26

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	j.gtld-servers.net, h.gtld-servers.net, k.gtld-servers.net, a.gtld-servers.net...	-
radioregistry.com	ns1.radioregistry.com, ns2.radioregistry.com	2 records

✅ Authoritative Response

Server:51.222.248.174

NS records: ns1.radioregistry.com, ns2.radioregistry.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for radioregistry.com (unsigned zone)

⏱️ Timing

Total: 243ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`51.222.248.174`
AAAA	1	`2607:5300:203:90ae::`
NS	2	`ns1.radioregistry.com, ns2.radioregistry.com`
MX	1	`radioregistry.com (pri: 0)`
TXT	2	`google-site-verification=Jw0EFMUg3HYoCA9, v=spf1 ip4:51.222.248.174 include:spf.ho`
SOA	1	`ns1.radioregistry.com hostmaster.radiore`

📌 Glue Records Collected

Total: 2

In-bailiwick: 2 (ns1.radioregistry.com, ns2.radioregistry.com)

Analysis

Mail Server Role

radioregistry.com serves as a mail server for radioregistry.com.

IP Addresses

radioregistry.com directs to two IP numbers, 51.222.248.174 and 2607:5300:203:90ae::

wenallboxers.com, ardiraq.com, telecareworld.com plus two other host names have IP numbers in common with radioregistry.com.

Name Servers

The NS records for radioregistry.com delegate to ns1.radioregistry.com and ns2.radioregistry.com.

ns1.radioregistry.com and ns2.radioregistry.com each resolve to one IP number: ns1.radioregistry.com points to 51.222.248.174 and ns2.radioregistry.com points to 51.75.64.141.

Mail Servers

radioregistry.com uses exactly one mail server, which is radioregistry.com.

radioregistry.com points to two IP addresses: 51.222.248.174 and 2607:5300:203:90ae::.

radioregistry.com - robtex.com