Skip to content

Hostname

jlcommerce.fi

Last fetched

jlcommerce.fi resolves to 104.21.47.9, announced in 104.21.32.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. jlcommerce.fi 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 · jlcommerce.fiRouting diversity2.4/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.5/10canon.whisper.security/host/jlcommerce.fi

Resolution chain

IPv6 resolution

Attribution

ovh

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for jlcommerce.fi. 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

Web-graph footprint

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

Mail and authentication

Nameservers

  • adele.ns.cloudflare.com
  • derek.ns.cloudflare.com
  • ns208-1.netfinn.net
  • ns411-1.netfinn.net
  • ns411-2.netfinn.net
  • 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

MX records

  • jlcommerce.fi
  • _dc-mx.347c87b00b2d.jlcommerce.fi

SPF policy

  • a: jlcommerce.fi
  • mx: jlcommerce.fi
  • include: _spf411.netfinn.net
  • ip: 135.125.7.9
  • ip: 151.80.103.109
  • ip: 188.165.138.182
  • ip: 192.163.216.113
  • ip: 5.135.60.106
  • ip: 50.116.71.212
  • ip: 51.255.103.183
  • ip: 51.91.48.26

Threat-feed evidence

History

Related pages

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