CF1757305073477-tsm20250907181809

DNSWHOIS.INFO - splunkcloud.be

Search for IP or hostnames:

splunkcloud.be checked at 2025-09-08T04:17:53.457Z 162ms 102/102/102 100% R:12

`splunkcloud.be`

	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}

`be`

	NS	`a.nsset.be`
	NS	`b.nsset.be`
	NS	`c.nsset.be`
	NS	`d.nsset.be`
	NS	`y.nsset.be`
	NS	`z.nsset.be`

Starts with same word
`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`
`splunkcloud.jp`
`splunkcloud.dk`

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

splunkcloud.be points to the IP address: 204.107.141.148.

IP numbers are shared between splunkcloud.be and other host names such as piondb.org, www.splunk.it, splunk.tk, pion.net, and splunk.co.

Seven name servers are delegated to splunkcloud.be, which are ns1.markmonitor.com, ns2.markmonitor.com, ns3.markmonitor.com, ns4.markmonitor.com, ns5.markmonitor.com, ns6.markmonitor.com, and ns7.markmonitor.com.

Name servers of splunkcloud.be are at least partially shared with other domains such as optiopnsexpress.com, bestbuycares.com, fluad.de, petmedsbymail.com, and 1430radiosports.net.

ns1.markmonitor.com, ns2.markmonitor.com, ns3.markmonitor.com, ns4.markmonitor.com, ns5.markmonitor.com, ns6.markmonitor.com, and ns7.markmonitor.com all point to two IP numbers each: 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

TbtMqyT CF johedugfp 2025-09-08