zerocap.io checked at 2025-02-06T10:44:41.808Z 1162ms 161/161/161 100% R:28
DNSTREE.COM - zerocap.io
Search for IP or hostnames
zerocap.io
io
NS | a0.nic.io | ||||||
NS | a2.nic.io | ||||||
NS | b0.nic.io | ||||||
NS | c0.nic.io |
0 | |
0 | |
0 | |
0 | |
0 | |
2 | |
(lm) | zerocap.com |
(lm) | zerocap.io |
16 | |
(le) | paczero.com |
(le) | precoza.fr |
(le) | azecorp.com |
(le) | zerocap.com |
(le) | precoza.be |
(le) | aprezco.com |
(le) | zerocap.io |
(le) | proceza.com |
(le) | precoza.org |
(le) | pozcare.com |
(le) | precoza.biz |
(le) | proceza.com.mx |
(le) | corezap.com |
(le) | precoza.com |
(le) | operacz.com |
(le) | operacz.net |
AI analysis
There are two IP numbers that zerocap.io points to: 141.193.213.20 and 141.193.213.21.
IP numbers are shared between zerocap.io and other host names such as meltatl.com, broad-path.com, www.stack.com, nwlabs.com, and lcfasd.com.
Two name servers, barbara.ns.cloudflare.com and quinton.ns.cloudflare.com, have been delegated for zerocap.io.
The name server setup for zerocap.io is shared with other domains, such as zerocap.com.
The name servers of zerocap.io are at least partially shared with other domains such as n71.ru, ariakababmenu.com, trivenix.com, justyellowpage.com, and aymedilac.com.
The name servers rodney.ns.cloudflare.com, zainab.ns.cloudflare.com, nelci.ns.cloudflare.com, surina.ns.cloudflare.com, ivan.ns.cloudflare.com, dan.ns.cloudflare.com, guss.ns.cloudflare.com, jeff.ns.cloudflare.com, clyde.ns.cloudflare.com, and luke.ns.cloudflare.com are commonly used in conjunction.
barbara.ns.cloudflare.com and quinton.ns.cloudflare.com each point to six IP numbers: 2606:4700:50::adf5:3af8, 2803:f800:50::6ca2:c0f8, 2a06:98c1:50::ac40:20f8, 108.162.192.248, 172.64.32.248, and 173.245.58.248 for barbara.ns.cloudflare.com, and 2606:4700:58::a29f:2cf9, 2803:f800:50::6ca2:c3f9, 2a06:98c1:50::ac40:23f9, 108.162.195.249, 162.159.44.249, and 172.64.35.249 for quinton.ns.cloudflare.com.
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 zerocap.io.
Just like domains such as ns500734.ns500693.ns500699.ns500699.ns500693.ns500734.ns500693.ns500699.ns500683.ns500683.ns500612.ns500612.ns500110.dtrkdll.com, ns500693.ns500734.ns500734.ns500734.ns500734.ns500699.ns500699.ns500734.ns500693.ns500588.ns500693.ns500699.ns500588.ns500632.ns500588.ns500588.ns500588.dtrkdll.com, ns500698.ns500758.ns500758.ns500759.ns500698.ns500698.ns500735.ns500735.ns500736.ns500735.ns500708.ns500708.ns500686.ns500652.ns500576.trackreceptor.com, ns500768.ns500758.ns500759.ns500698.ns500758.ns500736.ns500736.ns500698.ns500736.ns500735.ns500708.ns500708.ns500708.trackreceptor.com, and ns500754.ns500731.ns500731.ns500731.ns500671.ns500705.ns500678.ns500649.ns500653.ns500131.lustychickser.com, zerocap.io also shares the same mail server setup.
Some mail servers are at least partially shared by zerocap.io with other domains such as servvo.com, ccp.com.br, and sekis.co.uk.
The mail servers aspmx2.googlemail.com and aspmx3.googlemail.com are frequently used in conjunction with these mail servers.
aspmx.l.google.com, 2a00:1450:400c:c06::1a, and 64.233.166.26 are related.
alt1.aspmx.l.google.com, 2a00:1450:4013:c16::1a, and 142.250.153.26 are connected.
alt2.aspmx.l.google.com, 2a00:1450:4025:c03::1a, and 142.251.9.27 are associated.
alt3.aspmx.l.google.com, 2a00:1450:4010:c1c::1b, and 142.250.150.27 are linked.
alt4.aspmx.l.google.com, 2404:6800:4003:c00::1a, and 74.125.200.27 are correlated.