Skip to content

Hostname

bugemauniv.ac.ug

Last fetched

bugemauniv.ac.ug resolves to 82.29.189.104, announced in 82.29.184.0/21 by AS-HOSTINGER - Hostinger International Limited in GB. bugemauniv.ac.ug 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 · bugemauniv.ac.ugRouting diversity1.5/10Peering density6.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency6.7/10Resolver footprint3.2/10canon.whisper.security/host/bugemauniv.ac.ug

Resolution chain

IPv6 resolution

No AAAA record for bugemauniv.ac.ug is recorded in WhisperGraph.

Attribution

hostinger international

ORIGIN_AS

WHOIS identity

Registrant organisation
bugema university
Contact emails
registrar@i3c.co.ug

Subdomains

Subdomain
adminblog.bugemauniv.ac.ug
adminbuir.bugemauniv.ac.ug
admissions.bugemauniv.ac.ug
alumni.bugemauniv.ac.ug
apply.bugemauniv.ac.ug
assets.bugemauniv.ac.ug
authdb.bugemauniv.ac.ug
blog.bugemauniv.ac.ug
buir.bugemauniv.ac.ug
bulibrary.bugemauniv.ac.ug
busaguild.bugemauniv.ac.ug
conferencing.bugemauniv.ac.ug

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

  • dns1.namecheaphosting.com
  • dns2.namecheaphosting.com

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com
  • aspmx4.googlemail.com
  • aspmx5.googlemail.com

SPF policy

  • include: _spf.google.com
  • include: aspmx.googlemail.com
  • include: spf.web-hosting.com
  • a: bugemauniv.ac.ug
  • mx: bugemauniv.ac.ug
  • ip: 198.54.114.115
  • ip: 198.54.116.243

Threat-feed evidence

History

Related pages

Pivot from bugemauniv.ac.ug 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: "bugemauniv.ac.ug"})-[: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.