`critical-systems.com`

DNSSEC	⚠️ Not signed
NS	`ns1.netregistry.net` ⭐
		A	13.248.158.180^{🇺🇸 Amazon13.248.144.0/20}
			PTR	`a79764cc55c0ac9c0.awsglobalaccelerator.com`
NS	`ns2.netregistry.net`
		A	75.2.118.134^{🇺🇸 Amazon75.2.112.0/20}
			PTR	`abc65dd9a44b5332f.awsglobalaccelerator.com`
NS	`ns3.netregistry.net`
		A	76.223.26.245^{🇺🇸 Amazon76.223.16.0/20}
			PTR	`a79764cc55c0ac9c0.awsglobalaccelerator.com`
MX	`criticalsystems-com02b.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:cc31::^{🇦🇺 Microsoft2a01:111:f000::/36}
			PTR	`mail-sy2pr01cu00300.inbound.protection.outlook.com`
		A	2a01:111:f403:cc31::1^{🇦🇺 Microsoft2a01:111:f000::/36}
			PTR	`mail-sy8pr01cu00101.inbound.protection.outlook.com`
		A	2a01:111:f403:cc31::2^{🇦🇺 Microsoft2a01:111:f000::/36}
			PTR	`mail-sy5pr01cu00902.inbound.protection.outlook.com`
		A	2a01:111:f403:cc31::3^{🇦🇺 Microsoft2a01:111:f000::/36}
			PTR	`mail-sy2pr01cu00503.inbound.protection.outlook.com`
		A	52.101.149.0^{🇦🇺 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sy2pr01cu00300.inbound.protection.outlook.com`
		A	52.101.149.1^{🇦🇺 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sy8pr01cu00101.inbound.protection.outlook.com`
		A	52.101.149.9^{🇦🇺 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sy2pr01cu00501.inbound.protection.outlook.com`
		A	52.101.151.0^{🇦🇺 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-meupr01cu00200.inbound.protection.outlook.com`
TXT	`MS=ms59128095`
TXT	`v=spf1 include:spf.protection.outlook.com -all`
TXT	`openai-domain-verification=dv-oPON3Ew05YXLUoONtHhB7KX8`
SOA	`ns1.netregistry.net`dmain@netregistry.net 2026-02-25 #3

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

Same first word

critical-systems.de

critical-systems.net

critical-systems.com

critical-systems.com.sg

DNS History

5 records (4 active, 1 former)

●NSns1.netregistry.net2015-06-05 → 2026-04-12 · 2 obs

● 2015-06-05 05:41:18
● 2026-04-12 00:41:38

●NSns2.netregistry.net2015-06-05 → 2026-04-12 · 2 obs

● 2015-06-05 05:41:18
● 2026-04-12 00:41:38

●NSns3.netregistry.net2015-06-05 → 2026-04-12 · 2 obs

● 2015-06-05 05:41:18
● 2026-04-12 00:41:38

●MXcriticalsystems-com02b.mail.protection.outlook.com2026-04-12 → 2026-04-12 · 2 obs

○ 2017-06-05 22:26:30
● 2026-04-12 00:41:38

○MXremote.critical-systems.com2015-06-05 → 2017-06-05 · 3 obs

● 2015-06-05 05:41:18
● 2017-06-05 22:26:30
○ 2026-04-12 00:41:38

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
critical-systems.com	ns3.netregistry.net, ns1.netregistry.net, ns2.netregistry.net	-

✅ Authoritative Response

Server:76.223.26.245

NS records: ns3.netregistry.net, ns1.netregistry.net, ns2.netregistry.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for critical-systems.com (unsigned zone)

⏱️ Timing

Total: 211ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	3	`ns3.netregistry.net, ns2.netregistry.net...`
MX	1	`criticalsystems-com02b.mail.protection.o`
TXT	3	`MS=ms59128095, v=spf1 include:spf.protection.outlook.co...`
SOA	1	`ns1.netregistry.net dmain.netregistry.ne`