Skip to content

Hostname

e-nemo.nl

Last fetched

e-nemo.nl is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. e-nemo.nl 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 · e-nemo.nlRouting diversity0.0/10Peering density0.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.2/10canon.whisper.security/host/e-nemo.nl

Resolution chain

No IPv4 resolution is recorded for e-nemo.nl in WhisperGraph.

IPv6 resolution

No AAAA record for e-nemo.nl is recorded in WhisperGraph.

WHOIS identity

Registrar
registrar:team.blue nl b.v.

Subdomains

Subdomain
api.e-nemo.nl
apitest.e-nemo.nl
firewall01.e-nemo.nl
kantoor.e-nemo.nl
mail.e-nemo.nl
print.e-nemo.nl
prtg.e-nemo.nl
ras.e-nemo.nl
vpn.e-nemo.nl
webmail.e-nemo.nl
www.e-nemo.nl

Showing 11 of 11 subdomains (11 per page).

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

  • ns2.transip.eu
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • d.root-servers.net
  • e.root-servers.net
  • f.root-servers.net
  • g.root-servers.net
  • h.root-servers.net
  • i.root-servers.net
  • j.root-servers.net
  • k.root-servers.net
  • l.root-servers.net
  • m.root-servers.net
  • ns0.transip.net
  • ns1.transip.nl

MX records

  • enemo-nl0c.mail.protection.outlook.com

SPF policy

  • ip: 145.102.247.16/29
  • include: spf.protection.outlook.com
  • include: _spf.exsilia.net
  • include: sendgrid.net
  • a: e-nemo.nl
  • mx: e-nemo.nl
  • include: mailgun.org
  • ip: 178.79.171.92
  • ip: 2a00:1e28:3:3494:0:0:0:1

Threat-feed evidence

History

Related pages

Pivot from e-nemo.nl 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: "e-nemo.nl"})-[: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.