en
PlayIMDb — Watch IMDb Titles Instantly
Watch any IMDb movie or TV show instantly. Just paste an IMDb link and start streaming — no account needed.
IndustryOriginGlobal rankRank in India
Updated at The score and grade reflect the result recorded at scan time. Review each check and its evidence for the full context.
This report summarizes the security observations recorded for imdb.su at scan time. Review each check and its evidence for the full context.
At assessment time, CyStack did not find imdb.su 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.
Data 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 imdb.su.
Why it matters
Content Security Policy (CSP) limits where scripts, styles, frames, and other browser content may come from. A strong policy reduces the impact if an attacker manages to inject content into a page.
What to do
Define only the sources the application needs, test the policy before activating it, and avoid broad wildcard (*) rules, unsafe-inline, and unsafe-eval where possible.
Evidence and check scope
References
Why it matters
TLS 1.0 and TLS 1.1 use outdated security designs and are no longer accepted by modern standards. Leaving them enabled allows older, weaker connection methods.
What to do
Disable TLS 1.0 and TLS 1.1, support TLS 1.2 securely, and enable TLS 1.3 where possible.
Evidence and check scope
Why it matters
DMARC lets the domain owner tell receiving services what to do when the visible From address is not verified by SPF or DKIM. Without DMARC, attackers have more opportunity to impersonate the domain in phishing email.
What to do
Publish a DMARC record at _dmarc, begin by collecting reports, and confirm that legitimate senders pass before applying a blocking policy.
References
This list contains only failed checks and warnings. Checks without enough evidence are grouped separately below.
Check result
The result recorded “Allowed browser content (CSP)” as failed at scan time. Confirm the current condition before acting.
Why it matters
Content Security Policy (CSP) limits where scripts, styles, frames, and other browser content may come from. A strong policy reduces the impact if an attacker manages to inject content into a page.
What to do
Define only the sources the application needs, test the policy before activating it, and avoid broad wildcard (*) rules, unsafe-inline, and unsafe-eval where possible.
Evidence and check scope
References
Check result
Accepted versions: TLS 1.0, TLS 1.1, TLS 1.2, TLS 1.3.
Why it matters
TLS 1.0 and TLS 1.1 use outdated security designs and are no longer accepted by modern standards. Leaving them enabled allows older, weaker connection methods.
What to do
Disable TLS 1.0 and TLS 1.1, support TLS 1.2 securely, and enable TLS 1.3 where possible.
Check result
No DMARC policy was found by domain tree walk.
Why it matters
DMARC lets the domain owner tell receiving services what to do when the visible From address is not verified by SPF or DKIM. Without DMARC, attackers have more opportunity to impersonate the domain in phishing email.
What to do
Check result
The result recorded “Protection from deceptive framing (clickjacking)” as failed at scan time. Confirm the current condition before acting.
Why it matters
Another website can place this page inside a hidden or misleading frame and trick a user into clicking an unintended action. Frame restrictions tell browsers which sites, if any, may embed the page.
Check result
The result recorded “Correct file-type handling (nosniff)” as failed at scan time. Confirm the current condition before acting.
Why it matters
Without the nosniff setting, a browser may guess a file's type and treat harmless-looking content as executable code. This can turn an incorrect Content-Type into a security issue.
What to do
Check result
The HTTPS response does not contain an effective HSTS policy.
Why it matters
HTTP Strict Transport Security (HSTS) tells a browser to use HTTPS automatically on future visits. This reduces the chance that a visitor is downgraded to an unencrypted connection.
What to do
After confirming that every required page works over HTTPS, send the Strict-Transport-Security header on all HTTPS responses.
Check result
The HTTP root remains reachable without completing an HTTPS redirect.
Why it matters
Visitors may enter an address beginning with HTTP or follow an old link. Redirecting them immediately to HTTPS prevents the rest of the visit from continuing over an unencrypted connection.
What to do
Check result
No SPF record was found.
Why it matters
Sender Policy Framework (SPF) lists the systems allowed to send email for the domain. Without it, receiving services have less evidence to distinguish legitimate mail from spoofed mail.
What to do
Publish one SPF TXT record that includes every legitimate email service and no unauthorized sender.
Check result
CyStack confirmed at least 9 active DNS subdomains. 1 names may expose sensitive services; discovery was partial, so more may exist.
Why it matters
Names containing admin, development, staging, VPN, database, or monitoring terms may point attackers toward valuable systems. A name alone does not prove exposure, but it identifies a surface that should be reviewed.
Check result
No explicit MX or Null MX record was found.
Why it matters
MX records direct incoming email to the correct mail servers. Broken records can stop delivery, while a Null MX clearly tells senders that the domain does not receive email.
What to do
Correct unreachable or outdated MX hosts, or publish a Null MX if the domain is not intended to receive email.
Check result
The result recorded “Browser feature restrictions (Permissions-Policy)” as failed at scan time. Confirm the current condition before acting.
Why it matters
Permissions-Policy controls whether this page and embedded content may use features such as the camera, microphone, and location. Leaving unused features available creates unnecessary access paths.
Check result
The result recorded “URL privacy (Referrer-Policy)” as failed at scan time. Confirm the current condition before acting.
Why it matters
When a visitor follows a link, the browser may send the previous page's URL to the destination. Paths and query values in that URL can reveal sensitive context to another website.
What to do
Check result
No explicit MX or Null MX record was found.
Why it matters
A domain should clearly state whether it receives email. Without valid MX records or a Null MX, senders may try an unintended server and delivery behavior becomes unpredictable.
What to do
Publish valid MX records for the intended mail servers, or a Null MX if the domain never accepts email.
Check result
Found 0 applicable CAA record(s).
Why it matters
Certificate Authority Authorization (CAA) records state which certificate providers may issue certificates for the domain. This reduces the chance of an unintended provider issuing one.
What to do
Publish CAA records that allow only the certificate providers your organization actually uses.
Check result
No DNSSEC DS delegation was found.
Why it matters
DNSSEC adds digital signatures so resolvers can detect forged DNS answers. This quick check confirms the parent domain has a DS record, but it does not validate the complete signature chain.
What to do
Sign the DNS zone, publish the matching DS record through the registrar, and monitor the signature chain after key changes.
Check result
The scan could not determine “Domain registration expiry” from the collected evidence.
Why it matters
An expired domain stops directing users to the organization's services and may eventually become available to someone else. A domain close to expiry leaves little time to recover from payment or account problems.
What to do next
Review the recorded evidence with a security specialist before using this result for a current decision.
Check result
The scan could not determine “Domain registration status” from the collected evidence.
Why it matters
Registrar or registry restrictions such as hold, redemption, or pending deletion can disable the domain. If they are not resolved, the organization may lose control of its website and email identity.
What to do next
Review the recorded evidence with a security specialist before using this result for a current decision.
Check result
The service was observed on shared edge infrastructure and cannot be reliably attributed to this domain.
Why it matters
Every open service can be discovered and attacked and must be configured, monitored, and patched. Services without a clear public purpose add risk without providing business value.
What to do next
Review the recorded evidence with a security specialist before using this result for a current decision.
Evidence and check scope
Check result
5 providers were definitive and 1 were inconclusive.
Why it matters
This shows how many independent blacklist services returned a clear result. A service that was unavailable was not checked successfully and must not be treated as a clean result.
What to do next
Review the recorded evidence with a security specialist before using this result for a current decision.
Evidence and check scope
Check result
The public homepage response revealed 3 technology item(s).
Why it matters
Response headers, page content, and other public clues suggest which technologies the service uses. These observations help explain the attack surface, but they can be incomplete or mistaken and do not by themselves confirm a vulnerability.
What to do next
Review the recorded evidence with a security specialist before using this result for a current decision.
Evidence and check scope
Check result
Passive response signals identified one or more WAF, CDN, or edge products; enforcement was not tested.
Why it matters
Public response details suggest that a Web Application Firewall (WAF), CDN, or other edge service is present. This quick scan identified the provider but did not test whether attack blocking is configured or working correctly.
What to do next
Review the recorded evidence with a security specialist before using this result for a current decision.
Evidence and check scope
Check result
Observed 0 versioned product(s); 0 had exact CPE mappings and 0 completed lookup(s).
Why it matters
This shows how many detected products had reliable version information and an exact CPE identity, allowing them to be checked against CVE applicability data. A product that could not be checked must not be treated as free of known vulnerabilities.
What to do next
Review the recorded evidence with a security specialist before using this result for a current decision.
Evidence and check scope
Check result
The certificate matches the requested target.
Why it matters
The certificate must list the exact hostname visitors requested in its Subject Alternative Names (SAN). A mismatch produces browser warnings because the certificate may belong to a different service.
What to do next
Review the recorded evidence with a security specialist before using this result for a current decision.
Evidence and check scope
Check result
The certificate chains to a trusted root.
Why it matters
Browsers trust a website only when its certificate can be traced to a recognized certificate provider. An untrusted certificate causes warnings and prevents visitors from reliably confirming the website's identity.
What to do next
Review the recorded evidence with a security specialist before using this result for a current decision.
Evidence and check scope
Check result
A TLS handshake succeeded on port 443.
Why it matters
HTTPS encrypts data between visitors and the website and helps prove they reached the intended service. Without it, network observers may read or alter traffic and browsers may show a security warning.
What to do next
Review the recorded evidence with a security specialist before using this result for a current decision.
Evidence and check scope
Check result
The target resolved to 4 public IP address(es).
Why it matters
Public DNS connects the domain to its Internet addresses. Missing or incorrect records can make the service unreachable or send traffic to the wrong system.
What to do next
Review the recorded evidence with a security specialist before using this result for a current decision.
Evidence and check scope
Check result
The scan recorded “Password form transport security” as not applicable.
Why it matters
If either a password page or the address receiving its form uses HTTP, someone observing the network may read or change the submitted password.
What to do next
Review the recorded evidence with a security specialist before using this result for a current decision.
Evidence and check scope
Check result
No exact product version was observed, so there was no reliable CVE candidate to compare with the CISA Known Exploited Vulnerabilities catalog. This check is not applicable.
Why it matters
A possible CVE match also appears in the CISA Known Exploited Vulnerabilities (KEV) catalog, which means attackers have used that vulnerability in real incidents. The match is urgent to investigate, but the installed software still needs to be confirmed as affected.
What to do next
Review the recorded evidence with a security specialist before using this result for a current decision.
Evidence and check scope
Check result
No public management service was found on the scanned TCP port set.
Why it matters
Remote administration services such as RDP, VNC, Docker, Kubernetes, and management consoles are high-value targets. Public exposure allows anyone on the Internet to attempt passwords or exploit an unpatched service.
What to do next
Review the recorded evidence with a security specialist before using this result for a current decision.
Evidence and check scope
Check result
No public datastore service was found on the scanned TCP port set.
Why it matters
Databases and caches often contain sensitive information and are normally used only by internal applications. Direct Internet access makes password attacks and configuration mistakes much more likely to become a data breach.
What to do next
Review the recorded evidence with a security specialist before using this result for a current decision.
Evidence and check scope
Check result
No public file-sharing service was found on the scanned TCP port set.
Why it matters
Services such as SMB, NFS, and rsync can reveal or modify shared files and have a history of serious vulnerabilities. They rarely need to accept connections directly from the public Internet.
What to do next
Review the recorded evidence with a security specialist before using this result for a current decision.
Evidence and check scope
Check result
No public legacy cleartext service was found on the scanned TCP port set.
Why it matters
Older services such as Telnet, FTP, and unencrypted mail or directory protocols can send passwords and data in readable form. Anyone able to observe the network path may capture them.
What to do next
Review the recorded evidence with a security specialist before using this result for a current decision.
Evidence and check scope
Check result
The result recorded “Cross-site access rules (CORS)” as passed at scan time.
Why it matters
Cross-Origin Resource Sharing (CORS) decides which websites may read responses from this service in a visitor's browser. Rules that trust arbitrary origins, especially with login cookies, can expose private data to another website.
What to do next
Review the recorded evidence with a security specialist before using this result for a current decision.
Evidence and check scope
Check result
The certificate is valid from 2026-06-24T13:59:24Z to 2026-09-22T14:56:56Z.
Why it matters
A certificate works only between its start and expiry dates. An expired, not-yet-valid, or soon-to-expire certificate can trigger browser warnings and interrupt access to the website or API.
What to do next
Review the recorded evidence with a security specialist before using this result for a current decision.
Evidence and check scope
Check result
The certificate uses ECDSA-SHA256 with a 256-bit public key.
Why it matters
The certificate's public key and signature algorithm protect it from forgery. Keys that are too short or signatures based on obsolete algorithms provide less protection against modern attacks.
What to do next
Review the recorded evidence with a security specialist before using this result for a current decision.
Evidence and check scope
Check result
No independent abuse-list consensus was found across 5 definitive providers.
Why it matters
Security and email providers maintain DNS-based blacklists of IP addresses associated with spam, malware, or compromised systems. Several current, independent listings are a strong reason to investigate, although a shared IP can sometimes affect unrelated customers.
What to do next
Review the recorded evidence with a security specialist before using this result for a current decision.
Evidence and check scope
Check result
The scan recorded “Session cookies protected from scripts (HttpOnly)” as not applicable.
Why it matters
HttpOnly prevents browser scripts from directly reading a cookie. It does not fix script injection, but it makes theft of session and authentication cookies more difficult.
What to do next
Review the recorded evidence with a security specialist before using this result for a current decision.
Check result
The scan recorded “Cookies sent only over HTTPS (Secure)” as not applicable.
Why it matters
The Secure attribute prevents a browser from sending a cookie over unencrypted HTTP. Without it, session or authentication data may be exposed to someone observing the network.
What to do next
Review the recorded evidence with a security specialist before using this result for a current decision.
Check result
The scan completed without observing an exact product version that could be matched reliably to CVE records. This check is not applicable; it does not mean the system is free of vulnerabilities.
Why it matters
The detected product and version were compared with vulnerability records from the National Vulnerability Database (NVD). A match is a lead, not confirmation: the installed software may include vendor fixes or may differ from the version visible on the Internet.
What to do next
Review the recorded evidence with a security specialist before using this result for a current decision.
Evidence and check scope
Check result
The scan recorded “DMARC blocking policy” as not applicable.
Why it matters
A policy of quarantine or reject tells receiving services to move suspicious mail to spam or refuse it. A monitoring-only policy (p=none) records the problem but does not ask receivers to stop spoofed mail.
What to do next
Review the recorded evidence with a security specialist before using this result for a current decision.
References
Check result
The scan recorded “Valid DMARC configuration” as not applicable.
Why it matters
Receiving services may ignore a DMARC record that contains duplicate fields, invalid values, or is published at the wrong DNS name. An ignored record provides no reliable protection from domain impersonation.
What to do next
Review the recorded evidence with a security specialist before using this result for a current decision.
References
Check result
The result recorded “Insecure content on an HTTPS page” as passed at scan time.
Why it matters
An HTTPS page can still load scripts, frames, styles, or forms over unencrypted HTTP. An attacker on the network may alter that content and compromise the otherwise secure page.
What to do next
Review the recorded evidence with a security specialist before using this result for a current decision.
Evidence and check scope
Check result
The server presented 3 certificate(s).
Why it matters
The server must provide the intermediate certificates that connect its website certificate to a trusted provider. If any are missing, some browsers, mobile devices, or API clients may reject the connection.
What to do next
Review the recorded evidence with a security specialist before using this result for a current decision.
Evidence and check scope
Check result
The root page did not match a common automatic directory-index pattern.
Why it matters
When a web server automatically lists a directory, visitors may discover files that were never linked publicly, including backups, logs, or deployment artifacts.
What to do next
Review the recorded evidence with a security specialist before using this result for a current decision.
Evidence and check scope
Check result
No matching credential exposure records were found in the currently indexed intelligence data. This does not prove that no exposure exists.
Why it matters
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 next
Review the recorded evidence with a security specialist before using this result for a current decision.
Evidence and check scope
Check result
The scan recorded “Cross-site cookie protection (SameSite)” as not applicable.
Why it matters
SameSite limits when a browser includes cookies in requests started by another website. This helps prevent another site from silently making an authenticated request on a user's behalf.
What to do next
Review the recorded evidence with a security specialist before using this result for a current decision.
Check result
The scan recorded “SPF protection level” as not applicable.
Why it matters
The final SPF rule tells receiving services how confidently they should reject unlisted senders. A permissive result allows more spoofed mail to appear legitimate than a hard fail (-all).
What to do next
Review the recorded evidence with a security specialist before using this result for a current decision.
References
Check result
The scan recorded “Valid SPF configuration” as not applicable.
Why it matters
More than one SPF record, invalid terms, or too many DNS lookups can make SPF return a permanent error. Receiving services may then be unable to verify authorized senders.
What to do next
Review the recorded evidence with a security specialist before using this result for a current decision.
References
Check result
The result recorded “Exposed software version” as passed at scan time.
Why it matters
Exact web server or framework versions help attackers quickly look for known weaknesses that may apply. Hiding a version is not a substitute for patching, but unnecessary disclosure gives away useful targeting information.
What to do next
Review the recorded evidence with a security specialist before using this result for a current decision.
Check result
Found 2 authoritative name server(s).
Why it matters
Authoritative name servers tell visitors where the domain is hosted. Depending on only one server creates a single point of failure for the website and email.
What to do next
Review the recorded evidence with a security specialist before using this result for a current decision.
Evidence and check scope
Check result
The scan recorded “HSTS protection period” as not applicable.
Why it matters
The max-age value controls how long browsers remember to use HTTPS. A very short period provides limited protection, while includeSubDomains also covers every subdomain and can break one that does not support HTTPS.
What to do next
Review the recorded evidence with a security specialist before using this result for a current decision.
Check result
The scan recorded “DMARC monitoring reports” as not applicable.
Why it matters
DMARC aggregate reports show which systems send email using the domain and which messages fail verification. They help find both impersonation attempts and legitimate services that need correction.
What to do next
Review the recorded evidence with a security specialist before using this result for a current decision.
References
References
Evidence and check scope
References
Publish a DMARC record at _dmarc, begin by collecting reports, and confirm that legitimate senders pass before applying a blocking policy.
References
What to do
Set frame-ancestors in CSP to the required trusted sites, and keep X-Frame-Options for older browsers when appropriate.
Evidence and check scope
References
Send X-Content-Type-Options: nosniff on every response and return an accurate Content-Type.
Evidence and check scope
References
Evidence and check scope
Redirect every HTTP URL directly to its corresponding HTTPS URL without passing through another HTTP address.
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.
Evidence and check scope
What to do
Allow each sensitive browser feature only for the pages and trusted origins that require it, and disable the rest.
Evidence and check scope
References
Use strict-origin-when-cross-origin or a stricter Referrer-Policy, and avoid placing secrets in URLs.
Evidence and check scope
References
Evidence and check scope
References
References
14 additional evidence fields are not shown here.
References
14 additional evidence fields are not shown here.
14 additional evidence fields are not shown here.
References
4 additional evidence fields are not shown here.
Recently completed assessments, prioritizing websites with a similar sector, country or security grade for easier comparison.
India
