Hostname
ilanlar.com
Last fetched
ilanlar.com resolves to 13.61.65.234, announced in 13.60.0.0/15 by AMAZON-02 - Amazon.com, Inc. in SE. ilanlar.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.61.65.234
13.60.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Stockholm, SE
- 13.62.117.182
13.62.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Stockholm, SE
- 13.62.236.135
13.62.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Stockholm, SE
- 13.62.34.75
13.62.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Stockholm, SE
- 16.170.84.195
16.170.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Stockholm, SE
- 16.171.229.38
16.170.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Stockholm, SE
- 51.20.228.14
51.20.0.0/16 · AMAZON-02 - Amazon.com, Inc. · Stockholm, SE
- 56.228.53.60
56.228.0.0/16 · AMAZON-02 - Amazon.com, Inc. · Stockholm, SE
- 51.21.11.253
51.21.0.0/16 · AMAZON-02 - Amazon.com, Inc. · Stockholm, SE
- 16.16.236.154
16.16.0.0/16 · AMAZON-02 - Amazon.com, Inc. · Stockholm, SE
- 16.192.142.87
- 16.192.115.30
IPv6 resolution
No AAAA record for ilanlar.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:146
- Registrant organisation
- ******** ******** (see notes section below on how to view unmasked data)
- Contact emails
- ********@*****.***, yke@yusufergenc.com
Subdomains
Showing 4 of 6. View all subdomains →
Mail and authentication
Nameservers
- ns-498.awsdns-62.com
- ns-799.awsdns-35.net
- ns-1293.awsdns-33.org
- ns-2037.awsdns-62.co.uk
MX records
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- alt3.aspmx.l.google.com
- alt4.aspmx.l.google.com
SPF policy
- include: dc-aa8e722993._spfm.ilanlar.com
Threat-feed evidence
History
Related pages
Pivot from ilanlar.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: "ilanlar.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.