Skip to content

Hostname

commstbk.com

Last fetched

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

Resolution chain

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:299
Registrant organisation
community state bank of rock falls
Contact emails
admin@internationaladmin.com, sally.scanlan@commstbk.com

Subdomains

Showing 3 of 3 subdomains (3 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.

Mail and authentication

Nameservers

  • ns-509.awsdns-63.com
  • ns-658.awsdns-18.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
  • ns-1186.awsdns-20.org
  • ns-1800.awsdns-33.co.uk

MX records

  • mx1-us1.ppe-hosted.com
  • mx2-us1.ppe-hosted.com

SPF policy

  • ip: 207.67.42.11/32
  • ip: 173.84.2.228/32
  • ip: 66.254.204.7/32
  • include: amazonses.com
  • include: spf.cashedge.com
  • a: commstbk.com
  • mx: commstbk.com
  • a: monitor.ensenta.com
  • include: gateways.firstdata.com
  • include: spfref.jackhenry.com
  • include: spf.protection.outlook.com
  • a: dispatch-us.ppe-hosted.com
  • include: commstbk-com.spf.smtp25.com

Threat-feed evidence

History

Related pages

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