Skip to content

Hostname

projectcube.tech

Last fetched

projectcube.tech resolves to 109.120.137.79, announced in 109.120.137.0/24 by H2NEXUS-AS - H2NEXUS CLOUD SERVICES - FZCO in DE. projectcube.tech 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 · projectcube.techRouting diversity1.5/10Peering density5.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint8.3/10canon.whisper.security/host/projectcube.tech

Resolution chain

IPv6 resolution

No AAAA record for projectcube.tech is recorded in WhisperGraph.

Attribution

h2nexus fzco

ORIGIN_AS

WHOIS identity

Registrar
iana:1606
Registrant organisation
private person

Subdomains

Subdomain
code10.projectcube.tech
friday13th.projectcube.tech
nl.projectcube.tech
node.projectcube.tech
panel.projectcube.tech
webhook.projectcube.tech
wiki.projectcube.tech

Showing 7 of 7 subdomains (7 per page).

Mail and authentication

Nameservers

  • elma.ns.cloudflare.com
  • gordon.ns.cloudflare.com
  • hattie.ns.cloudflare.com
  • patryk.ns.cloudflare.com
  • 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

  • mx1.hosting.reg.ru
  • mx2.hosting.reg.ru

SPF policy

  • include: _spf.hosting.reg.ru
  • a: projectcube.tech
  • mx: projectcube.tech
  • ip: 37.140.192.183

Threat-feed evidence

History

Related pages

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