Skip to content

Hostname

nic.ec

Last fetched

nic.ec resolves to 107.154.155.107, announced in 107.154.155.0/24 by INCAPSULA - Incapsula Inc in US. nic.ec is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · nic.ecRouting diversity1.5/10Peering density9.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint6.9/10canon.whisper.security/host/nic.ec

Resolution chain

IPv6 resolution

No AAAA record for nic.ec is recorded in WhisperGraph.

Attribution

incapsula

ORIGIN_AS

WHOIS identity

Registrar
registrar:ec
Registrant organisation
local name: garry donoghue local organisation: nic.ec local address:
Contact emails
garry.donoghue@nic.ec, vabboud@nic.ec

Subdomains

Subdomain
automatizaciones.nic.ec
blog.nic.ec
dns1.nic.ec
dns2.nic.ec
dns3.nic.ec
dns4.nic.ec
dns41.nic.ec
dns42.nic.ec
dns43.nic.ec
dns44.nic.ec
freemail.nic.ec
mail.nic.ec

Showing 12 of 40. View all subdomains →

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Sample inbound links

Sample outbound links

Mail and authentication

Nameservers

  • ns1.anycastdns.cz
  • ns2.anycastdns.cz
  • n3.dns.ec
  • master.nic.ec
  • n2.nic.ec
  • dns41.cloudns.net
  • dns42.cloudns.net
  • dns43.cloudns.net
  • dns44.cloudns.net
  • a.lactld.org

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

SPF policy

  • include: _spf.google.com
  • include: spf.mailjet.com
  • include: spf.protection.outlook.com
  • include: one.zoho.com
  • a: nic.ec
  • mx: nic.ec
  • include: zcsend.net
  • ip: 141.95.1.185
  • ip: 200.12.196.2
  • ip: 200.12.197.40

Threat-feed evidence

History

Related pages

Pivot from nic.ec into the addresses, networks and registries it depends on.

Cypher and MCP

Reproduce this hostname's resolution chain against graph.whisper.security:

MATCH (h:HOSTNAME {name: "nic.ec"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.