Hostname
feoconsulting.com
Last fetched
feoconsulting.com resolves to 52.222.136.112, announced in 52.222.136.0/21 by AMAZON-02 - Amazon.com, Inc. in DE. feoconsulting.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
- 52.222.136.112
52.222.136.0/21 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 52.222.136.37
52.222.136.0/21 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 52.222.136.59
52.222.136.0/21 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 52.222.136.90
52.222.136.0/21 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 99.84.41.103
99.84.40.0/21 · AMAZON-02 - Amazon.com, Inc. · Los Angeles, US
- 99.84.41.110
99.84.40.0/21 · AMAZON-02 - Amazon.com, Inc. · Los Angeles, US
- 99.84.41.114
99.84.40.0/21 · AMAZON-02 - Amazon.com, Inc. · Los Angeles, US
- 99.84.41.56
99.84.40.0/21 · AMAZON-02 - Amazon.com, Inc. · Los Angeles, US
IPv6 resolution
No AAAA record for feoconsulting.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:468
- Registrant organisation
- feo consulting.com
- Contact emails
- domains@feoconsulting.com, 1a54c0c4-8528-4dab-98dc-f83cceee8fa7@identity-protect.org, 1a67be08-9181-49c7-8eb8-83cb506d0ad0@identity-protect.org, 44ae2c5d-88ce-455a-81a1-711ec3bb207d@identity-protect.org, 81551886-7ed5-4746-8f40-02545c1167fb@identity-protect.org, 9325f1c7-e78e-454f-a39c-4b4d0e251028@identity-protect.org, b211ca95-4dc6-4e5a-86c8-597948f53d8d@identity-protect.org, eb2fcc24-cbbd-4ba5-831e-e08ab57791ea@identity-protect.org
Subdomains
Showing 2 of 2 subdomains (2 per page).
Mail and authentication
Nameservers
- ns-13.awsdns-01.com
- ns-667.awsdns-19.net
- ns-1363.awsdns-42.org
- ns-1998.awsdns-57.co.uk
MX records
- inbound-smtp.us-east-1.amazonaws.com
Threat-feed evidence
History
Related pages
Pivot from feoconsulting.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: "feoconsulting.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.