Hostname
b2blatam.com
Last fetched
b2blatam.com resolves to 108.156.85.20, announced in 108.156.84.0/23 by AMAZON-02 - Amazon.com, Inc. in US. b2blatam.com 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
- 108.156.85.20
108.156.84.0/23 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 108.156.85.48
108.156.84.0/23 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 108.156.85.74
108.156.84.0/23 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 108.156.85.87
108.156.84.0/23 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 18.238.49.117
18.238.48.0/22 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 18.238.49.55
18.238.48.0/22 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 18.238.49.8
18.238.48.0/22 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 18.238.49.81
18.238.48.0/22 · AMAZON-02 - Amazon.com, Inc. · New York, US
IPv6 resolution
No AAAA record for b2blatam.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:440
- Registrant organisation
- baltea sas
- Contact emails
- marco@astonelatino.com
Subdomains
Showing 4 of 4 subdomains (4 per page).
Mail and authentication
Nameservers
- ns-110.awsdns-13.com
- ns-826.awsdns-39.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-1341.awsdns-39.org
- ns-1722.awsdns-23.co.uk
MX records
- b2blatam-com.mail.protection.outlook.com
SPF policy
- include: spf.mandrillapp.com
- include: spf.protection.outlook.com
- include: _spf.qp-mail.com
- include: zoho.com
- include: 20124867.spf08.hubspotemail.net
- include: zcsend.net
Threat-feed evidence
History
Related pages
Pivot from b2blatam.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: "b2blatam.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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.