| URL is rejected | The address may be malformed, unsupported or missing a usable host. | Check copied characters, remove surrounding spaces and paste an ordinary full HTTP or HTTPS URL. |
| The score seems too high for a suspicious link | A deceptive page may lack known structural or reputation signals. | Do not trust the score alone; independently verify the sender and target domain. |
| A legitimate site receives a warning | Its domain may resemble another brand or use unusual redirects or recent registration. | Examine individual factors and corroborate the site identity through trusted sources. |
| Deep scan does not finish | Network timeouts, blocking, rate limits or unavailable services may interrupt checks. | Retry later or use browser-local signals plus separate trusted verification. |
| Redirect chain is incomplete | Some pages rely on JavaScript, login state, cookies or conditional redirects. | Treat the reported chain as an observed subset; avoid visiting the questionable URL to fill gaps. |
| Short link destination cannot be resolved | The shortener may block scanners, expire links or require additional interaction. | Do not infer safety; request the full destination from the sender via a trusted channel. |
| TLS certificate details are missing | The destination may be unreachable, block the scanner or not support a normal TLS handshake. | Verify the exact domain and use a known official site rather than bypassing security warnings. |
| DNS records are unavailable | The domain may not resolve or DNS queries may fail temporarily. | Recheck authoritative records when needed and treat missing context as unknown. |
| RDAP domain age is unknown | Registry data may be inaccessible, privacy-redacted or not applicable. | Do not invent a domain age or use missing registration details as conclusive evidence. |
| A DNSBL result looks incorrect | Shared hosting or outdated reports can create misleading blacklist associations. | Review the queried source and current IP mapping before making a blocking decision. |
| A phishing brand match looks wrong | Similarity algorithms can flag innocent names. | Compare the real registrable domain with the brand’s published address. |
| Unicode domain appears unfamiliar | Punycode decoding may expose non-Latin characters or an unusual script combination. | Check actual code points and confirm that this is the intended legitimate IDN. |
| A QR URL leads to an unexpected domain | The QR code may be replaced, misdirected or legitimately operated by a third party. | Confirm the destination and payment recipient with the venue or service before proceeding. |
| Bulk upload fails | The TXT/CSV format may be invalid or contain unsupported rows. | Use one valid URL per line or check the CSV column mapping and file encoding. |
| CSV exports contain extra characters | Commas, Unicode text or quoting can be interpreted incorrectly by the spreadsheet app. | Import as UTF-8 CSV and inspect quoted cells instead of removing security-relevant characters. |
| Report shows old results | Local history can preserve an earlier snapshot. | Run a fresh scan and record the observation time. |
| Browser history is missing | Private mode, storage cleanup or disabled history may remove stored checks. | Export needed reports outside browser storage while respecting sensitive URL confidentiality. |
| A URL includes a reset token | The URL itself contains secret information in its path or query string. | Do not submit it to a network-dependent service; navigate to the official recovery workflow. |
| Security-header grade is poor on a genuine site | The operator may not have deployed some recommended browser defenses. | Treat it as a configuration issue to review, not automatic evidence of fraud. |
| Certificate is valid but URL looks fraudulent | Attackers can obtain valid certificates for domains they control. | Prioritize exact domain verification and independent organizational confirmation. |
| IP location differs from company country | CDNs and global cloud infrastructure distribute traffic across regions. | Do not infer legitimacy or criminal intent from hosting geography alone. |
| One scan flags a redirect but another does not | Redirect rules can vary by country, time, device or browser session. | Consider both observations and avoid making a single-scan certainty claim. |
| Email provider disagrees with the result | Providers may use different intelligence feeds and detection policies. | Use layered evidence and avoid the link until a high-impact request is independently verified. |
| A site requests an OTP after a clean scan | URL risk analysis cannot authorize authentication requests. | Stop and open the official service directly; never disclose codes on an unexpected page. |