`regencyworks.com`

DNSSEC	⚠️ Not signed
A	20.49.104.19^{🇺🇸 Microsoft20.48.0.0/12}
NS	`ns1-02.azure-dns.com` ⭐
		A	2603:1061:0:700::2^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-02.azure-dns.com`
		A	13.107.236.2^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns1-02.azure-dns.com`
NS	`ns2-02.azure-dns.net`
		A	2620:1ec:8ec:700::2^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-02.azure-dns.net`
		A	150.171.21.2^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-02.azure-dns.net`
NS	`ns3-02.azure-dns.org`
		A	2a01:111:4000:700::2^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-02.azure-dns.org`
		A	204.14.183.2^{🇺🇸 Microsoft204.14.180.0/22}
			PTR	`ns3-02.azure-dns.org`
NS	`ns4-02.azure-dns.info`
		A	2620:1ec:bda:700::2^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-02.azure-dns.info`
		A	208.84.5.2^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ns4-02.azure-dns.info`
MX	`regencyworks-com.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:c902::4^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sj0pr03cu01504.inbound.protection.outlook.com`
		A	2a01:111:f403:c922::2^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-bl0pr02cu00702.inbound.protection.outlook.com`
		A	2a01:111:f403:f910::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-cy5pr03cu00300.inbound.protection.outlook.com`
		A	2a01:111:f403:f913::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-cy1pr03cu00100.inbound.protection.outlook.com`
		A	52.101.10.8^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
		A	52.101.40.6^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-cy1pr03cu00106.inbound.protection.outlook.com`
		A	52.101.41.24^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sj0pr03cu01600.inbound.protection.outlook.com`
		A	52.101.194.3^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-ch1pr04cu00103.inbound.protection.outlook.com`
TXT	`MS=ms85465361`
TXT	`MS=ms97610530`
TXT	`MS=ms47806151`
TXT	`f2lHAUQe`
TXT	`v=spf1 include:spf.protection.outlook.com -all`
TXT	`CAF9400AF0BE971768088D15200DDE6A01A53DFA9FECC5D5C997A1891C94E674`
SOA	`ns1-02.azure-dns.com`azuredns-hostmaster@microsoft.com serial=1

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

Same first word

regencyworks.com

DNS History

6 records (6 active, 0 former)

●NSns1-02.azure-dns.com2026-05-26 → 2026-07-19 · 2 obs

● 2026-05-26 13:08:26
● 2026-07-19 08:48:34

●NSns2-02.azure-dns.net2026-05-26 → 2026-07-19 · 2 obs

● 2026-05-26 13:08:26
● 2026-07-19 08:48:34

●NSns3-02.azure-dns.org2026-05-26 → 2026-07-19 · 2 obs

● 2026-05-26 13:08:26
● 2026-07-19 08:48:34

●NSns4-02.azure-dns.info2026-05-26 → 2026-07-19 · 2 obs

● 2026-05-26 13:08:26
● 2026-07-19 08:48:34

●MXregencyworks-com.mail.protection.outlook.com2026-05-26 → 2026-07-19 · 2 obs

● 2026-05-26 13:08:26
● 2026-07-19 08:48:34

●A20.49.104.192026-05-26 → 2026-07-19 · 2 obs

● 2026-05-26 13:08:26
● 2026-07-19 08:48:34

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	h.gtld-servers.net, m.gtld-servers.net, f.gtld-servers.net, j.gtld-servers.net...	-
regencyworks.com	ns1-02.azure-dns.com, ns2-02.azure-dns.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info	2 records

✅ Authoritative Response

Server:13.107.236.2

NS records: ns1-02.azure-dns.com, ns2-02.azure-dns.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for regencyworks.com (unsigned zone)

⏱️ Timing

Total: 568ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`20.49.104.19`
NS	4	`ns1-02.azure-dns.com, ns2-02.azure-dns.net...`
MX	1	`regencyworks-com.mail.protection.outlook`
TXT	6	`MS=ms85465361, MS=ms97610530...`
SOA	1	`ns1-02.azure-dns.com azuredns-hostmaster`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1-02.azure-dns.com, ns1-02.azure-dns.com)

Analysis

IP Addresses

regencyworks.com resolves to one IP address: 20.49.104.19.

itechsolutions.al, origenes.com.ar, csharpescaper.com and two other host names share IP numbers with regencyworks.com.

Name Servers

The authoritative name servers for regencyworks.com are ns1-02.azure-dns.com, ns4-02.azure-dns.info, ns2-02.azure-dns.net and ns3-02.azure-dns.org.

regencyworks.com shares at least some of its name servers with other domains, including 118.1.20.in-addr.arpa, langhoejskolen.dk, posten-norge.no and two others.

The host names ns1-02.azure-dns.com, ns4-02.azure-dns.info, ns2-02.azure-dns.net and ns3-02.azure-dns.org each resolve to two IP addresses: ns1-02.azure-dns.com resolves to 13.107.236.2 and 2603:1061:0:700::2; ns4-02.azure-dns.info resolves to 208.84.5.2 and 2620:1ec:bda:700::2; ns2-02.azure-dns.net resolves to 150.171.21.2 and 2620:1ec:8ec:700::2; ns3-02.azure-dns.org resolves to 204.14.183.2 and 2a01:111:4000:700::2.

Mail Servers

Mail for regencyworks.com is handled by a single mail server, regencyworks-com.mail.protection.outlook.com.

regencyworks-com.mail.protection.outlook.com resolves to 8 IP addresses — 52.101.10.8, 52.101.40.6, 52.101.41.24 and 5 others.

regencyworks.com - robtex.com