message-cms.dev - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`message-cms.dev`

DNSSEC	⚠️ Not signed
NS	`ns1-03.azure-dns.com` ⭐
		A	2603:1061:0:700::3^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-03.azure-dns.com`
		A	13.107.236.3^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns1-03.azure-dns.com`
NS	`ns2-03.azure-dns.net`
		A	2620:1ec:8ec:700::3^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-03.azure-dns.net`
		A	150.171.21.3^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-03.azure-dns.net`
NS	`ns3-03.azure-dns.org`
		A	2a01:111:4000:700::3^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-03.azure-dns.org`
		A	204.14.183.3^{🇺🇸 Microsoft204.14.180.0/22}
			PTR	`ns3-03.azure-dns.org`
NS	`ns4-03.azure-dns.info`
		A	2620:1ec:bda:700::3^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-03.azure-dns.info`
		A	208.84.5.3^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ns4-03.azure-dns.info`
SOA	`ns1-03.azure-dns.com`azuredns-hostmaster@microsoft.com serial=1

`dev`

	DNSSEC	🔒 Signed (DS record present)
	NS	`ns-tld1.charlestonroadregistry.com` ⭐
	NS	`ns-tld2.charlestonroadregistry.com`
	NS	`ns-tld3.charlestonroadregistry.com`
	NS	`ns-tld4.charlestonroadregistry.com`
	NS	`ns-tld5.charlestonroadregistry.com`
	SOA	`ns-tld1.charlestonroadregistry.com`cloud-dns-hostmaster@google.com serial=1

🔒 HSTS Preload (+subdomains)

Same first word

message-cms.com

message-cms.dev

Previous names

mesk.dev

meskill.dev

mesmerize.dev

mesmerus.dev

mesmin.dev

mesmoustaches.dev

mesner.dev

mesnil.dev

mesny.dev

mesoglea.dev

mesolab.dev

mesonnaise.dev

mesopic.dev

mespi.dev

mesquita.dev

mess-hardware.dev

messa.dev

messabout.dev

message-bus.dev

message.dev

Next names

DNS History

4 records (4 active, 0 former)

●NSns1-03.azure-dns.com2026-08-29 → 2026-09-01 · 2 obs

● 2026-08-29 06:44:56
● 2026-09-01 09:17:00

●NSns2-03.azure-dns.net2026-08-29 → 2026-09-01 · 2 obs

● 2026-08-29 06:44:56
● 2026-09-01 09:17:00

●NSns3-03.azure-dns.org2026-08-29 → 2026-09-01 · 2 obs

● 2026-08-29 06:44:56
● 2026-09-01 09:17:00

●NSns4-03.azure-dns.info2026-08-29 → 2026-09-01 · 2 obs

● 2026-08-29 06:44:56
● 2026-09-01 09:17:00

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
dev	ns-tld1.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com...	-
message-cms.dev	ns3-03.azure-dns.org, ns1-03.azure-dns.com, ns2-03.azure-dns.net, ns4-03.azure-dns.info	-

✅ Authoritative Response

Server:204.14.183.3

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for message-cms.dev (unsigned zone)

⏱️ Timing

Total: 981ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns1-03.azure-dns.com, ns2-03.azure-dns.net...`
SOA	1	`ns1-03.azure-dns.com azuredns-hostmaster`

Analysis

Name Servers

The NS records for message-cms.dev point to four name servers: ns1-03.azure-dns.com, ns4-03.azure-dns.info, ns2-03.azure-dns.net and ns3-03.azure-dns.org.

message-cms.dev partially shares its NS delegation with several other domains, including microsoftstart.at, bcm.co.ma, barminco.com.au and two others.

ns1-03.azure-dns.com, ns4-03.azure-dns.info, ns2-03.azure-dns.net and ns3-03.azure-dns.org each carry two IP addresses. ns1-03.azure-dns.com has 13.107.236.3 and 2603:1061:0:700::3; ns4-03.azure-dns.info has 208.84.5.3 and 2620:1ec:bda:700::3; ns2-03.azure-dns.net has 150.171.21.3 and 2620:1ec:8ec:700::3; ns3-03.azure-dns.org has 204.14.183.3 and 2a01:111:4000:700::3.