Skip to content

Hostname

hitcom.pro

Last fetched

hitcom.pro resolves to 185.215.4.26, announced in 185.215.4.0/24 by DDOS-GUARD - DDOS-GUARD LTD in RU. hitcom.pro 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 · hitcom.proRouting diversity2.4/10Peering density8.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint3.2/10canon.whisper.security/host/hitcom.pro

Resolution chain

IPv6 resolution

No AAAA record for hitcom.pro is recorded in WhisperGraph.

Attribution

ddos guard

ORIGIN_AS

WHOIS identity

Registrar
iana:1606
Registrant organisation
hitcom
Contact emails
bvv@hitcom.pro

Subdomains

Subdomain
1c.hitcom.pro
1s-cs.hitcom.pro
appcloud.hitcom.pro
cn.hitcom.pro
edu.hitcom.pro
files.hitcom.pro
mail.hitcom.pro
mail2.hitcom.pro
nc.hitcom.pro
www.hitcom.pro
zmail.hitcom.pro

Showing 11 of 12. View all subdomains →

Mail and authentication

Nameservers

  • ns1.reg.ru
  • ns2.reg.ru

MX records

  • mail.hitcom.pro
  • mail2.hitcom.pro

SPF policy

  • a: mail.hitcom.pro

Threat-feed evidence

History

Related pages

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