Hostname
whatspos.com
Last fetched
whatspos.com resolves to 13.227.192.106, announced in 13.227.192.0/24 by AMAZON-02 - Amazon.com, Inc. in CZ. whatspos.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
- 13.227.192.106
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.53
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.73
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.97
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.32.220.110
13.32.216.0/21 · AMAZON-02 - Amazon.com, Inc. · Milan, IT
- 13.32.220.16
13.32.216.0/21 · AMAZON-02 - Amazon.com, Inc. · Milan, IT
- 13.32.220.52
13.32.216.0/21 · AMAZON-02 - Amazon.com, Inc. · Milan, IT
- 13.32.220.80
13.32.216.0/21 · AMAZON-02 - Amazon.com, Inc. · Milan, IT
- 3.161.82.11
3.161.80.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.161.82.111
3.161.80.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.161.82.115
3.161.80.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.161.82.122
3.161.80.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
IPv6 resolution
No AAAA record for whatspos.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:420
- Registrant organisation
- pax technology
- Contact emails
- pengxh@paxsz.com, pxh_kevin@yahoo.com
Subdomains
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-243.awsdns-30.com
- ns-641.awsdns-16.net
- ns-1237.awsdns-26.org
- ns-2044.awsdns-63.co.uk
MX records
- inbound-smtp.us-west-2.amazonaws.com
SPF policy
- include: amazonses.com
Threat-feed evidence
History
Related pages
Pivot from whatspos.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: "whatspos.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.