Skip to content

Hostname

collaboromarketing.com

Last fetched

collaboromarketing.com resolves to 34.41.139.193, announced in 34.41.0.0/16 by GOOGLE-CLOUD-PLATFORM - Google LLC in US. collaboromarketing.com is listed by 1 threat feed; reconciled level HIGH.

Threat posture

40threat score (procedure-native scale)

HIGH

Listed by 1 threat feed. At least one source recommends blocking.

Categories: Phishing

Threat feeds listing this
1
Verdict coverage
malicious-evidenced
First seen on a feed
Wed, 26 Aug 2026 14:45:24 GMT
Last seen on a feed
Tue, 22 Sep 2026 19:47:37 GMT

Nutrition Label

WHISPER CANON · collaboromarketing.comRouting diversity1.5/10Peering density2.4/10MOAS conflict✓ noneThreat-feed listings8.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/collaboromarketing.com

Resolution chain

IPv6 resolution

Attribution

Google

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:472
Registrant organisation
corene newbery
Contact emails
reg_20639274@whoisprotection.cc, corenee@gmail.com, a51fa6a6b305493caffd045ecc6eb08e.protect@withheldforprivacy.com, reactivation-pending@mail.withheldforprivacy.com

Subdomains

Subdomain
apps.collaboromarketing.com
cpanel.collaboromarketing.com
hostmaster.collaboromarketing.com
m.collaboromarketing.com
webdisk.collaboromarketing.com
www.collaboromarketing.com

Showing 6 of 6 subdomains (6 per page).

Mail and authentication

Nameservers

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

  • mx1.csof.net
  • mx2.csof.net

SPF policy

  • include: _incspfcheck.mailspike.net

Threat-feed evidence

History

Related pages

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