DNSWHOIS.INFO - tch.to

Search for IP or hostnames:

tch.to checked at 2025-09-06T23:38:00.664Z 6534ms 153/153/153 100% R:16

`tch.to`

MX	`aspmx.l.google.com`
		A	2607:f8b0:4004:c21::1b ^{🇺🇸 Google}
			PTR	`pe-in-f27.1e100.net`
		A	172.253.122.27^{🇺🇸 Google}
			PTR	`bh-in-f27.1e100.net`
NS	`dns1.p01.nsone.net`
		A	2620:4d:4000:6259:7:1:0:1 ^{🇺🇸 NSONE}
			PTR	`dns1.p01.nsone.net`
		A	198.51.44.1^{🇺🇸 NSONE}
			PTR	`dns1.p01.nsone.net`
NS	`dns2.p01.nsone.net`
		A	2a00:edc0:6259:7:1::2 ^{🇺🇸 NSONE}
			PTR	`dns2.p01.nsone.net`
		A	198.51.45.1^{🇺🇸 NSONE}
			PTR	`dns2.p01.nsone.net`
NS	`dns3.p01.nsone.net`
		A	2620:4d:4000:6259:7:1:0:3 ^{🇺🇸 NSONE}
			PTR	`dns3.p01.nsone.net`
		A	198.51.44.65^{🇺🇸 NSONE}
			PTR	`dns3.p01.nsone.net`
NS	`dns4.p01.nsone.net`
		A	2a00:edc0:6259:7:1::4 ^{🇺🇸 NSONE}
			PTR	`dns4.p01.nsone.net`
		A	198.51.45.65^{🇺🇸 NSONE}
			PTR	`dns4.p01.nsone.net`
MX	`alt1.aspmx.l.google.com`
		A	2a00:1450:400b:c02::1a ^{🇮🇪 Google}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.26^{🇺🇸 Google}
			PTR	`dj-in-f26.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.26^{🇺🇸 Google}
			PTR	`ws-in-f26.1e100.net`
MX	`alt3.aspmx.l.google.com`
		A	2a00:1450:4025:402::1a ^{🇳🇱 Google}
			PTR	`rb-in-f26.1e100.net`
		A	142.250.102.26^{🇺🇸 Google}
			PTR	`rb-in-f26.1e100.net`
MX	`alt4.aspmx.l.google.com`
		A	2a00:1450:4013:c1c::1b ^{🇳🇱 Google}
			PTR	`yugrqog-in-f27.1e100.net`
		A	192.178.156.26^{🇺🇸 Google}
			PTR	`yugrqog-in-f26.1e100.net`
A	2600:1f18:16e:df01::258 ^{🇺🇸 Amazon}
A	2600:1f18:16e:df01::259 ^{🇺🇸 Amazon}
A	18.208.88.157^{🇺🇸 Amazon}
		PTR	`ec2-18-208-88-157.compute-1.amazonaws.com`
A	98.84.224.111^{🇺🇸 Amazon}
		PTR	`ec2-98-84-224-111.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`

Starts with same word
`tch.ie`
`tch.co.za`
`tch.net`
`tch.wtf`
`tch.org`
`tch.nl`
`tch.gov.tw`
`tch.ch`
`tch.org.nz`
`tch.ru`
`tch.ua`
`tch.be`
`tch.or.jp`
`tch.edgekey.net`
`tch.ca`
`tch.biz`
`tch.kiev.ua`
`tch.ae`
`tch.es`
`tch.cz`
`tch.by`
`tch.com.tr`
`tch.hu`
`tch.pl`
`tch.co.th`
`tch.co`
`tch.media`
`tch.co.uk`
`tch.gr`
`tch.cn`
`tch.com`
`tch.in`
`tch.to`
`tch.cl`
`tch.me`
`tch.dk`
`tch.com.tw`
`tch.fr`
`tch.org.tw`
`tch.com.br`
`tch.fm`
`tch.de`
`tch.se`
`tch.vn`

Starts similarily
`hct.gr`
`hct.com.vn`
`htc.kr`
`tch.vn`
`cht.ro`
`htc.nsw.edu.au`
`tch.ie`
`hct.cn`
`cth.spdns.de`
`thc.md`
`tch.co.za`
`cth.us`
`cth.at`
`htc.ca`
`cth.fr`
`cht.sg`
`tch.net`
`htc.nl`
`cht.gov.in`
`cht.tv`
`cht.at`
`hct.nl`
`cht.pf`
`thc.team`
`hct.org`
`tch.wtf`
`htc.uk.com`
`hct.it`
`thc.com.es`
`cht.nhs.uk`
`cht.no`
`cth.jp`
`thc.salon`
`htc.ph`
`hct.vn`
`htc.coop`
`hct.mx`
`hct.biz`
`cht.net.tw`
`thc.mba`
`htc.co.za`
`htc.edu.cn`
`hct.ae`
`hct.net.au`
`thc.com`
`thc.co.za`
`tch.org`
`thc.run`
`hct.pl`
`htc.com.sa`
`tch.nl`
`thc.org.nz`
`tch.gov.tw`
`cth.ca`
`thc.toys`
`cth.co`
`cht.cl`
`hct.com.tw`
`cht.me`
`cth.com.hk`
`thc.academy`
`htc.no`
`htc.ru`
`htc.gr`
`hct.ac.ae`
`thc.ws`
`hct.pt`
`thc.org.uk`
`tch.ch`
`htc.co.at`
`thc.dk`
`hct.at`
`tch.org.nz`
`cht.tw`
`hct.taxi`
`htc.fi`
`htc.im`
`cht.im`
`cht.kz`
`cht.com.co`
`thc.com.ua`
`cth.vn`
`cth.as`
`htc.com.tw`
`htc.edu`
`cht.net.au`
`tch.ru`
`thc.ru`
`htc.eu`
`cht.ir`
`thc.fr`
`hct.ca`
`cth.dz`
`thc.nl`
`htc.agency`
`cht.net.br`
`htc.om`
`tch.ua`
`htc.nyc`
`cht.com.br`
`cth.synology.me`
`tch.be`
`cth.nl`
`htc.hatenablog.com`
`cht.life`
`cht.sh`
`htc.tc`
`thc.hk`
`thc.cheap`
`tch.or.jp`
`htc.co.nz`
`htc.us`
`cth.ru`
`hct.ru`
`htc.be`
`cth.com.ec`
`hct.im`
`thc.cash`
`tch.edgekey.net`
`htc.es`
`htc.ag`
`tch.ca`
`cht.com.uy`
`thc.center`
`htc.de`
`tch.biz`
`thc.today`
`hct.edu.vn`
`thc.guide`
`cth.co.nz`
`cht.jp`
`htc.lu`
`htc.inf.br`
`cth.pl`
`tch.kiev.ua`
`htc.se`
`cth.co.za`
`htc.net.cn`
`hct.lu`
`thc.com.my`
`hct.tw`
`tch.ae`
`hct.be`
`thc.or.jp`
`thc.blue`
`thc.la`

AI analysis

tch.to is configured to point to the following four IP addresses: 2600:1f18:16e:df01::258, 2600:1f18:16e:df01::259, 18.208.88.157, and 98.84.224.111.

IP numbers are shared between tch.to and other host names, such as shuochao.net, nempo.be, awax-demo.netlify.com, 1da.co, and bandjoo.com.

Four name servers, dns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net, and dns4.p01.nsone.net, have been delegated to tch.to.

The domain tch.to shares name servers, at least partially, with other domains such as amberelise.com, debrabryson.com, brennanspub.com, e2ac.com, and abiomed.eu.

The name servers ns01.squarespacedns.com, ns02.squarespacedns.com, ns03.squarespacedns.com, ns04.squarespacedns.com, ns01.jnjdns.com, ns02.jnjdns.com, ns03.jnjdns.com, ns04.jnjdns.com, ns01.kenvuedns.com, and ns02.kenvuedns.com are commonly used together.

dns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net, and dns4.p01.nsone.net all point to two IP numbers each: 2620:4d:4000:6259:7:1:0:1 and 198.51.44.1; 2a00:edc0:6259:7:1::2 and 198.51.45.1; 2620:4d:4000:6259:7:1:0:3 and 198.51.44.65; 2a00:edc0:6259:7:1::4 and 198.51.45.65, respectively.

The five mail servers, aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com, and alt4.aspmx.l.google.com, are responsible for handling tch.to.

Other domains like alfalazer.com.tr, marcellomorena.com, ramsay.cl, yasuda-u.ac.jp, and friendbasegames.com share some mail servers, at least partially, with tch.to.

The mail servers aspmx2.googlemail.com, aspmx3.googlemail.com, and 43k7zvsix6am23us3eihwk5fkxrixjgwqxigkfsww4tlqqhqldeq.mx-verification.google.com are commonly used in conjunction with these.

aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com, and alt4.aspmx.l.google.com each point to two IP numbers: 2607:f8b0:4004:c21::1b/172.253.122.27, 2a00:1450:400b:c02::1a/172.253.116.26, 2a00:1450:400c:c00::1a/173.194.76.26, 2a00:1450:4025:402::1a/142.250.102.26, and 2a00:1450:4013:c1c::1b/192.178.156.26 respectively.

dbq