Skip to content

Hostname

heycolleagues.com

Last fetched

heycolleagues.com resolves to 172.234.24.211, announced in 172.234.16.0/20 by AKAMAI-LINODE-AP - Akamai Connected Cloud in US. heycolleagues.com 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 · heycolleagues.comRouting diversity2.4/10Peering density6.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint5.6/10canon.whisper.security/host/heycolleagues.com

Resolution chain

IPv6 resolution

No AAAA record for heycolleagues.com is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:1068
Registrant organisation
privacy service provided by withheld for privacy ehf
Contact emails
2bf444a376e5400bbdc182a51b57432c.protect@withheldforprivacy.com

Subdomains

Subdomain
belo4d.heycolleagues.com
caprover.heycolleagues.com
dev.heycolleagues.com
mail.heycolleagues.com
news.heycolleagues.com
node-server.heycolleagues.com
server.heycolleagues.com
wiki.heycolleagues.com
www.heycolleagues.com

Showing 9 of 9 subdomains (9 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.dizoolexa.com
  • ns2.dizoolexa.com
  • dns1.registrar-servers.com
  • dns101.registrar-servers.com
  • dns102.registrar-servers.com
  • dns2.registrar-servers.com

MX records

  • mail.heycolleagues.com
  • mx.plingest.com

SPF policy

  • a: heycolleagues.com
  • mx: heycolleagues.com
  • ip: 194.238.19.121

Threat-feed evidence

History

Related pages

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