Hostname
sapsana.com
Last fetched
sapsana.com resolves to 188.120.243.160, announced in 188.120.240.0/21 by RU-JSCIOT - JSC IOT in RU. sapsana.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
- 188.120.243.160
188.120.240.0/21 · RU-JSCIOT - JSC IOT · Moscow, RU
IPv6 resolution
Attribution
jsc iot
ORIGIN_AS
WHOIS identity
- Registrar
- iana:1606
- Registrant organisation
- personal data, can not be publicly disclosed according to applicable laws.
- Contact emails
- sapsana.com@regprivate.ru
Subdomains
| Subdomain |
|---|
| dev.sapsana.com |
| www.sapsana.com |
Showing 2 of 3. View all subdomains →
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
- ns1.reg.ru
- ns2.reg.ru
MX records
- mx.yandex.net
SPF policy
- include: spf.smtp.bz
- a: sapsana.com
- mx: sapsana.com
- include: spf.unisender.com
- include: _spf.yandex.net
- include: spf.cloud.simtechdev.us
- ip: 18.195.252.74
Threat-feed evidence
History
Related pages
Pivot from sapsana.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: "sapsana.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.