Skip to content

Hostname

jdpu.uz

Last fetched

jdpu.uz resolves to 84.54.75.181, announced in 84.54.64.0/19 by BRM-AS - "Uzbektelekom" Joint Stock Company in UZ. jdpu.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 · jdpu.uzRouting diversity1.5/10Peering density2.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.0/10canon.whisper.security/host/jdpu.uz

Resolution chain

IPv6 resolution

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

Attribution

uzbektelekom joint stock

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for jdpu.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
110.jdpu.uz
fll.jdpu.uz
hemis.jdpu.uz
hp.jdpu.uz
iqtidor.jdpu.uz
logicompitance.jdpu.uz
mail.jdpu.uz
moodle.jdpu.uz
ruslit.jdpu.uz
student.jdpu.uz

Showing 10 of 10 subdomains (10 per page).

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

  • 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
  • rdns1.ahost.uz
  • rdns2.ahost.uz

SPF policy

  • a: jdpu.uz
  • mx: jdpu.uz
  • ip: 84.54.75.181

Threat-feed evidence

History

Related pages

Pivot from jdpu.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: "jdpu.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.