Skip to content

Hostname

cryptojunkie.net

Last fetched

cryptojunkie.net resolves to 162.0.217.103, announced in 162.0.217.0/24 by NAMECHEAP-NET - Namecheap, Inc. in NL. cryptojunkie.net 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 · cryptojunkie.netRouting diversity2.4/10Peering density4.6/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/cryptojunkie.net

Resolution chain

IPv6 resolution

Attribution

namecheap net

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrar
iana:1647
Registrant organisation
anton antokhin
Contact emails
antokhin.anton@gmail.com, domains@55domains.com

Subdomains

Subdomain
cpanel.cryptojunkie.net
cpcalendars.cryptojunkie.net
cpcontacts.cryptojunkie.net
mail.cryptojunkie.net
webdisk.cryptojunkie.net
webmail.cryptojunkie.net
www.cryptojunkie.net

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

Sample outbound links

Mail and authentication

Nameservers

  • dns1.namecheaphosting.com
  • dns2.namecheaphosting.com
  • ns1.siteguarding.com
  • ns2.siteguarding.com

MX records

  • mx1.hostinger.com
  • mx2.hostinger.com
  • cryptojunkie.net

SPF policy

  • include: spf.web-hosting.com
  • a: cryptojunkie.net
  • mx: cryptojunkie.net
  • include: spf.greengeeks.net
  • ip: 107.6.151.38
  • ip: 107.6.184.242
  • ip: 162.0.217.183
  • ip: 162.0.217.71

Threat-feed evidence

History

Related pages

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