Hostname
engineeringinvestments.com
Last fetched
engineeringinvestments.com resolves to 18.173.154.34, announced in 18.173.154.0/23 by AMAZON-02 - Amazon.com, Inc. in DE. engineeringinvestments.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
- 18.173.154.34
18.173.154.0/23 · AMAZON-02 - Amazon.com, Inc. · Munich, DE
- 18.173.154.74
18.173.154.0/23 · AMAZON-02 - Amazon.com, Inc. · Munich, DE
- 18.173.154.8
18.173.154.0/23 · AMAZON-02 - Amazon.com, Inc. · Munich, DE
- 18.173.154.87
18.173.154.0/23 · AMAZON-02 - Amazon.com, Inc. · Munich, DE
- 35.156.136.27
35.156.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 63.181.86.252
63.180.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
IPv6 resolution
No AAAA record for engineeringinvestments.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:468
- Registrant organisation
- on behalf of engineeringinvestments.com owner
- Contact emails
- nivr@bigfoot.com, sales@ifastnet.com, 293266bf-8bab-4deb-a7af-9ef0bb664942@identity-protect.org, 31c661f1-7887-4a84-9cc4-5439c23f353a@identity-protect.org, 7c29d370-a0ea-4140-b755-60e2141df6e8@identity-protect.org, 8010784a-bdc1-458d-bfb3-7eaa8405e4db@identity-protect.org, contact@privacyprotect.org
Subdomains
| Subdomain |
|---|
| courses.engineeringinvestments.com |
Showing 1 of 1 subdomain (1 per page).
Mail and authentication
Nameservers
- ns-132.awsdns-16.com
- ns-978.awsdns-58.net
- ns-1374.awsdns-43.org
- ns-1931.awsdns-49.co.uk
MX records
- inbound-smtp.us-east-1.amazonaws.com
SPF policy
- include: amazonses.com
- include: eu-sender.zohoinvoice.com
Threat-feed evidence
History
Related pages
Pivot from engineeringinvestments.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: "engineeringinvestments.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.