Skip to content

Hostname

hellosaks.com

Last fetched

hellosaks.com resolves to 104.21.74.239, announced in 104.21.64.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. hellosaks.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 · hellosaks.comRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency6.7/10Resolver footprint3.2/10canon.whisper.security/host/hellosaks.com

Resolution chain

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:146
Registrant organisation
domains by proxy,

Subdomains

Subdomain
app.hellosaks.com
conteudo.hellosaks.com
coolify.hellosaks.com
dynatech-old.hellosaks.com
dynatech.hellosaks.com
gate.hellosaks.com
help.hellosaks.com
homologblog.hellosaks.com
linked.hellosaks.com
linkstest.hellosaks.com
mail.hellosaks.com
partners.hellosaks.com

Showing 12 of 23. View all subdomains →

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

Mail and authentication

Nameservers

  • athena.ns.cloudflare.com
  • kirk.ns.cloudflare.com

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com
  • aspmx4.googlemail.com
  • aspmx5.googlemail.com
  • mail.hellosaks.com

SPF policy

  • include: spf.odin7080.com.br
  • include: amazonses.com
  • include: _spf.google.com
  • a: hellosaks.com
  • mx: hellosaks.com
  • include: mxsspf.sendpulse.com
  • include: mail.zendesk.com
  • include: one.zoho.com
  • include: spf.zoho.com
  • include: transmail.net
  • include: zcsend.net
  • ip: 177.154.191.218

Threat-feed evidence

History

Related pages

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