Hostname
foleycs.com
Last fetched
foleycs.com resolves to 13.32.220.105, announced in 13.32.216.0/21 by AMAZON-02 - Amazon.com, Inc. in IT. foleycs.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.32.220.105
13.32.216.0/21 · AMAZON-02 - Amazon.com, Inc. · Milan, IT
- 13.32.220.29
13.32.216.0/21 · AMAZON-02 - Amazon.com, Inc. · Milan, IT
- 13.32.220.31
13.32.216.0/21 · AMAZON-02 - Amazon.com, Inc. · Milan, IT
- 13.32.220.89
13.32.216.0/21 · AMAZON-02 - Amazon.com, Inc. · Milan, IT
- 13.33.67.124
13.33.64.0/21 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 13.33.67.19
13.33.64.0/21 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 13.33.67.28
13.33.64.0/21 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 13.33.67.80
13.33.64.0/21 · AMAZON-02 - Amazon.com, Inc. · New York, US
IPv6 resolution
No AAAA record for foleycs.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:468
- Registrant organisation
- on behalf of foleycs.com owner
- Contact emails
- mike.every@foleyservices.com, 146c905f-fd8e-4405-8d6c-c373781cc759@identity-protect.org, 88590b09-1627-4332-8186-4dc27c401611@identity-protect.org, a42dc8d6-ccb5-48c7-aaf6-05a7fe975347@identity-protect.org, b3f718f9-e25d-43d8-a75d-8da82f86b0e6@identity-protect.org, c24acda0-9bab-4d68-9bca-dcc0d2b0f83b@identity-protect.org, e60e29c7-e474-41a0-8ccc-d806db24194c@identity-protect.org, owner-4186664@foleycs.com.whoisprivacyservice.org
Subdomains
| Subdomain |
|---|
| www.foleycs.com |
Showing 1 of 1 subdomain (1 per page).
Mail and authentication
Nameservers
- ns-427.awsdns-53.com
- ns-971.awsdns-57.net
- ns-1444.awsdns-52.org
- ns-1779.awsdns-30.co.uk
MX records
- foleycs-com.mail.protection.outlook.com
SPF policy
- include: spf.protection.outlook.com
Threat-feed evidence
History
Related pages
Pivot from foleycs.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: "foleycs.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.