Hostname
indels-a.app
Last fetched
indels-a.app resolves to 195.209.66.244, announced in 195.209.66.0/24 by CCT-AS - OOO "Sovremennye setevye tekhnologii" in RU. indels-a.app 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
- 195.209.66.244
195.209.66.0/24 · CCT-AS - OOO "Sovremennye setevye tekhnologii" · Moscow, RU
- 195.209.67.251
195.209.67.0/24 · CCT-AS - OOO "Sovremennye setevye tekhnologii" · Moscow, RU
- 212.193.153.253
212.193.152.0/23 · CCT-M9P1 - OOO "Sovremennye setevye tekhnologii" · Moscow, RU
- 46.235.185.245
46.235.185.0/24 · CCT-AS - OOO "Sovremennye setevye tekhnologii" · Moscow, RU
- 93.93.89.222
93.93.88.0/23 · CCT-AS - OOO "Sovremennye setevye tekhnologii" · Moscow, RU
- 37.220.161.193
37.220.161.0/24 · CCT-AS - OOO "Sovremennye setevye tekhnologii" · Moscow, RU
- 37.220.161.90
37.220.161.0/24 · CCT-AS - OOO "Sovremennye setevye tekhnologii"
IPv6 resolution
No AAAA record for indels-a.app is recorded in WhisperGraph.
Attribution
ooo sovremennye setevye tekhnologii
ORIGIN_AS
WHOIS identity
- Registrar
- iana:463
- Registrant organisation
- obshchestvo s ogranichennoy otvetstvennostu centr razrabotki programmnogo obespecheniya
Subdomains
Showing 12 of 12 subdomains (12 per page).
Mail and authentication
Nameservers
- a.root-servers.net
- b.root-servers.net
- c.root-servers.net
- d.root-servers.net
- e.root-servers.net
- f.root-servers.net
- g.root-servers.net
- h.root-servers.net
- i.root-servers.net
- j.root-servers.net
- k.root-servers.net
- l.root-servers.net
- m.root-servers.net
- ns1.ngenix-dns.ru
- ns2.ngenix-dns.ru
Threat-feed evidence
History
Related pages
Pivot from indels-a.app 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: "indels-a.app"})-[: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.