zball.me checked at 2025-03-22T03:08:08.392Z 153ms 66/67/67 99% R:13DNS.NINJA - zball.me
Search for IP or hostnames
zball.me
| MX | mx.yandex.net | ||||||
| A | 2a02:6b8::311 🇷🇺 Yandex | ||||||
| PTR | mxfront.stable.qloud-b.yandex.net | ||||||
| A | 77.88.21.249🇷🇺 Teletech | ||||||
| PTR | mxfront.stable.qloud-b.yandex.net | ||||||
| NS | ns1.dobrovds.ru | ||||||
| A | 82.146.43.2🇷🇺 JSC IOT | ||||||
| PTR | ns1.firstvds.ru | ||||||
| NS | ns2.dobrovds.ru | ||||||
| A | 94.250.248.160🇷🇺 JSC IOT | ||||||
| PTR | ns2.firstvds.ru | ||||||
| A | 82.146.56.55🇷🇺 JSC IOT | ||||||
| PTR | rusconnect.ru | ||||||
me
| NS | a0.nic.me | ||||||
| NS | a2.nic.me | ||||||
| NS | b0.nic.me | ||||||
| NS | b2.nic.me | ||||||
| NS | c0.nic.me | ||||||
| 0 | ||||
| 0 | ||||
| 0 | ||||
| 0 | ||||
| 1 | ||||
| (u) | www.zball.me | |||
| 3 | ||||
| (lm) | zball.com | |||
| (lm) | zball.com.au | |||
| (lm) | zball.me | |||
| 11 | ||||
| (le) | ballz.co | |||
| (le) | zball.com | |||
| (le) | ballz.com | |||
| (le) | zball.com.au | |||
| (le) | zball.me | |||
| (le) | ballz.io | |||
| (le) | zllab.com.cn | |||
| (le) | bzall.com | |||
| (le) | allbz.com | |||
| (le) | ballz.de | |||
| (le) | lazlb.com | |||
AI analysis
The parent of www.zball.me is zball.me.
zball.me is associated with a single IP address: 82.146.56.55.
For example, other host names such as rusconnect.ru share IP numbers with zball.me.
Two name servers, ns1.dobrovds.ru and ns2.dobrovds.ru, are delegated to zball.me.
ns1.dobrovds.ru and ns2.dobrovds.ru both point to their respective IP numbers: 82.146.43.2 and 94.250.248.160.
The mail server, mx.yandex.net, manages zball.me.
Like domains prodiod.ru, kent-shop.com, klimaservishizmeti.com, zeta.az, and cms-moscow.ru, zball.me also has the same mail server setup.
Some mail servers are at least partially shared between zball.me and other domains, such as takikehribar.com, ujut-doma.com, w4d.net, griffelstudio.com, and 5a.ru.
mx.yandex.net points to two IP numbers: 2a02:6b8::311 and 77.88.21.249.
dbq