splunkcloud.jp - dns.ninja

`splunkcloud.jp`

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

`jp`

	DNSSEC	🔒 Signed (DS record present)
	NS	`z.dns.jp` ⭐
	NS	`a.dns.jp`
	NS	`b.dns.jp`
	NS	`c.dns.jp`
	NS	`d.dns.jp`
	NS	`e.dns.jp`
	NS	`f.dns.jp`
	NS	`g.dns.jp`
	NS	`h.dns.jp`
	SOA	`z.dns.jp`root@dns.jp serial=1784347202

Same first word

DNS History

10 records (8 active, 2 former)

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

● 2015-07-05 15:06:36
● 2026-07-18 05:05:22

●NSns2.markmonitor.com2016-02-04 → 2026-07-18 · 3 obs

○ 2015-07-05 15:06:36
● 2016-02-04 12:18:08
● 2026-07-18 05:05:22

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

● 2015-07-05 15:06:36
● 2026-07-18 05:05:22

●NSns4.markmonitor.com2016-02-04 → 2026-07-18 · 3 obs

○ 2015-07-05 15:06:36
● 2016-02-04 12:18:08
● 2026-07-18 05:05:22

●NSns5.markmonitor.com2016-02-04 → 2026-07-18 · 3 obs

○ 2015-07-05 15:06:36
● 2016-02-04 12:18:08
● 2026-07-18 05:05:22

●NSns6.markmonitor.com2016-02-04 → 2026-07-18 · 3 obs

○ 2015-07-05 15:06:36
● 2016-02-04 12:18:08
● 2026-07-18 05:05:22

●NSns7.markmonitor.com2016-02-04 → 2026-07-18 · 3 obs

○ 2015-07-05 15:06:36
● 2016-02-04 12:18:08
● 2026-07-18 05:05:22

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

○ 2017-02-09 14:47:42
● 2026-02-26 09:24:02
● 2026-07-18 05:05:22

○A72.52.10.142016-02-04 → 2017-02-09 · 5 obs

○ 2015-11-11 19:56:20
● 2016-02-04 12:18:08
● 2017-02-09 14:47:42
○ 2026-02-26 09:24:02
○ 2026-07-18 05:05:22

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

● 2015-07-05 15:06:36
● 2015-11-11 19:56:20
○ 2016-02-04 12:18:08
○ 2026-07-18 05:05:22

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
jp	a.dns.jp, b.dns.jp, c.dns.jp, d.dns.jp...	-
splunkcloud.jp	ns6.markmonitor.com, ns7.markmonitor.com, ns1.markmonitor.com, ns2.markmonitor.com...	-

✅ Authoritative Response

Server:149.112.160.2

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for splunkcloud.jp (unsigned zone)

⏱️ Timing

Total: 3021ms | 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.jp resolves to just one IP address, 204.107.141.148.

Two other host names, along with splunkcloud.biz, splunkstorm.co.in and splunk.com.hk, also share IP numbers with splunkcloud.jp.

Name Servers

splunkcloud.jp delegates authority to 7 name servers: ns1.markmonitor.com, ns2.markmonitor.com, ns3.markmonitor.com plus 4 other.

splunkcloud.jp shares at least some of its name servers with other domains, including silkerandschmitt.com, onetwomarketplace.nl, tencent.tel and two others.

These name servers are frequently seen alongside 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 directs traffic to 149.112.160.1 and 2620:10a:80a8::1.

ns2.markmonitor.com directs traffic to 176.97.158.1 and 2001:67c:10b8::1.

ns3.markmonitor.com directs traffic to 149.112.161.1 and 2620:10a:80a9::1.

ns4.markmonitor.com directs traffic to 192.174.68.1 and 2001:67c:1bc::1.

ns5.markmonitor.com directs traffic to 149.112.160.2 and 2620:10a:80a8::2.

ns6.markmonitor.com directs traffic to 176.97.158.3 and 2001:67c:10b8::3.

ns7.markmonitor.com directs traffic to 149.112.161.2 and 2620:10a:80a9::2.