`malwarenotice.net`

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

`net`

	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=1784499487

Same first word

malwarenotice.com

malwarenotice.net

DNS History

6 records (4 active, 2 former)

●NSns1-01.azure-dns.com2019-12-26 → 2026-07-19 · 2 obs

● 2019-12-26 08:37:08
● 2026-07-19 22:49:02

●NSns2-01.azure-dns.net2019-12-26 → 2026-07-19 · 2 obs

● 2019-12-26 08:37:08
● 2026-07-19 22:49:02

●NSns3-01.azure-dns.org2019-12-26 → 2026-07-19 · 2 obs

● 2019-12-26 08:37:08
● 2026-07-19 22:49:02

●NSns4-01.azure-dns.info2019-12-26 → 2026-07-19 · 2 obs

● 2019-12-26 08:37:08
● 2026-07-19 22:49:02

○A64.4.6.2332015-06-29 → 2016-05-03 · 4 obs

● 2015-06-29 02:14:28
● 2016-05-03 11:37:48
○ 2019-12-26 08:37:08
○ 2026-07-19 22:49:02

○A65.55.39.122015-06-29 → 2016-05-03 · 4 obs

● 2015-06-29 02:14:28
● 2016-05-03 11:37:48
○ 2019-12-26 08:37:08
○ 2026-07-19 22:49:02

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
net	m.gtld-servers.net, k.gtld-servers.net, b.gtld-servers.net, f.gtld-servers.net...	-
malwarenotice.net	ns1-01.azure-dns.com, ns2-01.azure-dns.net, ns3-01.azure-dns.org, ns4-01.azure-dns.info	2 records

✅ Authoritative Response

Server:150.171.21.1

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for malwarenotice.net (unsigned zone)

⏱️ Timing

Total: 2466ms | Queries: -

📄 Records

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

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns2-01.azure-dns.net, ns2-01.azure-dns.net)

Analysis

Name Servers

The domain malwarenotice.net is delegated to these four name servers: ns1-01.azure-dns.com, ns4-01.azure-dns.info, ns2-01.azure-dns.net and ns3-01.azure-dns.org.

malwarenotice.net shares at least some of its name servers with other domains, including matchscorer.net, geekclub.pl, agbar.cat and two others.

The host names ns1-01.azure-dns.com, ns4-01.azure-dns.info, ns2-01.azure-dns.net and ns3-01.azure-dns.org each resolve to two IP addresses: ns1-01.azure-dns.com resolves to 13.107.236.1 and 2603:1061:0:700::1; ns4-01.azure-dns.info resolves to 208.84.5.1 and 2620:1ec:bda:700::1; ns2-01.azure-dns.net resolves to 150.171.21.1 and 2620:1ec:8ec:700::1; ns3-01.azure-dns.org resolves to 204.14.183.1 and 2a01:111:4000:700::1.

malwarenotice.net - robtex.com