Hostname
smlsy.com
Last fetched
smlsy.com resolves to 18.164.32.106, announced in 18.164.32.0/21 by AMAZON-02 - Amazon.com, Inc. in BR. smlsy.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.164.32.106
18.164.32.0/21 · AMAZON-02 - Amazon.com, Inc. · São Paulo, BR
- 18.164.32.118
18.164.32.0/21 · AMAZON-02 - Amazon.com, Inc. · São Paulo, BR
- 18.164.32.122
18.164.32.0/21 · AMAZON-02 - Amazon.com, Inc. · São Paulo, BR
- 18.164.32.82
18.164.32.0/21 · AMAZON-02 - Amazon.com, Inc. · São Paulo, BR
- 18.245.104.41
18.245.104.0/23 · AMAZON-02 - Amazon.com, Inc. · Toronto, CA
- 18.245.104.49
18.245.104.0/23 · AMAZON-02 - Amazon.com, Inc. · Toronto, CA
- 18.245.104.7
18.245.104.0/23 · AMAZON-02 - Amazon.com, Inc. · Toronto, CA
- 18.245.104.90
18.245.104.0/23 · AMAZON-02 - Amazon.com, Inc. · Toronto, CA
- 54.192.35.117
54.192.34.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 54.192.35.7
54.192.34.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 54.192.35.76
54.192.34.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 54.192.35.88
54.192.34.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
IPv6 resolution
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:146
- Registrant organisation
- domains by proxy,
- Contact emails
- 2622580066@qq.com, xindata@163ns.com
Subdomains
| Subdomain |
|---|
| www.smlsy.com |
Showing 1 of 1 subdomain (1 per page).
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Mail and authentication
Nameservers
- carol.ns.cloudflare.com
- donald.ns.cloudflare.com
MX records
- mx.yandex.net
- mxa.mailgun.org
- mxb.mailgun.org
SPF policy
- redirect: _spf.yandex.net
- include: mailgun.org
Threat-feed evidence
History
Related pages
Pivot from smlsy.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: "smlsy.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.