WWW.ROBTEX.COM - bitcap.co

Search for IP or hostnames:

bitcap.co checked at 2025-09-08T03:07:52.362Z 236ms 246/246/246 100% R:21

`bitcap.co`

NS	`ns-293.awsdns-36.com`
		A	2600:9000:5301:2500::1^{🇺🇸 Amazon}
			PTR	`ns-293.awsdns-36.com`
		A	205.251.193.37^{🇺🇸 Amazon}
			PTR	`ns-293.awsdns-36.com`
MX	`aspmx2.googlemail.com`
		A	2a00:1450:400b:c02::1b^{🇮🇪 Google}
			PTR	`dj-in-f27.1e100.net`
		A	172.253.116.27^{🇺🇸 Google}
			PTR	`dj-in-f27.1e100.net`
MX	`aspmx3.googlemail.com`
		A	2a00:1450:400c:c00::1a^{🇧🇪 Google}
			PTR	`ws-in-f26.1e100.net`
			PTR	`ws-in-x1a.1e100.net`
		A	173.194.76.26^{🇺🇸 Google}
			PTR	`ws-in-f26.1e100.net`
NS	`ns-707.awsdns-24.net`
		A	2600:9000:5302:c300::1^{🇺🇸 Amazon}
			PTR	`ns-707.awsdns-24.net`
		A	205.251.194.195^{🇺🇸 Amazon}
			PTR	`ns-707.awsdns-24.net`
NS	`ns-1173.awsdns-18.org`
		A	2600:9000:5304:9500::1^{🇺🇸 Amazon}
			PTR	`ns-1173.awsdns-18.org`
		A	205.251.196.149^{🇺🇸 Amazon}
			PTR	`ns-1173.awsdns-18.org`
MX	`aspmx.l.google.com`
		A	2607:f8b0:4004:c19::1b^{🇺🇸 Google}
			PTR	`bk-in-f27.1e100.net`
		A	172.253.122.26^{🇺🇸 Google}
			PTR	`bh-in-f26.1e100.net`
NS	`ns-1618.awsdns-10.co.uk`
		A	2600:9000:5306:5200::1^{🇺🇸 Amazon}
			PTR	`ns-1618.awsdns-10.co.uk`
		A	205.251.198.82^{🇺🇸 Amazon}
			PTR	`ns-1618.awsdns-10.co.uk`
MX	`alt1.aspmx.l.google.com`
		A	2a00:1450:4013:c1c::1b^{🇳🇱 Google}
			PTR	`yugrqog-in-f27.1e100.net`
		A	192.178.156.27^{🇺🇸 Google}
			PTR	`yugrqog-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`
		A	2a00:1450:4025:c01::1a^{🇵🇱 Google}
			PTR	`rd-in-f26.1e100.net`
		A	142.250.147.27^{🇺🇸 Google}
			PTR	`rd-in-f27.1e100.net`
A	75.2.70.75^{🇺🇸 Amazon}
		PTR	`aacb0a264e514dd48.awsglobalaccelerator.com`
A	99.83.190.102^{🇺🇸 Amazon}
		PTR	`aacb0a264e514dd48.awsglobalaccelerator.com`

`co`

	NS	`ns1.cctld.co`
	NS	`ns2.cctld.co`
	NS	`ns3.cctld.co`
	NS	`ns4.cctld.co`
	NS	`ns5.cctld.co`
	NS	`ns6.cctld.co`
	NS	`ns7.cctld.co`
	NS	`ns8.cctld.co`

Up
`app.bitcap.co`

Starts with same word
`bitcap.io`
`bitcap.net`
`bitcap.se`
`bitcap.com`
`bitcap.co`
`bitcap.ru`

Starts similarily
`pictab.com`
`cpabit.com`
`ibacpt.com`
`tibcap.com`
`ipctba.org.br`
`apibtc.com`
`bapict.com`
`catbip.com`
`bitcap.net`
`abitcp.com`
`tbipac.com`
`abcpti.com`
`bitcap.se`
`bcitpa.info`
`bitcap.com`
`bitcap.co`
`btcapi.org`
`pcbait.com`
`tibcap.eu`
`cpbait.com`
`abctip.com`
`bcipta.com`
`bitcap.ru`
`pacbit.biz`
`pacbit.net`
`bcitpa.com`
`bcipta.org`
`pacbit.org`
`pacbit.com`
`bpacit.com`
`btcapi.net`
`capbit.com`
`bitcap.io`
`baicpt.com`

AI analysis

The parent of app.bitcap.co is bitcap.co.

There are two IP numbers that bitcap.co points to: 75.2.70.75 and 99.83.190.102.

IP numbers are shared between bitcap.co and other host names such as c-risk.com, unifyhs.com, airmasters.in, leanrfp.com, and brookeo.fr.

Four name servers, ns-293.awsdns-36.com, ns-707.awsdns-24.net, ns-1173.awsdns-18.org and ns-1618.awsdns-10.co.uk, are delegated to bitcap.co.

The name servers of bitcap.co are at least partially shared with other domains such as c0unsel.net, diuy5pv2jydea.cloudfront.net, dolightful.com, themedynamics.com, and findsubs.com.

The name servers ns-269.awsdns-33.com, ns-842.awsdns-41.net, ns-1062.awsdns-04.org, ns-1418.awsdns-49.org, ns-789.awsdns-34.net, and ns-1947.awsdns-51.co.uk are frequently used in conjunction.

Two IP numbers, 2600:9000:5301:2500::1 and 205.251.193.37, are pointed to by ns-293.awsdns-36.com. Similarly, ns-707.awsdns-24.net directs to 2600:9000:5302:c300::1 and 205.251.194.195. Moreover, ns-1173.awsdns-18.org is associated with 2600:9000:5304:9500::1 and 205.251.196.149, and ns-1618.awsdns-10.co.uk points to 2600:9000:5306:5200::1 and 205.251.198.82.

The five mail servers, aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com, alt1.aspmx.l.google.com, and alt2.aspmx.l.google.com, are responsible for handling bitcap.co.

Domains such as gssltd.co.in, skibas.com, saltation.com, x-trekkers.com, and washingtoneasttravel.com share some mail servers, at least partially, with bitcap.co.

Mail servers such as aspmx4.googlemail.com, aspmx5.googlemail.com, alt3.aspmx.l.google.com, and alt4.aspmx.l.google.com are frequently employed in combination.

aspmx2.googlemail.com, 2a00:1450:400b:c02::1b, and 172.253.116.27 are related.

aspmx3.googlemail.com, 2a00:1450:400c:c00::1a, and 173.194.76.26 are connected.

aspmx.l.google.com, 2607:f8b0:4004:c19::1b, and 172.253.122.26 are associated.

alt1.aspmx.l.google.com, 2a00:1450:4013:c1c::1b, and 192.178.156.27 are linked.

alt2.aspmx.l.google.com, 2a00:1450:4025:c01::1a, and 142.250.147.27 are correlated.

dbq