splunkcloud.com.sg - dns.ninja

`splunkcloud.com.sg`

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

`com.sg`

	DNSSEC	⚠️ Not signed
	NS	`ds.sgnic.sg` ⭐
	NS	`dsany2.sgnic.sg` ⚠️ Not in parent delegation
	NS	`dsany3.sgnic.sg` ⚠️ Not in parent delegation
	NS	`dsany4.sgnic.sg` ⚠️ Not in parent delegation
	NS	`pch.sgzones.sg` ⚠️ Not in parent delegation
	SOA	`ds.sgnic.sg`dna@sgnic.sg serial=2607180730

Same first word

DNS History

10 records (8 active, 2 former)

●NSns1.markmonitor.com2015-04-28 → 2026-07-18 · 2 obs

● 2015-04-28 19:55:38
● 2026-07-18 08:47:26

●NSns2.markmonitor.com2016-03-25 → 2026-07-18 · 3 obs

○ 2015-04-28 19:55:38
● 2016-03-25 03:22:08
● 2026-07-18 08:47:26

●NSns3.markmonitor.com2015-04-28 → 2026-07-18 · 2 obs

● 2015-04-28 19:55:38
● 2026-07-18 08:47:26

●NSns4.markmonitor.com2016-03-25 → 2026-07-18 · 3 obs

○ 2015-04-28 19:55:38
● 2016-03-25 03:22:08
● 2026-07-18 08:47:26

●NSns5.markmonitor.com2016-03-25 → 2026-07-18 · 3 obs

○ 2015-04-28 19:55:38
● 2016-03-25 03:22:08
● 2026-07-18 08:47:26

●NSns6.markmonitor.com2016-03-25 → 2026-07-18 · 3 obs

○ 2015-04-28 19:55:38
● 2016-03-25 03:22:08
● 2026-07-18 08:47:26

●NSns7.markmonitor.com2016-03-25 → 2026-07-18 · 3 obs

○ 2015-04-28 19:55:38
● 2016-03-25 03:22:08
● 2026-07-18 08:47:26

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

○ 2017-04-03 05:09:56
● 2026-02-27 05:35:34
● 2026-07-18 08:47:26

○A72.52.10.142016-03-25 → 2017-04-03 · 5 obs

○ 2015-12-12 07:31:48
● 2016-03-25 03:22:08
● 2017-04-03 05:09:56
○ 2026-02-27 05:35:34
○ 2026-07-18 08:47:26

○A93.191.168.522015-04-28 → 2015-12-12 · 4 obs

● 2015-04-28 19:55:38
● 2015-12-12 07:31:48
○ 2016-03-25 03:22:08
○ 2026-07-18 08:47:26

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
sg	pch.sgzones.sg, dsany2.sgnic.sg, dsany3.sgnic.sg, dsany4.sgnic.sg	-
splunkcloud.com.sg	ns2.markmonitor.com, ns6.markmonitor.com, ns7.markmonitor.com, ns1.markmonitor.com...	-

✅ Authoritative Response

Server:149.112.160.1

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for splunkcloud.com.sg (unsigned zone)

⏱️ Timing

Total: 574ms | Queries: -

📄 Records

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

Analysis

IP Addresses

splunkcloud.com.sg resolves to just one IP address, 204.107.141.148.

Two other host names, along with splunk.org.in, splunk.ec and mysplunk.com, also share IP numbers with splunkcloud.com.sg.

Name Servers

splunkcloud.com.sg is served by 7 authoritative name servers — among them ns1.markmonitor.com, ns2.markmonitor.com, ns3.markmonitor.com and 4 others.

The name servers of splunkcloud.com.sg overlap at least partially with those of other domains — among them shutterstokc.ru, learningforlife.org, veraflight.com and two more.

These name servers commonly co-occur with the name servers ns4.markmonitor.com, ns5.markmonitor.com, ns6.markmonitor.com and ns7.markmonitor.com.

Host names that have two IP addresses:

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

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

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

ns4.markmonitor.com resolves to two addresses: 192.174.68.1 and 2001:67c:1bc::1.

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

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

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