Skip to content

Hostname

openbank.com

Last fetched

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

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:69
Registrant organisation
security first technologies
Contact emails
infrastructureservices@aciworldwide.com

Subdomains

Subdomain
aciaodmail.openbank.com
api.openbank.com
bcdn.openbank.com
brand.openbank.com
email.openbank.com
even.openbank.com
form.openbank.com
info.openbank.com
logs.openbank.com
news.openbank.com
ns1.openbank.com
ns2.openbank.com

Showing 12 of 32. 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

  • ns-473.awsdns-59.com
  • ns-632.awsdns-15.net
  • ns-1436.awsdns-51.org
  • ns-1988.awsdns-56.co.uk

MX records

  • mx1.santandergroup.c3s2.iphmx.com
  • mx2.santandergroup.c3s2.iphmx.com
  • mx1.hc5532-55.iphmx.com
  • mx2.hc5532-55.iphmx.com

SPF policy

  • ip: 195.149.208.0/21
  • exists: %{i}.spf.santandergroup.c3s2.iphmx.com
  • exists: %{i}.spf.santandergroup-out.c3s2.iphmx.com
  • exists: %{i}.spf.hc5532-55.iphmx.com
  • include: santandergroup.net
  • ip: 194.224.110.206

Threat-feed evidence

History

Related pages

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