Skip to content

Hostname

carisma.net

Last fetched

carisma.net resolves to 76.9.245.203, announced in 76.9.240.0/20 by COHO-ASN - Whiz to Coho, Inc. in US. carisma.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 · carisma.netRouting diversity1.5/10Peering density2.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/carisma.net

Resolution chain

IPv6 resolution

No AAAA record for carisma.net is recorded in WhisperGraph.

Attribution

whiz to coho

ORIGIN_AS

WHOIS identity

Registrar
iana:146
Registrant organisation
carisma
Contact emails
fricciardi@carisma.net, support@carisma.net

Subdomains

Subdomain
admin.carisma.net
carisma.carisma.net
mail.carisma.net
ns1.carisma.net
ns2.carisma.net
ns3.carisma.net
remote.carisma.net
smtp.carisma.net
solutions.carisma.net
status.carisma.net
support.carisma.net
www.carisma.net

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

  • ns1.carisma.net
  • ns2.carisma.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

  • carisma-net.inbound.emailservice.cc
  • carisma-net.inbound.emailservice.co
  • carisma-net.inbound.emailservice.io

SPF policy

  • include: amazonses.com
  • include: spf.us.emailservice.io
  • a: carisma.net
  • mx: carisma.net

Threat-feed evidence

History

Related pages

Pivot from carisma.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: "carisma.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.