Hostname
beta.pressmind.io
Last fetched
beta.pressmind.io resolves to 18.155.173.103, announced in 18.155.168.0/21 by AMAZON-02 - Amazon.com, Inc. in US. beta.pressmind.io 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
- 18.155.173.103
18.155.168.0/21 · AMAZON-02 - Amazon.com, Inc. · San Jose, US
- 18.155.173.123
18.155.168.0/21 · AMAZON-02 - Amazon.com, Inc. · San Jose, US
- 18.155.173.57
18.155.168.0/21 · AMAZON-02 - Amazon.com, Inc. · San Jose, US
- 18.155.173.80
18.155.168.0/21 · AMAZON-02 - Amazon.com, Inc. · San Jose, US
- 65.8.180.129
65.8.176.0/21 · AMAZON-02 - Amazon.com, Inc. · San Francisco, US
- 65.8.180.53
65.8.176.0/21 · AMAZON-02 - Amazon.com, Inc. · San Francisco, US
- 65.8.180.8
65.8.176.0/21 · AMAZON-02 - Amazon.com, Inc. · San Francisco, US
- 65.8.180.81
65.8.176.0/21 · AMAZON-02 - Amazon.com, Inc. · San Francisco, US
IPv6 resolution
No AAAA record for beta.pressmind.io is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for beta.pressmind.io. 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.
Mail and authentication
Nameservers
- ns-153.awsdns-19.com
- ns-704.awsdns-24.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-1435.awsdns-51.org
- ns-1737.awsdns-25.co.uk
Threat-feed evidence
History
Related pages
Pivot from beta.pressmind.io 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: "beta.pressmind.io"})-[: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.