en
TRƯỜNG ĐẠI HỌC HÀNG HẢI VIỆT NAM
IndustryOriginGlobal rankRank in Vietnam
Updated at The higher the score, the more externally observable protections the system has recorded. This page does not certify that the website is reputable, legitimate, or completely free of vulnerabilities.
As of August 27, 2026 at 11:07, www.vieclam.vimaru.edu.vn has a security score of 59/100 (grade U: “Unrated”), but this result is provisional because some required evidence is incomplete. CyStack’s automated assessment recorded 12 issues to review after completing 61.1% of applicable checks. The website owner should address “HTTPS/TLS endpoint reachability” first, then review the remaining items in order of impact.
At assessment time, CyStack did not find www.vieclam.vimaru.edu.vn or related infrastructure on any scam, phishing, or malware warning list after checking 5 online reputation sources. This result reflects external observations; it does not guarantee absolute safety or verify the organization’s legal status or reputation.
Compare the security level of each assessed category at a glance.
Frequently asked questions
A valid SSL certificate still does not prove that www.vieclam.vimaru.edu.vn is safe, legitimate, or free of scam signals. For a more complete assessment, this report also checks phishing and malware, exposed email records, IPs and open ports, subdomains, technologies, and CVEs that may apply to observed versions.
HTTPS on www.vieclam.vimaru.edu.vn could not be reached during this assessment, so its SSL certificate and transport encryption could not be evaluated.
Review HTTPS and certificateData sources
CyStack compiles scan results from its internal cybersecurity monitoring systems, including CyStack VulnScan and CyStack Threat Intelligence, together with publicly available Internet data. The assessment only observes and analyzes information already available; it does not attempt unauthorized access, test passwords, send exploit code, or change or disrupt the assessed system.
CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the enterprise.
These 3 failed checks or warnings have the greatest impact on the result for www.vieclam.vimaru.edu.vn.
Why it matters
This check only confirms whether a TLS handshake can be established with at least one tested resolved endpoint on the HTTPS port. Certificate trust, hostname identity, validity, chain, protocol, and cryptographic strength are evaluated separately.
What to do
Provide the entire website over HTTPS using a certificate trusted by common browsers.
Diagnostic information
The scanner could not complete a TLS handshake with the HTTPS endpoint during this assessment.
Evidence and check scope
This is the port on which the scanner attempted a TLS connection. The port number alone does not prove that the port is open or that HTTPS works.
This list contains only failed checks and warnings. Checks without enough evidence are grouped separately below.
Evidence and check scope
Evidence and check scope
What to do
Remove direct Internet access and require a VPN, a hardened access gateway, or trusted source networks; also use MFA where supported.
Evidence and check scope
What to do
Disable the legacy service or replace it with an encrypted alternative such as SSH, SFTP, HTTPS, or the secure version of the mail protocol.
Evidence and check scope
This check compares an observed product only when a reliable version and exact CPE identity are available, using applicability records from the National Vulnerability Database (NVD). Any returned match is a lead, not confirmation: the installed software may include vendor fixes or differ from the version visible on the Internet.
What to do
Confirm the exact installed package and read the vendor advisory. If that installation is affected, apply the vendor patch or upgrade to a fixed version.
Evidence and check scope
16 additional evidence fields are not shown here.
References
What to do
After every legitimate sender passes DMARC, move gradually to quarantine and then reject, covering 100% of messages.
Evidence and check scope
References
What to do
Remove obsolete DNS names and protect non-public systems with strong authentication, MFA, network allowlists, or a VPN.
Diagnostic information
Subdomain discovery did not complete, so the current list may be incomplete.
Evidence and check scope
Infostealer intelligence may contain credentials associated with the domain, but it does not prove that an account is current, valid, or still exposed.
What to do
Review the masked evidence and observation time, validate affected accounts and devices, then reset active credentials and sessions, enforce MFA, and remove malware where confirmed.
Evidence and check scope
8 additional evidence fields are not shown here.
What to do
Confirm the owner and purpose of every open port, then stop or firewall any service that is not intentionally public.
Evidence and check scope
What to do
Add an aggregate report address (rua) that is protected and monitored, or use a trusted DMARC reporting service.
Evidence and check scope
References
What to do
Publish CAA records that allow only the certificate providers your organization actually uses.
Evidence and check scope
References
What to do
Sign the DNS zone, publish the matching DS record through the registrar, and monitor the signature chain after key changes.
References
What to do
Publish at least two authoritative name servers, then separately verify that they use resilient, appropriately independent infrastructure.
Evidence and check scope
16 additional evidence fields are not shown here.
16 additional evidence fields are not shown here.
References
Recently completed assessments, prioritizing websites with a similar sector, country or security grade for easier comparison.
Vietnam
