Hostname
robokassa.com
Last fetched
robokassa.com resolves to 6 IPv4 addresses operated by KIT Karlsruhe Institute of Technology in RU. WHOIS lists iana:463 as the registrar.
Nutrition Label
Resolution chain
robokassa.com resolves to 6 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 195.209.82.63 | 195.209.82.0/24 | AS34879 | KIT Karlsruhe Institute of Technology | RU |
| 46.235.186.62 | 46.235.186.0/24 | AS34879 | KIT Karlsruhe Institute of Technology | RU |
| 46.235.189.252 | 46.235.188.0/23 | AS34879 | KIT Karlsruhe Institute of Technology | RU |
| 78.41.109.216 | 78.41.109.0/24 | AS34879 | KIT Karlsruhe Institute of Technology | BY |
| 195.209.82.105 | 195.209.82.0/24 | AS34879 | KIT Karlsruhe Institute of Technology | RU |
| 195.209.81.169 | 195.209.81.0/24 | AS34879 | KIT Karlsruhe Institute of Technology | RU |
WHOIS identity
- Registrar
- iana:463
- Organization
- llc 'ps development'
- Contact emails
Subdomains
2 observed subdomains of robokassa.com.
| Subdomain |
|---|
| docs2.robokassa.com |
| www.robokassa.com |
Web-graph footprint
Distinct hostnames that link to or from robokassa.com in the public web crawl.
794 sites link to this hostname.
Sample inbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
3 SPF mechanisms authorising senders for robokassa.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | _spf.yandex.net |
| SPF_INCLUDE | spf.protection.outlook.com |
| SPF_IP | 185.59.216.0/24 |
Related pages
Pivot deeper into the graph from robokassa.com.
- IP · 195.209.82.63
- ASN · AS34879KIT Karlsruhe Institute of Technology
- Registrar · iana:463
- Country · RU
- Email · ops-registrators@paysend.com
- TLD · .com
- Browse hostnames · ro…
- Glossary · What is a hostname?
- Whisper Internet Directory — home
- Live MOAS conflicts feed
- Threat feed · Spamhaus DROP
- United States internet infrastructure
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "robokassa.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
-[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.