How to fix: Potential phishing lookalike domain detected in links
Outgoing links or redirects reference domains that closely resemble known trusted brands via typosquatting or homoglyph substitution.
Why it matters
Links to phishing lookalike domains can redirect users to malicious sites that steal credentials or install malware, especially dangerous if these links appear in official pages and users assume they are legitimate.
Outbound links should be audited to ensure they do not reference typosquatted or lookalike domains.
How to fix it
- 1Audit all outbound links for lookalike domains
- 2Use rel="noopener noreferrer" on all external links
- 3Consider monitoring your brand name for lookalike domain registrations
Code examples
Register lookalike domains defensively
// Register common typosquatting variants of your domain:
// examp1e.com, exarnple.com, example.co, example.net
// Then redirect all variants to your canonical domain.
// nginx: redirect lookalike to canonical
server {
server_name examp1e.com;
return 301 https://example.com$request_uri;
}References
Detected automatically by VulnRadar. The check id is phishing-lookalike-domain, stable across every scan so you can filter or diff on it.
More content checks
- MediumPotential Open Redirect Parameters
- HighDirectory Listing Appears Enabled
- MediumSensitive File References Detected
- HighPotentially Outdated JavaScript Libraries
- Inforobots.txt Present - Review Manually
- InfoCMS / Technology Fingerprinting
- MediumPotentially Dangerous Inline JavaScript
- LowServer version disclosed in response header
Questions
- How severe is Potential phishing lookalike domain detected in links?
- VulnRadar rates this medium severity in the content category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id phishing-lookalike-domain, which stays the same between runs so you can filter, diff, or gate CI on it.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.