Hostname
foleyifta.com
Last fetched
foleyifta.com resolves to 13.249.182.127, announced in 13.249.182.0/23 by AMAZON-02 - Amazon.com, Inc. in US. foleyifta.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.249.182.127
13.249.182.0/23 · AMAZON-02 - Amazon.com, Inc. · Los Angeles, US
- 13.249.182.60
13.249.182.0/23 · AMAZON-02 - Amazon.com, Inc. · Los Angeles, US
- 13.249.182.71
13.249.182.0/23 · AMAZON-02 - Amazon.com, Inc. · Los Angeles, US
- 13.249.182.94
13.249.182.0/23 · AMAZON-02 - Amazon.com, Inc. · Los Angeles, US
- 13.35.93.116
13.35.93.0/24 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 13.35.93.19
13.35.93.0/24 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 13.35.93.32
13.35.93.0/24 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 13.35.93.90
13.35.93.0/24 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
IPv6 resolution
No AAAA record for foleyifta.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:468
- Registrant organisation
- on behalf of foleyifta.com owner
- Contact emails
- mike.every@foleyservices.com, 02670f68-85ee-43e9-8ba0-1e20e30d0374@identity-protect.org, 363783e8-fbc3-4e95-b034-9fc3644bc2ba@identity-protect.org, aded4d24-afa3-471e-aa90-b49e049ec88e@identity-protect.org, ccbdac73-27d3-400e-b58e-52fcf191dd15@identity-protect.org, d9bd60c9-4bd1-4311-8960-f9c699b1ac65@identity-protect.org, owner-9745724@foleyifta.com.whoisprivacyservice.org
Subdomains
| Subdomain |
|---|
| www.foleyifta.com |
Showing 1 of 1 subdomain (1 per page).
Mail and authentication
Nameservers
- ns-451.awsdns-56.com
- ns-684.awsdns-21.net
- ns-1245.awsdns-27.org
- ns-1827.awsdns-36.co.uk
MX records
- foleyifta-com.mail.protection.outlook.com
SPF policy
- include: spf.protection.outlook.com
Threat-feed evidence
History
Related pages
Pivot from foleyifta.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: "foleyifta.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.