CF1757133447446-tsm20250905231252

DNSWHOIS.INFO - n3.dns.ec

Search for IP or hostnames:

n3.dns.ec checked at 2025-09-06T04:37:27.431Z 51ms 30/30/30 100% R:9

`n3.dns.ec`

	A	2001:500:14:6039:ad::1 ^{🇺🇸 PCH AS42}
			PTR	`n3.dns.ec`
	A	204.61.216.39^{🇺🇸 PCH AS42}
			PTR	`n3.dns.ec`

`dns.ec`

	NS	`n3.dns.ec`
	NS	`n2.nic.ec`
	NS	`a.lactld.org`

PTR for
`39.216.61.204.in-addr.arpa`
`1.0.0.0.0.0.0.0.0.0.0.0.d.a.0.0.9.3.0.6.4.1.0.0.0.0.5.0.1.0.0.2.ip6.arpa`

NS for
`fin.ec`
`dns.ec`
`gov.ec`
`k12.ec`
`org.ec`
`196.12.200.in-addr.arpa`
`med.ec`
`edu.ec`
`gob.ec`
`nic.ec`
`ec`
`199.12.200.in-addr.arpa`
`pro.ec`
`pub.ec`
`198.12.200.in-addr.arpa`
`info.ec`
`net.ec`
`mil.ec`
`com.ec`

Starts with same word
`n3.pl`
`n3.se`
`n3.com.tw`
`n3.net.ua`
`n3.fi`
`n3.vc`
`n3.to`
`n3.org`
`n3.group`
`n3.nl`
`n3.de`
`n3.hu`
`n3.nhs.uk`
`n3.media`
`n3.ru`
`n3.be`
`n3.at`
`n3.net`
`n3.ca`
`n3.com.br`
`n3.com.mx`
`n3.com.au`
`n3.com`
`n3.app`
`n3.co.nz`
`n3.com.ua`
`n3.services`
`n3.tv`
`n3.fr`
`n3.com.cn`
`n3.eu`
`n3.nu`
`n3.by`

Starts similarily
`3n.com.mx`
`n3.co.nz`
`n3.com.ua`
`n3.services`
`n3.tv`
`n3.fr`
`n3.com.cn`
`n3.eu`
`3n.cc`
`3n.cz`
`n3.nu`
`3n.se`
`n3.by`
`n3.pl`
`n3.se`
`n3.com.tw`
`3n.org`
`3n.no`
`n3.net.ua`
`n3.fi`
`3n.dk`
`3n.hk`
`n3.vc`
`n3.to`
`n3.org`
`3n.com.vn`
`3n.ca`
`3n.nl`
`3n.com`
`n3.group`
`3n.com.pl`
`3n.de`
`n3.nl`
`n3.de`
`n3.hu`
`n3.nhs.uk`
`3n.is`
`n3.media`
`3n.pl`
`n3.ru`
`3n.nz`
`n3.be`
`n3.at`
`n3.net`
`n3.ca`
`3n.fi`
`3n.net`
`n3.com.br`
`n3.com.mx`
`n3.com.au`
`n3.com`
`n3.app`
`3n.fr`
`3n.cn`

AI analysis

The name server for domains fin.ec, dns.ec, gov.ec, k12.ec, org.ec, among others, is n3.dns.ec.

Together with n3.dns.ec, n2.nic.ec, a.lactld.org, and ns1.anycastdns.cz are frequently utilized as a name server.

n3.dns.ec is configured to point to two IP addresses, namely 2001:500:14:6039:ad::1 and 204.61.216.39.

dbq

GUbhJqF CF johedugfp 2025-09-06