Hostname
peibo.mx
Last fetched
peibo.mx resolves to 100.27.149.35, announced in 100.24.0.0/13 by AMAZON-AES - Amazon.com, Inc. in US. peibo.mx 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
- 100.27.149.35
100.24.0.0/13 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 18.204.45.249
18.204.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 3.215.225.86
3.208.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 34.235.183.6
34.224.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 34.235.245.244
34.224.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 44.195.142.158
44.192.0.0/11 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 44.206.55.63
44.192.0.0/11 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 44.211.15.75
44.192.0.0/11 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 52.73.159.214
52.72.0.0/15 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 52.73.163.151
52.72.0.0/15 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 54.87.83.184
54.87.0.0/16 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 98.95.192.144
98.88.0.0/13 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 3.215.60.132
- 32.199.50.29
IPv6 resolution
No AAAA record for peibo.mx is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for peibo.mx. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.
Subdomains
Mail and authentication
Nameservers
- ns-86.awsdns-10.com
- ns-831.awsdns-39.net
- ns-1071.awsdns-05.org
- ns-1943.awsdns-50.co.uk
MX records
- peibo-mx.mail.protection.outlook.com
SPF policy
- include: spf.protection.outlook.com
Threat-feed evidence
History
Related pages
Pivot from peibo.mx 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: "peibo.mx"})-[: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.