Skip to content

Hostname

sackstark.com

Last fetched

sackstark.com resolves to 3.141.188.206, announced in 3.136.0.0/13 by AMAZON-02 - Amazon.com, Inc. in US. sackstark.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 · sackstark.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/sackstark.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:1861
Registrant organisation
mark loo
Contact emails
watchout@gmx.ch

Subdomains

Subdomain
cpanel.sackstark.com
cpcalendars.sackstark.com
cpcontacts.sackstark.com
mail.sackstark.com
webdisk.sackstark.com
webmail.sackstark.com
www.sackstark.com

Showing 7 of 7 subdomains (7 per page).

Mail and authentication

Nameservers

  • ns75.rochenhost.com
  • ns76.rochenhost.com
  • ns1.rochendns.net
  • ns2.rochendns.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

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com
  • aspmx4.googlemail.com
  • aspmx5.googlemail.com

SPF policy

  • include: _spf.google.com
  • include: aspmx.googlemail.com
  • include: netvigator.com
  • a: sackstark.com
  • mx: sackstark.com
  • include: relay.mailchannels.net
  • ip: 72.249.107.2
  • ip: 72.249.107.80
  • ip: 72.249.98.80

Threat-feed evidence

History

Related pages

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