Skip to content

Hostname

emaktab.uz

Last fetched

emaktab.uz resolves to 84.54.112.58, announced in 84.54.112.0/24 by BRM-AS - "Uzbektelekom" Joint Stock Company in UZ. emaktab.uz is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · emaktab.uzRouting diversity1.5/10Peering density2.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.6/10canon.whisper.security/host/emaktab.uz

Resolution chain

IPv6 resolution

No AAAA record for emaktab.uz is recorded in WhisperGraph.

Attribution

uzbektelekom joint stock

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for emaktab.uz. 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.

Subdomains

Subdomain
amity.emaktab.uz
amityuz.emaktab.uz
anor.emaktab.uz
anorbank.emaktab.uz
company.emaktab.uz
forpartners.emaktab.uz
forpartnersuz.emaktab.uz
help.emaktab.uz
login.emaktab.uz
mx.emaktab.uz
ocs.emaktab.uz
program.emaktab.uz

Showing 12 of 34. 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.

Sample inbound links

Sample outbound links

Mail and authentication

Nameservers

  • ns1.selectel.ru
  • ns2.selectel.ru
  • ns3.selectel.ru
  • ns4.selectel.ru

MX records

  • mx.emaktab.uz

SPF policy

  • include: mail.zendesk.com
  • ip: 185.74.4.45
  • ip: 185.74.5.154

Threat-feed evidence

History

Related pages

Pivot from emaktab.uz 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: "emaktab.uz"})-[: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.