DNSWHOIS.INFO - 33.35.200.in-addr.arpa

Search for IP or hostnames:

33.35.200.in-addr.arpa checked at 2025-09-06T20:04:42.934Z 694ms 36/36/36 100% R:19

`33.35.200.in-addr.arpa`

NS	`dns1.edatel.net.co`
		A	200.35.33.3^{🇨🇴 AS27695}
			PTR	`dns1.edatel.net.co`
NS	`dns2.edatel.net.co`
		A	200.35.33.4^{🇨🇴 AS27695}
			PTR	`dns2.edatel.net.co`

`35.200.in-addr.arpa`

Up
`58.33.35.200.in-addr.arpa`
`3.33.35.200.in-addr.arpa`
`60.33.35.200.in-addr.arpa`
`4.33.35.200.in-addr.arpa`
`9.33.35.200.in-addr.arpa`

Starts with same word
`33.com`
`33.ddns.net`
`33.net.au`
`33.tt`
`33.co.za`
`33.do`
`33.com.ua`
`33.be`
`33.se`
`33.ms`
`33.uy`
`33.in-addr.arpa`
`33.com.cn`
`33.eu`
`33.vg`
`33.tn`
`33.cl`
`33.pl`
`33.company`
`33.poznan.pl`
`33.at`
`33.dk`
`33.ro`
`33.cc`
`33.sk`
`33.is`
`33.my`
`33.design`
`33.lv`
`33.ee`
`33.su`
`33.cool`
`33.cz`
`33.com.bh`
`33.ru`
`33.ly`
`33.co.nz`
`33.cn`
`33.wtf`
`33.ca`
`33.co.uk`
`33.rs`
`33.life`

Starts similarily
`33.ly`
`33.co.nz`
`33.cn`
`33.wtf`
`33.ca`
`33.co.uk`
`33.rs`
`33.life`
`33.com`
`33.ddns.net`
`33.net.au`
`33.tt`
`33.co.za`
`33.do`
`33.com.ua`
`33.be`
`33.se`
`33.ms`
`33.uy`
`33.in-addr.arpa`
`33.com.cn`
`33.eu`
`33.vg`
`33.tn`
`33.cl`
`33.pl`
`33.company`
`33.poznan.pl`
`33.at`
`33.dk`
`33.ro`
`33.cc`
`33.sk`
`33.is`
`33.my`
`33.design`
`33.lv`
`33.ee`
`33.su`
`33.cool`
`33.cz`
`33.com.bh`
`33.ru`

AI analysis

The parent of 58.33.35.200.in-addr.arpa, 3.33.35.200.in-addr.arpa, 60.33.35.200.in-addr.arpa, 4.33.35.200.in-addr.arpa, and 9.33.35.200.in-addr.arpa is 33.35.200.in-addr.arpa.

Two name servers, dns1.edatel.net.co and dns2.edatel.net.co, have been delegated to 33.35.200.in-addr.arpa.

The name server setup of 33.35.200.in-addr.arpa is identical to that of other domains such as 40.43.186.in-addr.arpa, 35.35.200.in-addr.arpa, 193.3.190.in-addr.arpa, 44.35.200.in-addr.arpa, and 36.35.200.in-addr.arpa.

dns1.edatel.net.co and dns2.edatel.net.co both point to different IP numbers. 200.35.33.3 and 200.35.33.4 respectively.

dbq