CyberTrust

Public security report

hoyu.edu.hk security rating

F

32/100

A means lowest risk and F means highest, like a school report card. How the score is calculated →

Scanned 2026-10-26 · 28 issue(s) found · 10 checks passed

Re-scan hoyu.edu.hk now

What this scan found

CyberTrust assessed hoyu.edu.hk passively — using only information that is publicly visible on the internet: DNS records, certificates, response headers and reachable services. The result is 32/100, grade F, where A means lowest risk and F means highest, like a school report card.

Email spoofing is possible: no DMARC record was found for hoyu.edu.hk, so anyone can send mail that appears to come from @hoyu.edu.hk.

Strongest area: reputation and credential exposure (100/100). Weakest area: TLS encryption and certificates (0/100).

28 issue(s) need attention (2 critical, 6 high, 7 medium, 13 low), while 10 checks passed.

Infrastructure observed: mail is hosted by google, DNS is served by godaddy, the web server identifies as apache.

21 subdomain(s) of hoyu.edu.hk resolve publicly.

Score by category

Issues found (28)

criticalDatabase exposed to the internet: MySQL on 103.11.101.95:3306

Automated bots continuously scan for MySQL on 103.11.101.95:3306 (hosts: hoyu.edu.hk, www.hoyu.edu.hk, mobilelab.hoyu.edu.hk) and try weak passwords or known exploits; the usual outcome is a full data exfiltration or ransomware wiping.

1 asset(s) affected · worth +7 points · how to manage your external attack surface →

high2 actively exploited vulnerabilities (CISA KEV) on 210.3.239.138

2 actively exploited vulnerabilities (CVE-2021-40438, CVE-2024-38475) match versions seen on 210.3.239.138; working exploits exist and attackers scan for them at scale.

4 asset(s) affected · worth +7 points · how to manage your external attack surface →

highSSLv3 is enabled

SSLv3 suffers from POODLE, which can recover plaintext such as cookies and credentials; it is prohibited by standard and offers no compatibility benefit today.

6 asset(s) affected · worth +5 points · how to read an SSL/TLS certificate check →

criticalCertificate expired 847 days ago (2024-07-01)

It expired 847 days ago (2024-07-01): browsers show a full-page warning, most visitors leave, and API or app integrations fail without a clear reason.

1 asset(s) affected · worth +4 points · check a certificate with the free SSL tool →

medium356 known vulnerabilities inferred on 210.3.239.138

356 known vulnerabilities are inferred on 210.3.239.138; even un-weaponised ones leave the system open to every published technique. Version-based inference - treat as a patch-currency signal.

5 asset(s) affected · worth +4 points · how to manage your external attack surface →

mediumHSTS not enabled

Without it, an attacker can strip SSL on the first HTTP request and keep the user on plaintext (SSL stripping), a common attack on public Wi-Fi.

9 asset(s) affected · worth +3 points · how to set HSTS, CSP and other security headers →

mediumHTTP is not redirected to HTTPS

Visitors who type the bare domain land on an unencrypted connection and submit data in plaintext, with nothing on screen to warn them.

5 asset(s) affected · worth +3 points · how to set HSTS, CSP and other security headers →

mediumPossibly end-of-life software: php 7.4.11, openssl 1.0.2k

Software php 7.4.11, openssl 1.0.2k appears unsupported: new vulnerabilities will never be patched. (Version-based inference; some distributions backport fixes - confirm with your vendor.)

5 asset(s) affected · worth +3 points · how to set HSTS, CSP and other security headers →

highCertificate does not match the hostname

This certificate is issued for www.hoyu.edu.hk, so browsers warn; typical causes are missing the bare domain, a stale name, or an incomplete SAN list.

1 asset(s) affected · worth +2 points · check a certificate with the free SSL tool →

highCertificate is not trusted (self-signed)

This certificate cannot be chained (self-signed), so visitors get a warning - and repeated warnings teach people to click through, which defeats warnings during real attacks.

1 asset(s) affected · worth +2 points · check a certificate with the free SSL tool →

mediumDES/3DES cipher accepted

64-bit block ciphers are vulnerable to SWEET32 after enough data on one connection, and 3DES is no longer accepted by compliance standards.

5 asset(s) affected · worth +2 points · how to read an SSL/TLS certificate check →

mediumOutdated TLS versions enabled (TLSv1.0, TLSv1.1)

Versions TLSv1.0, TLSv1.1 are formally deprecated, fail PCI DSS requirements and are no longer supported by modern browsers; they also enable downgrade attacks and fail compliance audits.

5 asset(s) affected · worth +2 points · how to read an SSL/TLS certificate check →

mediumFile sharing exposed: FTP on 103.11.101.95:21

FTP on 103.11.101.95:21 (hosts: hoyu.edu.hk, www.hoyu.edu.hk, mobilelab.hoyu.edu.hk) enables ransomware spread (as WannaCry did via SMB), arbitrary file downloads and a pivot into the internal network.

1 asset(s) affected · worth +2 points · how to manage your external attack surface →

lowNo OCSP stapling

The server does not staple the certificate revocation status. Every revocation check becomes an extra round trip to the CA, which slows the first visit and, if the CA endpoint is unreachable or the visitor's network blocks it, leaves the browser without a usable revocation status.

8 asset(s) affected · worth +1 points · check a certificate with the free SSL tool →

lowNo Content Security Policy

Without it, any injected script runs: session theft, fake payment forms, or card-skimming scripts on compromised pages. CSP limits the damage even when something else fails.

8 asset(s) affected · worth +1 points · how to set HSTS, CSP and other security headers →

lowX-Content-Type-Options missing

Without it a file uploaded as an image can be executed as HTML/JavaScript on your domain, stealing same-site cookies and sessions.

9 asset(s) affected · worth +1 points · how to set HSTS, CSP and other security headers →

lowNo clickjacking protection

Without it, attackers overlay a transparent frame of your page and trick users into clicking real actions such as transfers or password changes (clickjacking).

9 asset(s) affected · worth +1 points · how to set HSTS, CSP and other security headers →

lowCleartext mail protocol exposed: POP3 on 103.11.101.95:110

POP3 on 103.11.101.95:110 exposes mailbox credentials to anyone capturing traffic; one compromised mailbox is usually used to reset other accounts and phish contacts.

2 asset(s) affected · worth +1 points · how to manage your external attack surface →

lowCookies without Secure/HttpOnly (MRBS_SESSID)

Missing Secure lets cookies travel in plaintext; missing HttpOnly lets injected scripts steal sessions; missing SameSite enables CSRF. Affected: MRBS_SESSID.

2 asset(s) affected · worth +1 points · how to set HSTS, CSP and other security headers →

lowDNSSEC not enabled

Without it, attackers can poison caches or forge answers and send visitors to a lookalike server that harvests credentials.

1 asset(s) affected · worth +1 points · what DNSSEC prevents and how to enable it →

lowContent Security Policy is weak (object-src not restricted)

The policy is too permissive (object-src not restricted), so injected scripts still run while giving a false sense of security.

1 asset(s) affected · worth +1 points · how to set HSTS, CSP and other security headers →

lowPage loads 6 active resources over HTTP

6 script(s)/stylesheet(s) load over HTTP and can be replaced in transit, letting an attacker act inside a page that looks secure; browsers also hide the padlock.

1 asset(s) affected · worth +1 points · how to set HSTS, CSP and other security headers →

Checks passed

  • Mail exchangers configured
  • SPF record is valid
  • DKIM signing keys found
  • Name servers are redundant
  • No API keys found in front-end bundles
  • Only modern TLS versions are enabled
  • No weak cipher suites accepted
  • Certificate is valid and trusted
  • No shadow-AI services exposed
  • No mail-server IP on spam blocklists

What we detected

mail provider
google
dns provider
godaddy
web server
apache
subdomain count
21

What could not be fully checked

Frequently asked questions about hoyu.edu.hk security

Does hoyu.edu.hk have DMARC protection against email spoofing?
No. No DMARC record was found for hoyu.edu.hk, so mail forged from @hoyu.edu.hk has no policy-based barrier at all.
How is hoyu.edu.hk's F security grade calculated?
CyberTrust scores hoyu.edu.hk passively across 6 area(s) — reputation and credential exposure 100/100; DNS hygiene 84/100; email spoofing defences (SPF/DKIM/DMARC) 44/100; TLS encryption and certificates 0/100; HTTP security headers 0/100; external attack surface 0/100 — and combines them by weight into the overall score of 32/100, which maps to grade F.
What is the most serious issue found on hoyu.edu.hk?
Database exposed to the internet: MySQL on 103.11.101.95:3306 (severity critical). Automated bots continuously scan for MySQL on 103.11.101.95:3306 (hosts: hoyu.edu.hk, www.hoyu.edu.hk, mobilelab.hoyu.edu.hk) and try weak passwords or known exploits; the usual outcome is a full data exfiltration or ransomware wiping. Fixing it is worth about +7 points.
How many subdomains does hoyu.edu.hk expose?
This scan observed 21 publicly resolvable subdomain(s) for hoyu.edu.hk. Verified owners get the full list, with each host's open ports and running services.

What a verified owner of hoyu.edu.hk sees

Everything above is what anyone can observe from the internet. Domain owners who verify ownership additionally get the full asset inventory — every subdomain with its open ports and running services — look-alike and typosquatting domains registered against the brand, credential-exposure monitoring, and copy-paste fixes for each finding.

Verify ownership of hoyu.edu.hk (free) → Open the live interactive report →