Hostname
ostering.com
Last fetched
ostering.com resolves to 18.173.219.103, announced in 18.173.218.0/23 by AMAZON-02 - Amazon.com, Inc. in US. ostering.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.219.103
18.173.218.0/23 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 18.173.219.42
18.173.218.0/23 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 18.173.219.60
18.173.218.0/23 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 18.173.219.87
18.173.218.0/23 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 3.160.196.123
3.160.196.0/22 · AMAZON-02 - Amazon.com, Inc. · Marseille, FR
- 3.160.196.14
3.160.196.0/22 · AMAZON-02 - Amazon.com, Inc. · Marseille, FR
- 3.160.196.36
3.160.196.0/22 · AMAZON-02 - Amazon.com, Inc. · Marseille, FR
- 3.160.196.88
3.160.196.0/22 · AMAZON-02 - Amazon.com, Inc. · Marseille, FR
IPv6 resolution
No AAAA record for ostering.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:468
- Registrant organisation
- brett crawley
- Contact emails
- brettcrawley@yahoo.com, 0f7a161b-1b6a-46f6-bd17-8c1ad985f077@identity-protect.org, 68081e71-5259-44ee-8217-12f166f6fcf0@identity-protect.org, 80a9365c-845e-4be3-a65d-c7ea1b4adda3@identity-protect.org, 8c4cc72c-76cd-49be-83f7-f260e6d66e68@identity-protect.org, a08238a5-e5d7-4b9d-9e26-cb1ecb278269@identity-protect.org, e0bb08bc-aec7-4ac1-8d3b-a005681a2eae@identity-protect.org, owner-7556782@ostering.com.whoisprivacyservice.org
Subdomains
| Subdomain |
|---|
| www.ostering.com |
Showing 1 of 1 subdomain (1 per page).
Mail and authentication
Nameservers
- ns-40.awsdns-05.com
- ns-633.awsdns-15.net
- ns-1291.awsdns-33.org
- ns-1919.awsdns-47.co.uk
MX records
- dbd6a4fd.21.ik2.com
- dbd6a4fd.22.ik2.io
SPF policy
- include: amazonses.com
Threat-feed evidence
History
Related pages
Pivot from ostering.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: "ostering.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.