`nullmx.couldplay.com`

DNSSEC	⚠️ Not signed
A	13.248.169.48^{🇺🇸 Amazon13.248.160.0/20}
		PTR	`a904c694c05102f30.awsglobalaccelerator.com`
A	76.223.54.146^{🇺🇸 Amazon76.223.48.0/20}
NS	`ns1.namefind.com` ⭐ ⚠️ Not in parent delegation
		A	97.74.99.64^{🇺🇸 GODADDY-DNS97.74.98.0/23}
			PTR	`ns1.namefind.com`
NS	`ns2.namefind.com` ⚠️ Not in parent delegation
		A	173.201.67.64^{🇺🇸 GODADDY-DNS173.201.66.0/23}
			PTR	`ns2.namefind.com`
TXT	`v=spf1 -all`
SOA	`ns1.namefind.com`dns@jomax.net 2023-03-15 #0

`couldplay.com`

	DNSSEC	⚠️ Not signed
	A	13.248.169.48^{🇺🇸 Amazon13.248.160.0/20}
	A	76.223.54.146^{🇺🇸 Amazon76.223.48.0/20}
	NS	`ns1.namefind.com` ⭐
	NS	`ns2.namefind.com`
	TXT	`v=spf1 -all`
	SOA	`ns1.namefind.com`dns@jomax.net 2023-03-15 #0

Previously MX for

couldplay.com

Same first word

nullmx.org

nullmx.com

nullmx.net

DNS History

9 records (4 active, 5 former)

○NSbuy.internettraffic.com2015-11-03 → 2016-05-07 · 4 obs

● 2015-11-03 11:52:02
● 2016-05-07 03:29:12
○ 2026-07-08 14:24:26
○ 2026-08-05 18:10:26

●NSns1.namefind.com2026-07-08 → 2026-08-05 · 3 obs

○ 2016-05-07 03:29:12
● 2026-07-08 14:24:26
● 2026-08-05 18:10:26

●NSns2.namefind.com2026-07-08 → 2026-08-05 · 3 obs

○ 2016-05-07 03:29:12
● 2026-07-08 14:24:26
● 2026-08-05 18:10:26

○NSsell.internettraffic.com2015-11-03 → 2016-05-07 · 4 obs

● 2015-11-03 11:52:02
● 2016-05-07 03:29:12
○ 2026-07-08 14:24:26
○ 2026-08-05 18:10:26

●A13.248.169.482026-07-08 → 2026-08-05 · 3 obs

○ 2016-05-07 03:29:12
● 2026-07-08 14:24:26
● 2026-08-05 18:10:26

○A209.181.247.1052015-06-11 → 2015-06-11 · 3 obs

● 2015-06-11 03:33:28
○ 2015-11-03 11:52:02
○ 2026-08-05 18:10:26

○A69.172.201.1532016-05-07 → 2016-05-07 · 4 obs

○ 2016-01-23 22:22:28
● 2016-05-07 03:29:12
○ 2026-07-08 14:24:26
○ 2026-08-05 18:10:26

○A69.172.201.2082015-11-03 → 2016-01-23 · 5 obs

○ 2015-06-11 03:33:28
● 2015-11-03 11:52:02
● 2016-01-23 22:22:28
○ 2016-05-07 03:29:12
○ 2026-08-05 18:10:26

●A76.223.54.1462026-07-08 → 2026-08-05 · 3 obs

○ 2016-05-07 03:29:12
● 2026-07-08 14:24:26
● 2026-08-05 18:10:26

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	f.gtld-servers.net, h.gtld-servers.net, b.gtld-servers.net, d.gtld-servers.net...	-
couldplay.com	ns2.namefind.com, ns1.namefind.com	2 records

✅ Authoritative Response

Server:97.74.99.64

NS records: ns2.namefind.com, ns1.namefind.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for couldplay.com (unsigned zone)

⏱️ Timing

Total: 290ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`13.248.169.48, 76.223.54.146`
NS	2	`ns1.namefind.com, ns2.namefind.com`
TXT	1	`v=spf1 -all`
SOA	1	`ns1.namefind.com dns.jomax.net`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns2.namefind.com, ns1.namefind.com)

Analysis

IP Addresses

nullmx.couldplay.com has two IP addresses: 13.248.169.48 and 76.223.54.146

Among the host names that share IP numbers with nullmx.couldplay.com are smtp-in.wow-life.com, fada.mobi, pg185.com and two others.

Name Servers

DNS delegation for nullmx.couldplay.com points to two name servers: ns1.namefind.com and ns2.namefind.com.

nullmx.couldplay.com has the same name server delegation as a number of other domains, such as streamingmovie.com, highoutput.net, www.jahex.com and two more.

Some name servers delegated to nullmx.couldplay.com are also used by other domains, notably raww.nl and mujaddid.org.

These name servers are routinely deployed together with the name servers verification-gsjsth52a2zvxihb6hoygp.ns101.verify.hn.

ns1.namefind.com → 97.74.99.64 and ns2.namefind.com → 173.201.67.64: one IP number per host name.

nullmx.couldplay.com - robtex.com