CF1757308650146-tsm20250907181809

DNSWHOIS.INFO - splunkcloud.jp

Search for IP or hostnames:

splunkcloud.jp checked at 2025-09-08T05:17:30.128Z 161ms 102/102/102 100% R:13

`splunkcloud.jp`

	NS	`ns1.markmonitor.com`
			A	2620:10a:80a8::1 ^{🇨🇦 CIRA-CLOUD1}
			A	149.112.160.1^{🇨🇦 CIRA-CLOUD1}
	NS	`ns2.markmonitor.com`
			A	2001:67c:10b8::1 ^{🇨🇭 RCODEZERO-ANYCAST-SEC2}
				PTR	`ns2.markmonitor.com`
			A	176.97.158.1^{🇦🇹 RCODEZERO-ANYCAST-SEC2}
				PTR	`ns2.markmonitor.com`
	NS	`ns3.markmonitor.com`
			A	2620:10a:80a9::1 ^{🇨🇦 CIRA-CLOUD2}
			A	149.112.161.1^{🇨🇦 CIRA-CLOUD2}
	NS	`ns4.markmonitor.com`
			A	2001:67c:1bc::1 ^{🇦🇹 RcodeZero Anycast DNS}
				PTR	`ns1.markmonitor.com`
			A	192.174.68.1^{🇦🇹 RcodeZero Anycast DNS}
				PTR	`ns1.markmonitor.com`
	NS	`ns5.markmonitor.com`
			A	2620:10a:80a8::2 ^{🇨🇦 CIRA-CLOUD1}
			A	149.112.160.2^{🇨🇦 CIRA-CLOUD1}
	NS	`ns6.markmonitor.com`
			A	2001:67c:10b8::3 ^{🇨🇭 RCODEZERO-ANYCAST-SEC2}
				PTR	`ns6.markmonitor.com`
			A	176.97.158.3^{🇦🇹 RCODEZERO-ANYCAST-SEC2}
				PTR	`ns6.markmonitor.com`
	NS	`ns7.markmonitor.com`
			A	2620:10a:80a9::2 ^{🇨🇦 CIRA-CLOUD2}
			A	149.112.161.2^{🇨🇦 CIRA-CLOUD2}
	A	204.107.141.148^{🇺🇸 Splunk}

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

Starts with same word
`splunkcloud.systems`
`splunkcloud.biz`
`splunkcloud.info`
`splunkcloud.ch`
`splunkcloud.net`
`splunkcloud.ca`
`splunkcloud.cl`
`splunkcloud.at`
`splunkcloud.co.in`
`splunkcloud.com.mx`
`splunkcloud.mx`
`splunkcloud.de`
`splunkcloud.sg`
`splunkcloud.eu`
`splunkcloud.org`
`splunkcloud.es`
`splunkcloud.com.au`
`splunkcloud.it`
`splunkcloud.tv`
`splunkcloud.in`
`splunkcloud.co`
`splunkcloud.us`
`splunkcloud.pl`
`splunkcloud.mobi`
`splunkcloud.jp`
`splunkcloud.dk`
`splunkcloud.co.nz`
`splunkcloud.com.sg`
`splunkcloud.ie`
`splunkcloud.fr`
`splunkcloud.be`
`splunkcloud.cz`
`splunkcloud.com`
`splunkcloud.ru`
`splunkcloud.com.br`
`splunkcloud.com.es`

Starts similarily
`splunkcloud.jp`
`splunkcloud.dk`
`splunkcloud.co.nz`
`splunkcloud.com.sg`
`splunkcloud.ie`
`splunkcloud.fr`
`splunkcloud.be`
`splunkcloud.cz`
`splunkcloud.com`
`splunkcloud.ru`
`splunkcloud.com.br`
`splunkcloud.com.es`
`splunkcloud.systems`
`splunkcloud.biz`
`splunkcloud.info`
`splunkcloud.ch`
`splunkcloud.net`
`splunkcloud.ca`
`splunkcloud.cl`
`splunkcloud.at`
`splunkcloud.co.in`
`splunkcloud.com.mx`
`splunkcloud.mx`
`splunkcloud.de`
`splunkcloud.sg`
`splunkcloud.eu`
`splunkcloud.org`
`splunkcloud.es`
`splunkcloud.com.au`
`splunkcloud.it`
`splunkcloud.tv`
`splunkcloud.in`
`splunkcloud.co`
`splunkcloud.us`
`splunkcloud.pl`
`splunkcloud.mobi`

AI analysis

204.107.141.148 is the IP address that splunkcloud.jp points to.

The IP numbers of splunkcloud.jp are also shared by other host names such as splunkcloud.info, splunk.pt, splunkcloud.ch, splunk.com.my, and splunkmobile.cl.

The delegation of splunkcloud.jp is to seven name servers: ns1.markmonitor.com, ns2.markmonitor.com, ns3.markmonitor.com, ns4.markmonitor.com, ns5.markmonitor.com, ns6.markmonitor.com, and ns7.markmonitor.com.

The domain splunkcloud.jp partially shares its name servers with other domains such as silkerandschmitt.com, tencent.tel, samsclubauctions.net, cpasoftware.org, and waterswealthmanagement.com.

ns1.markmonitor.com, ns2.markmonitor.com, ns3.markmonitor.com, ns4.markmonitor.com, ns5.markmonitor.com, ns6.markmonitor.com, and ns7.markmonitor.com each point to two IP numbers: 2620:10a:80a8::1 and 149.112.160.1, 2001:67c:10b8::1 and 176.97.158.1, 2620:10a:80a9::1 and 149.112.161.1, 2001:67c:1bc::1 and 192.174.68.1, 2620:10a:80a8::2 and 149.112.160.2, 2001:67c:10b8::3 and 176.97.158.3, 2620:10a:80a9::2 and 149.112.161.2 respectively.

dbq

ZSPhTVe CF johedugfp 2025-09-08