Skip to content

Hostname

api.jeetbot.cc

Last fetched

api.jeetbot.cc resolves to 152.53.177.186, announced in 152.53.176.0/22 by netcup-AS - netcup GmbH in DE. api.jeetbot.cc is listed by 2 threat feeds; reconciled level HIGH.

Threat posture

40threat score (procedure-native scale)

HIGH

Listed by 2 threat feeds. At least one source recommends blocking.

Categories: Command-and-control

Threat feeds listing this
2
Verdict coverage
malicious-evidenced
First seen on a feed
Tue, 15 Sep 2026 07:25:36 GMT
Last seen on a feed
Tue, 22 Sep 2026 23:26:40 GMT

Nutrition Label

WHISPER CANON · api.jeetbot.ccRouting diversity3.0/10Peering density1.2/10MOAS conflict⚠ 1 conflictThreat-feed listings6.8/10WHOIS transparency0.0/10Resolver footprint4.6/10canon.whisper.security/host/api.jeetbot.cc

Resolution chain

IPv6 resolution

No AAAA record for api.jeetbot.cc is recorded in WhisperGraph.

Attribution

hetzner

ORIGIN_AS

WHOIS identity

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

Mail and authentication

Nameservers

  • gns21.cloudns.net
  • gns22.cloudns.net
  • gns23.cloudns.net
  • gns24.cloudns.net

Threat-feed evidence

History

Related pages

Pivot from api.jeetbot.cc 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: "api.jeetbot.cc"})-[: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.