Hostname
bbva.com.pe
Last fetched
bbva.com.pe resolves to 2.23.244.156, announced in 2.23.244.0/22 by AKAMAI-AS - Akamai Technologies, Inc. in DE. bbva.com.pe is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 2.23.244.156
2.23.244.0/22 · AKAMAI-AS - Akamai Technologies, Inc. · Frankfurt am Main, DE
- 23.197.45.191
23.197.44.0/22 · AKAMAI-AS - Akamai Technologies, Inc. · Edison, US
- 23.215.172.148
23.215.172.0/22 · AKAMAI-AS - Akamai Technologies, Inc. · Santiago, CL
- 23.58.108.153
23.32.0.0/11 · AKAMAI-ASN1 - Akamai International B.V. · Frankfurt am Main, DE
- 23.75.64.148
23.75.64.0/22 · AKAMAI-AS - Akamai Technologies, Inc. · Prague, CZ
IPv6 resolution
No AAAA record for bbva.com.pe is recorded in WhisperGraph.
Attribution
akamai
ORIGIN_AS
WHOIS identity
- Registrar
- registrar:neudomains digital s.l.
- Registrant organisation
- banco bilbao vizcaya argentaria,
- Contact emails
- gestion.dominios@bbva.com
Subdomains
Mail and authentication
Nameservers
- ns1.bbvaedge.com
- ns2.bbvaedge.com
- a1-166.akam.net
- a22-65.akam.net
- a3-66.akam.net
- a4-67.akam.net
- a6-64.akam.net
- a7-65.akam.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
SPF policy
- ip: 85.115.32.0/19
- ip: 192.151.176.0/20
- ip: 86.111.216.0/21
- ip: 208.87.232.0/21
- ip: 116.50.56.0/21
- ip: 103.1.196.0/22
- ip: 86.111.220.0/22
- ip: 177.39.96.0/22
- ip: 196.216.238.0/23
- ip: 168.195.58.192/26
- include: spf.mailjet.com
Threat-feed evidence
History
Related pages
Pivot from bbva.com.pe 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: "bbva.com.pe"})-[: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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.