Hostname
wink.team
Last fetched
wink.team resolves to 212.193.153.152, announced in 212.193.152.0/23 by CCT-M9P1 - OOO "Sovremennye setevye tekhnologii" in RU. wink.team 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
- 212.193.153.152
212.193.152.0/23 · CCT-M9P1 - OOO "Sovremennye setevye tekhnologii" · Moscow, RU
- 212.193.153.156
212.193.152.0/23 · CCT-M9P1 - OOO "Sovremennye setevye tekhnologii" · Moscow, RU
- 212.193.155.244
212.193.155.0/24 · CCT-AS - OOO "Sovremennye setevye tekhnologii" · Moscow, RU
- 212.193.155.246
212.193.155.0/24 · CCT-AS - OOO "Sovremennye setevye tekhnologii" · Moscow, RU
- 212.193.155.251
212.193.155.0/24 · CCT-AS - OOO "Sovremennye setevye tekhnologii" · Moscow, RU
- 46.235.186.247
46.235.186.0/24 · CCT-AS - OOO "Sovremennye setevye tekhnologii" · Moscow, RU
- 212.193.153.157
212.193.152.0/23 · CCT-M9P1 - OOO "Sovremennye setevye tekhnologii" · Moscow, RU
- 93.93.89.132
93.93.88.0/23 · CCT-AS - OOO "Sovremennye setevye tekhnologii" · Moscow, RU
- 93.93.89.131
93.93.88.0/23 · CCT-AS - OOO "Sovremennye setevye tekhnologii" · Moscow, RU
IPv6 resolution
No AAAA record for wink.team is recorded in WhisperGraph.
Attribution
ooo sovremennye setevye tekhnologii
ORIGIN_AS
WHOIS identity
- Registrar
- iana:463
- Registrant organisation
- m.i.b., s.r.o.
- Contact emails
- roman@fratric.sk
Subdomains
| Subdomain |
|---|
| helpme-test.wink.team |
| kibana-test.wink.team |
| minio-test.wink.team |
| mt-test.wink.team |
| sm-test.wink.team |
Showing 5 of 5 subdomains (5 per page).
Mail and authentication
Nameservers
- ns1.ngenix-dns.ru
- ns2.ngenix-dns.ru
MX records
- mx.yandex.net
SPF policy
- ip: 46.61.198.231/32
- include: _spf.yandex.net
Threat-feed evidence
History
Related pages
Pivot from wink.team 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: "wink.team"})-[: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.