DNSWHOIS.INFO - ban.to

Search for IP or hostnames:

ban.to checked at 2025-09-06T19:09:44.918Z 263ms 147/147/147 100% R:15

`ban.to`

CNAME	`park.io`
NS	`ns-441.awsdns-55.com`
		A	2600:9000:5301:b900::1 ^{🇺🇸 Amazon}
			PTR	`ns-441.awsdns-55.com`
		A	205.251.193.185^{🇺🇸 Amazon}
			PTR	`ns-441.awsdns-55.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.27^{🇺🇸 Google}
			PTR	`ws-in-f27.1e100.net`
NS	`ns-672.awsdns-20.net`
		A	2600:9000:5302:a000::1 ^{🇺🇸 Amazon}
			PTR	`ns-672.awsdns-20.net`
		A	205.251.194.160^{🇺🇸 Amazon}
			PTR	`ns-672.awsdns-20.net`
NS	`ns-1348.awsdns-40.org`
		A	2600:9000:5305:4400::1 ^{🇺🇸 Amazon}
			PTR	`ns-1348.awsdns-40.org`
		A	205.251.197.68^{🇺🇸 Amazon}
			PTR	`ns-1348.awsdns-40.org`
MX	`aspmx.l.google.com`
		A	2607:f8b0:4004:c1b::1b ^{🇺🇸 Google}
			PTR	`wv-in-f27.1e100.net`
		A	172.253.122.26^{🇺🇸 Google}
			PTR	`bh-in-f26.1e100.net`
NS	`ns-1624.awsdns-11.co.uk`
		A	2600:9000:5306:5800::1 ^{🇺🇸 Amazon}
			PTR	`ns-1624.awsdns-11.co.uk`
		A	205.251.198.88^{🇺🇸 Amazon}
			PTR	`ns-1624.awsdns-11.co.uk`
MX	`alt1.aspmx.l.google.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	`alt2.aspmx.l.google.com`
		A	2a00:1450:400c:c00::1a ^{🇧🇪 Google}
			PTR	`ws-in-f26.1e100.net`
			PTR	`ws-in-x1a.1e100.net`
		A	173.194.76.27^{🇺🇸 Google}
			PTR	`ws-in-f27.1e100.net`
A	54.164.10.11^{🇺🇸 Amazon}
		PTR	`ec2-54-164-10-11.compute-1.amazonaws.com`
A	54.205.24.57^{🇺🇸 Amazon}
		PTR	`ec2-54-205-24-57.compute-1.amazonaws.com`

`to`

	NS	`ns01.trs-dns.com`
	NS	`ns10.trs-dns.info`
	NS	`ns01.trs-dns.net`
	NS	`ns10.trs-dns.org`

Up
`www.ban.to`

Starts with same word
`ban.wtf`
`ban.io`
`ban.dk`
`ban.co.za`
`ban.ch`
`ban.cz`
`ban.la`
`ban.one`
`ban.mx`
`ban.net`
`ban.pl`
`ban.aero`
`ban.com.tw`
`ban.info`
`ban.cool`
`ban.org`
`ban.at`
`ban.ai`
`ban.us`
`ban.com`
`ban.ee`
`ban.ru`
`ban.com.ua`
`ban.center`
`ban.lt`
`ban.se`
`ban.be`
`ban.eu`
`ban.hu`
`ban.im`
`ban.com.co`
`ban.co`
`ban.systems`
`ban.lv`
`ban.de`
`ban.si`
`ban.fi`
`ban.re`
`ban.ink`
`ban.hr`
`ban.fr`
`ban.me`
`ban.by`
`ban.to`
`ban.gr`
`ban.az`
`ban.net.ua`
`ban.tw`
`ban.su`
`ban.com.tr`
`ban.s3.amazonaws.com`
`ban.do`

Starts similarily
`anb.co.nz`
`nab.ie`
`nba.name`
`nba.so`
`nab.co.za`
`ban.ai`
`nba.ge`
`ban.us`
`nab.com.vn`
`bna.tn`
`nba.com.de`
`ban.com`
`nba.com.mx`
`abn.eu`
`abn.in`
`nab.kiev.ua`
`nba.com.tw`
`nab.com.cn`
`ban.ee`
`ban.ru`
`nba.hosting`
`abn.com.tr`
`bna.com.es`
`anb.company`
`nba.co.jp`
`nba.org`
`nba`
`nba.gov.cy`
`bna.com.ar`
`nab.gov.gh`
`bna.dz`
`bna.ca`
`nab.be`
`nba.or.jp`
`anb.su`
`abn.us`
`ban.com.ua`
`bna.in`
`bna.org.au`
`abn.mobi`
`abn.net`
`abn.nl`
`nab.io`
`abn.cn`
`nab`
`nba.com.pl`
`ban.center`
`nab.su`
`nba.info`
`ban.lt`
`nba.net.cn`
`nab.tv`
`nba.ch`
`abn.info`
`abn.asia`
`nba.ws`
`bna.kr`
`nab.gov.dm`
`anb.ch`
`bna.be`
`bna.co`
`anb.com.es`
`nab.cz`
`ban.se`
`nba.me`
`nba.eu`
`abn.com`
`nab.com.au`
`nba.no`
`nba.moe`
`ban.be`
`nab.biz`
`nba.vc`
`nab.se`
`bna.com.au`
`abn.store`
`anb.com.pl`
`nba.gov.au`
`anb.co.uk`
`abn.kr`
`bna.it`
`nab.com.my`
`ban.eu`
`bna.org.uk`
`nab.kz`
`anb.info`
`nba.com.tr`
`nba.net`
`ban.hu`
`ban.im`
`ban.com.co`
`nba.gs`
`bna.se`
`nba.buzz`
`anb.com.sg`
`nba.es`
`nab.no`
`abn.co.kr`
`bna.fi`
`nab.bg`

AI analysis

The parent of www.ban.to is ban.to.

ban.to is configured to point to two IP addresses: 54.164.10.11 and 54.205.24.57.

The IP numbers of ban.to are also shared by other host names such as ec2-54-164-10-11.compute-1.amazonaws.com, app.park.io, park.io, and ec2-54-205-24-57.compute-1.amazonaws.com.

Four name servers, ns-441.awsdns-55.com, ns-672.awsdns-20.net, ns-1348.awsdns-40.org, and ns-1624.awsdns-11.co.uk, are assigned to ban.to.

The domain ban.to shares at least some of its name servers with other domains such as rs374-realsender.com, staticit.com, sk-indonesia.com, sns.ap-southeast-2.amazonaws.com, and lupicia.co.jp.

The name servers ns-1470.awsdns-55.org, ns-1787.awsdns-31.co.uk, ns-318.awsdns-39.com, ns-1072.awsdns-06.org, ns-116.awsdns-14.com, ns-2022.awsdns-60.co.uk, ns-779.awsdns-33.net, ns-248.awsdns-31.com, and ns-923.awsdns-51.net are typically used in conjunction.

ns-441.awsdns-55.com, ns-672.awsdns-20.net, ns-1348.awsdns-40.org, and ns-1624.awsdns-11.co.uk each point to two IP numbers: 2600:9000:5301:b900::1 and 205.251.193.185, 2600:9000:5302:a000::1 and 205.251.194.160, 2600:9000:5305:4400::1 and 205.251.197.68, 2600:9000:5306:5800::1 and 205.251.198.88 respectively.

The five mail servers handling ban.to are aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com, alt1.aspmx.l.google.com, and alt2.aspmx.l.google.com.

Other domains such as x-fire.us, catandmousedesign.com, s-generation.com, skaggbyran.se, and binaryawesome.com share at least a portion of their mail servers with ban.to.

The mail servers aspmx4.googlemail.com, aspmx5.googlemail.com, alt3.aspmx.l.google.com, and alt4.aspmx.l.google.com are commonly used in conjunction.

aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com, alt1.aspmx.l.google.com, and alt2.aspmx.l.google.com all point to two IP numbers each: 2a00:1450:400b:c02::1b and 172.253.116.27 for aspmx2.googlemail.com and alt1.aspmx.l.google.com, and 2a00:1450:400c:c00::1a and 173.194.76.27 for aspmx3.googlemail.com, aspmx.l.google.com, and alt2.aspmx.l.google.com.

dbq