Skip to content

Hostname

authorization.rutech.tech

Last fetched

authorization.rutech.tech resolves to 188.120.246.133, announced in 188.120.240.0/21 by RU-JSCIOT - JSC IOT in RU. authorization.rutech.tech is listed by 1 threat feed; reconciled level HIGH.

Threat posture

40threat score (procedure-native scale)

HIGH

Listed by 1 threat feed. At least one source recommends blocking.

Threat feeds listing this
1
Verdict coverage
malicious-evidenced
First seen on a feed
Thu, 03 Sep 2026 09:49:49 GMT
Last seen on a feed
Mon, 14 Sep 2026 23:25:39 GMT

Nutrition Label

WHISPER CANON · authorization.rutech.techRouting diversity1.5/10Peering density5.4/10MOAS conflict✓ noneThreat-feed listings8.0/10WHOIS transparency0.0/10Resolver footprint8.0/10canon.whisper.security/host/authorization.rutech.tech

Resolution chain

IPv6 resolution

No AAAA record for authorization.rutech.tech is recorded in WhisperGraph.

Attribution

jsc iot

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for authorization.rutech.tech. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

Mail and authentication

Nameservers

  • miguel.ns.cloudflare.com
  • veda.ns.cloudflare.com
  • 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

Threat-feed evidence

History

Related pages

Pivot from authorization.rutech.tech 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: "authorization.rutech.tech"})-[: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 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.