`royalsecurity-da.com`

DNSSEC	⚠️ Not signed
A	185.45.67.192^{🇧🇬 SUPERHOSTING_AS185.45.66.0/23 SUPERHOSTINGBG ROUTE OBJECT}
		PTR	`host-185-45-67-192.superhosting.bg`
NS	`royalsecurity-da.com` ⭐
		A	185.45.67.192^{🇧🇬 SUPERHOSTING_AS185.45.66.0/23 SUPERHOSTINGBG ROUTE OBJECT}
			PTR	`host-185-45-67-192.superhosting.bg`
NS	`ns1.royalsecurity-da.com`
		A	84.38.243.193^{🇧🇬 BGLAN-AS84.38.243.0/24}
			PTR	`ns1.impuls-ko.com`
NS	`ns2.royalsecurity-da.com`
		A	92.247.91.245^{🇧🇬 A1BG92.247.0.0/16 A1 BG Net}
			PTR	`mail.telemarkarea.org`
NS	`ns3.royalsecurity-da.com` ⚠️ Not in parent delegation
		A	92.247.91.243^{🇧🇬 A1BG92.247.0.0/16 A1 BG Net}
			PTR	`ns2.impuls-ko.com`
MX	`mx1.royalsecurity-da.com` ⭐
		A	84.38.243.193^{🇧🇬 BGLAN-AS84.38.243.0/24}
			PTR	`ns1.impuls-ko.com`
TXT	`v=spf1 +a +mx a:mail.royalsecurity-da.com ip4:92.247.91.245 ip4:84.38.243.193...`
SOA	`royalsecurity-da.com`hostmaster@royalsecurity-da.com 2025-07-05 #0

`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=1776040182

NS for

royalsecurity-da.com

Subdomains

ns1.royalsecurity-da.com

mail.royalsecurity-da.com

mx1.royalsecurity-da.com

ns2.royalsecurity-da.com

mx2.royalsecurity-da.com

ns3.royalsecurity-da.com

Same first word

royalsecurity-da.com

DNS History

10 records (6 active, 4 former)

●NSns1.royalsecurity-da.com2015-07-04 → 2026-04-13 · 5 obs

● 2015-07-04 21:23:08
● 2015-12-06 04:45:02
○ 2016-03-16 12:52:06
● 2016-07-16 19:32:50
● 2026-04-13 00:49:42

●NSns2.royalsecurity-da.com2015-07-04 → 2026-04-13 · 7 obs

● 2015-07-04 21:23:08
○ 2015-12-06 04:45:02
● 2016-03-16 12:52:06
○ 2016-07-16 19:32:50
○ 2017-02-19 14:15:04
● 2020-01-01 05:50:48
● 2026-04-13 00:49:42

●NSns3.royalsecurity-da.com2026-02-26 → 2026-04-13 · 3 obs

○ 2020-01-01 05:50:48
● 2026-02-26 01:11:18
● 2026-04-13 00:49:42

●NSroyalsecurity-da.com2026-02-26 → 2026-04-13 · 3 obs

○ 2020-01-01 05:50:48
● 2026-02-26 01:11:18
● 2026-04-13 00:49:42

○MXmail.royalsecurity-da.com2020-01-01 → 2020-01-01 · 4 obs

○ 2017-02-19 14:15:04
● 2020-01-01 05:50:48
○ 2026-02-26 01:11:18
○ 2026-04-13 00:49:42

○MXmail1.royalsecurity-da.com2015-07-04 → 2017-02-19 · 4 obs

● 2015-07-04 21:23:08
● 2017-02-19 14:15:04
○ 2020-01-01 05:50:48
○ 2026-04-13 00:49:42

○MXmail2.royalsecurity-da.com2015-07-04 → 2017-02-19 · 4 obs

● 2015-07-04 21:23:08
● 2017-02-19 14:15:04
○ 2020-01-01 05:50:48
○ 2026-04-13 00:49:42

●MXmx1.royalsecurity-da.com2026-02-26 → 2026-04-13 · 3 obs

○ 2020-01-01 05:50:48
● 2026-02-26 01:11:18
● 2026-04-13 00:49:42

●A185.45.67.1922026-02-26 → 2026-04-13 · 3 obs

○ 2020-01-01 05:50:48
● 2026-02-26 01:11:18
● 2026-04-13 00:49:42

○A95.111.10.1872015-07-04 → 2020-01-01 · 4 obs

● 2015-07-04 21:23:08
● 2020-01-01 05:50:48
○ 2026-02-26 01:11:18
○ 2026-04-13 00:49:42

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
royalsecurity-da.com	ns1.royalsecurity-da.com, ns2.royalsecurity-da.com	2 records

✅ Authoritative Response

Server:84.38.243.193

NS records: ns1.royalsecurity-da.com, ns2.royalsecurity-da.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for royalsecurity-da.com (unsigned zone)

⏱️ Timing

Total: 568ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`185.45.67.192`
NS	3	`ns3.royalsecurity-da.com, ns2.royalsecurity-da.com...`
MX	1	`mx1.royalsecurity-da.com (pri: 10)`
TXT	1	`v=spf1 +a +mx a:mail.royalsecurity-da.co`
SOA	1	`royalsecurity-da.com hostmaster.royalsec`

📌 Glue Records Collected

Total: 2

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

Analysis

Hierarchy

royalsecurity-da.com is a parent of ns1.royalsecurity-da.com, mail.royalsecurity-da.com, mx1.royalsecurity-da.com, ns2.royalsecurity-da.com, mx2.royalsecurity-da.com and a few other host names.

Name Server Role

royalsecurity-da.com serves as a name server for royalsecurity-da.com.

ns1.royalsecurity-da.com, ns2.royalsecurity-da.com and ns3.royalsecurity-da.com are commonly used as name servers together with royalsecurity-da.com.

IP Addresses

royalsecurity-da.com points to IP number: 185.45.67.192.

Other host names such as mail.mitika.bg, niagarabg.com, mail.avtozona.net, imperial-travel.eu and mail.intex.bg share IPs with royalsecurity-da.com.

Name Servers

The zone for royalsecurity-da.com is delegated to four name servers: royalsecurity-da.com, ns1.royalsecurity-da.com, ns2.royalsecurity-da.com and ns3.royalsecurity-da.com.

Host names with one IP number:

royalsecurity-da.com points to 185.45.67.192.

ns1.royalsecurity-da.com points to 84.38.243.193.

ns2.royalsecurity-da.com points to 92.247.91.245.

ns3.royalsecurity-da.com points to 92.247.91.243.

Mail Servers

royalsecurity-da.com is handled by a single mail server, mx1.royalsecurity-da.com.

mx1.royalsecurity-da.com points to a single IP: 84.38.243.193.

royalsecurity-da.com - robtex.com