splunkcloud.mx - dns.ninja

`splunkcloud.mx`

DNSSEC	⚠️ Not signed
A	204.107.141.148^{🇺🇸 SPLUNK204.107.141.0/24 Splunk-West-2}
NS	`ns1.markmonitor.com` ⭐
		A	2620:10a:80a8::1^{🇨🇦 CIRA-22620:10a:80a8::/48 markmonitor v6 cloud1 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
		A	149.112.160.1^{🇨🇦 CIRA-2149.112.160.0/24 markmonitor v4 cloud1 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
NS	`ns2.markmonitor.com`
		A	2001:67c:10b8::1^{🇨🇭 RCODEZERO-ANYCAST-SEC22001:67c:10b8::/48 IPCOM-anycast-net}
			PTR	`ns2.markmonitor.com`
		A	176.97.158.1^{🇦🇹 RCODEZERO-ANYCAST-SEC2176.97.158.0/24 NICat-anycast-net}
			PTR	`ns2.markmonitor.com`
NS	`ns3.markmonitor.com`
		A	2620:10a:80a9::1^{🇨🇦 CIRA-32620:10a:80a9::/48 markmonitor v6 cloud2 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
		A	149.112.161.1^{🇨🇦 CIRA-3149.112.161.0/24 markmonitor v4 cloud2 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
NS	`ns4.markmonitor.com`
		A	2001:67c:1bc::1^{🇦🇹 RCODEZERO-ANYCAST-SEC1-TLD2001:67c:1bc::/48 IPCom-NET Anycast}
			PTR	`ns1.markmonitor.com`
		A	192.174.68.1^{🇦🇹 RCODEZERO-ANYCAST-SEC1-TLD192.174.68.0/24 NICat-anycast-net}
			PTR	`ns1.markmonitor.com`
NS	`ns5.markmonitor.com`
		A	2620:10a:80a8::2^{🇨🇦 CIRA-22620:10a:80a8::/48 markmonitor v6 cloud1 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
		A	149.112.160.2^{🇨🇦 CIRA-2149.112.160.0/24 markmonitor v4 cloud1 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
NS	`ns6.markmonitor.com` ⚠️ Not in parent delegation
		A	2001:67c:10b8::3^{🇨🇭 RCODEZERO-ANYCAST-SEC22001:67c:10b8::/48 IPCOM-anycast-net}
			PTR	`ns6.markmonitor.com`
		A	176.97.158.3^{🇦🇹 RCODEZERO-ANYCAST-SEC2176.97.158.0/24 NICat-anycast-net}
			PTR	`ns6.markmonitor.com`
NS	`ns7.markmonitor.com` ⚠️ Not in parent delegation
		A	2620:10a:80a9::2^{🇨🇦 CIRA-32620:10a:80a9::/48 markmonitor v6 cloud2 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
		A	149.112.161.2^{🇨🇦 CIRA-3149.112.161.0/24 markmonitor v4 cloud2 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
TXT	`v=spf1 include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email ~all`
SOA	`ns1.markmonitor.com`hostmaster@markmonitor.com 2025-10-23 #1

`mx`

	DNSSEC	🔒 Signed (DS record present)
	NS	`m.mx-ns.mx` ⭐
	NS	`c.mx-ns.mx`
	NS	`e.mx-ns.mx`
	NS	`i.mx-ns.mx`
	NS	`o.mx-ns.mx`
	NS	`x.mx-ns.mx`
	TXT	`v=spf1 -all`
	SOA	`m.mx-ns.mx`hostmaster@nic.mx serial=1782576049

Same first word

DNS History

10 records (8 active, 2 former)

●NSns1.markmonitor.com2015-05-02 → 2026-06-27 · 2 obs

● 2015-05-02 18:46:52
● 2026-06-27 16:13:30

●NSns2.markmonitor.com2016-03-15 → 2026-06-27 · 3 obs

○ 2015-05-02 18:46:52
● 2016-03-15 05:29:30
● 2026-06-27 16:13:30

●NSns3.markmonitor.com2015-05-02 → 2026-06-27 · 2 obs

● 2015-05-02 18:46:52
● 2026-06-27 16:13:30

●NSns4.markmonitor.com2016-03-15 → 2026-06-27 · 3 obs

○ 2015-05-02 18:46:52
● 2016-03-15 05:29:30
● 2026-06-27 16:13:30

●NSns5.markmonitor.com2016-03-15 → 2026-06-27 · 3 obs

○ 2015-05-02 18:46:52
● 2016-03-15 05:29:30
● 2026-06-27 16:13:30

●NSns6.markmonitor.com2016-03-15 → 2026-06-27 · 3 obs

○ 2015-05-02 18:46:52
● 2016-03-15 05:29:30
● 2026-06-27 16:13:30

●NSns7.markmonitor.com2016-03-15 → 2026-06-27 · 3 obs

○ 2015-05-02 18:46:52
● 2016-03-15 05:29:30
● 2026-06-27 16:13:30

●A204.107.141.1482026-02-27 → 2026-06-27 · 3 obs

○ 2017-03-29 08:24:42
● 2026-02-27 05:35:34
● 2026-06-27 16:13:30

○A72.52.10.142016-03-15 → 2017-03-29 · 5 obs

○ 2015-12-07 21:15:56
● 2016-03-15 05:29:30
● 2017-03-29 08:24:42
○ 2026-02-27 05:35:34
○ 2026-06-27 16:13:30

○A93.191.168.522015-05-02 → 2015-12-07 · 4 obs

● 2015-05-02 18:46:52
● 2015-12-07 21:15:56
○ 2016-03-15 05:29:30
○ 2026-06-27 16:13:30

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
mx	c.mx-ns.mx, i.mx-ns.mx, o.mx-ns.mx, e.mx-ns.mx...	-
splunkcloud.mx	ns5.markmonitor.com, ns4.markmonitor.com, ns2.markmonitor.com, ns3.markmonitor.com...	-

✅ Authoritative Response

Server:149.112.160.1

NS records: ns5.markmonitor.com, ns4.markmonitor.com, ns2.markmonitor.com, ns3.markmonitor.com, ns1.markmonitor.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for splunkcloud.mx (unsigned zone)

⏱️ Timing

Total: 1780ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`204.107.141.148`
NS	7	`ns1.markmonitor.com, ns2.markmonitor.com...`
TXT	1	`v=spf1 include:%{i}._ip.%{h}._ehlo.%{d}.`
SOA	1	`ns1.markmonitor.com hostmaster.markmonit`

Analysis

IP Addresses

splunkcloud.mx resolves to just one IP address, 204.107.141.148.

Two other host names, along with 360-devops.com, splunk.tv and splunk.ws, also share IP numbers with splunkcloud.mx.

Name Servers

The DNS delegation for splunkcloud.mx covers 7 name servers: ns1.markmonitor.com, ns2.markmonitor.com, ns3.markmonitor.com and 4 more.

splunkcloud.mx has at least partial name server overlap with other domains, such as morningstarcomody.com, calvinkleininc.com, rawhd.com and two others.

ns4.markmonitor.com, ns5.markmonitor.com and ns6.markmonitor.com — plus 5 other name servers — are commonly paired with these name servers.

Host names that have two IP addresses:

ns1.markmonitor.com maps to two IP addresses — 149.112.160.1 and 2620:10a:80a8::1.

ns2.markmonitor.com maps to two IP addresses — 176.97.158.1 and 2001:67c:10b8::1.

ns3.markmonitor.com maps to two IP addresses — 149.112.161.1 and 2620:10a:80a9::1.

ns4.markmonitor.com maps to two IP addresses — 192.174.68.1 and 2001:67c:1bc::1.

ns5.markmonitor.com maps to two IP addresses — 149.112.160.2 and 2620:10a:80a8::2.

ns6.markmonitor.com maps to two IP addresses — 176.97.158.3 and 2001:67c:10b8::3.

ns7.markmonitor.com maps to two IP addresses — 149.112.161.2 and 2620:10a:80a9::2.