Skip to content

Hostname

elon.no

Last fetched

elon.no resolves to 104.17.67.120, announced in 104.17.64.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. elon.no 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 · elon.noRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.6/10canon.whisper.security/host/elon.no

Resolution chain

IPv6 resolution

No AAAA record for elon.no is recorded in WhisperGraph.

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for elon.no. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

Subdomains

Subdomain
butikker.elon.no
collect.elon.no
kundeavis.elon.no
kundeklubb.elon.no
tipsograad.elon.no
to.elon.no
www.elon.no

Showing 7 of 7 subdomains (7 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

Mail and authentication

Nameservers

  • dns01.dipcon.com
  • dns04.ports.net
  • dns02.ports.se
  • dns03.ports.se

MX records

  • elon-no.mail.protection.outlook.com

SPF policy

  • include: amazonses.com
  • include: spf.protection.outlook.com
  • include: _spf.vaimo.net
  • include: _spf.bleken.no
  • a: elon.no
  • mx: elon.no
  • include: spf.nisecasp.no
  • include: eu.mailgun.org
  • ip: 52.211.201.244

Threat-feed evidence

History

Related pages

Pivot from elon.no 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: "elon.no"})-[: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.