ScamLens analyzed badge-to-submit.github.io using 90+ threat intelligence sources and assigned a trust score of 10/100, classifying it as dangerous.
Trust Score: 10/100
Risk Level: Dangerous
This domain behaves more like an impersonation or spoofing entry point. Do not log in, pay, or call any number shown on the site before you preserve the spoofing and communication evidence.
Quick Answer
This domain behaves more like an impersonation or spoofing entry point. Do not log in, pay, or call any number shown on the site before you preserve the spoofing and communication evidence.
Positive Signals
- +Globally recognized website
- +HTTPS encryption supported
Concerns
- -Google Safe Browsing: Flagged as dangerous
- -3 security sources flagged as suspicious
Score Breakdown
Was this assessment accurate?
badge-to-submit.github.io is confirmed malicious
Multiple threat-intelligence feeds agree this domain is dangerous. Treat any data you entered as compromised.
- Close the tab immediatelyContinued browsing increases the chance of drive-by downloads, exploit kits, or session hijacking.
- Run a full antivirus / malware scanIf the site loaded scripts, scan your device. Update your OS and browser to the latest version first.
- Change passwords for any account you enteredRotate the password and enable two-factor authentication on the real site. Watch for unauthorised charges over the next 30 days.
- Report the incidentReporting helps blocklists update faster and protects other potential victims.
Trust but verify — open this domain on unrelated security services and compare the verdict.
Sign in to run the AI risk analysis
The threat-intelligence signals below are available to everyone. The plain-language AI risk summary is generated on demand for signed-in users — sign in (free) to run it for this domain.
Threat-intelligence sources
Checked across 28 sources — 3 flagged this domain
Show source breakdown
Threat-intelligence sources
Checked across 28 sources — 3 flagged this domain
- safe_browsingflagged
- urlhausclean
- cloudflare_radarclean
- cert_transparencyclean
- alienvault_otxclean
- phishstatsclean
- virustotalclean
- ipqsclean
- abuseipdbclean
- securitytrailsclean
- phishdestroyclean
- threatfoxclean
- shodan_internetdbclean
- phishtankclean
- urlscanclean
- rdapclean
- maltiverseclean
- dns_securityflagged
- wanted_domainsclean
- darkwebclean
- phishing_databaseflagged
- openphishclean
- scam_blocklistclean
- maltrailclean
- crypto_scam_feedclean
- phishing_armyclean
- hagezi_tifclean
- red_flag_domainsclean
ScamLens aggregates real-time signals from 90+ commercial and open-source threat-intelligence providers including Google Safe Browsing, VirusTotal, PhishTank, URLhaus, ThreatFox, Cloudflare Radar, OTX, IPQS, GoPlus, Honeypot.is, and more. A flagged signal is evidence; the absence of flags is not proof of safety. Use the signals below alongside community reports to decide.
Advanced Scan
Comprehensive data lookup across premium sources
- Website history verification
- Detailed WHOIS information
- Reverse WHOIS association
- Traffic rank analysis
- Company registration check
AI Deep Investigation
Cross-check the story, claims, and supporting evidence before you decide
- Everything in Advanced Scan
- AI website content analysis
- AI cross-reference verification
- Claim authenticity validation
- Detailed report with evidence
Comprehensive Investigation
Full-spectrum investigation with company deep search & social intelligence
- Everything in Deep Investigation
- AI company background search
- Social media intelligence
- Detailed suspicious point analysis
- Event timeline & entity connections
This analysis is for informational purposes only and does not constitute a legal determination.
Security Sources
Domain Information
- DNSSEC
- Disabled
SSL/TLS Certificate
No data available
Server Information
- IP Address
- 185.199.110.153
- Hosting Provider
- Fastly, Inc.
- ASN
- AS54113 Fastly, Inc.
- Server Location
- San Francisco, United States
- Organization
- GitHub, Inc
Related Intelligence
Technical Details (DNS / Headers / Subdomains)
DNS Records
Email Security
SPF Not ConfiguredDMARC Not Configured| Type | Value |
|---|---|
| A | 185.199.110.153 |
| A | 185.199.108.153 |
| A | 185.199.109.153 |
| A | 185.199.111.153 |
| AAAA | 2606:50c0:8003::153 |
| AAAA | 2606:50c0:8000::153 |
| AAAA | 2606:50c0:8001::153 |
| AAAA | 2606:50c0:8002::153 |
HTTP Security Headers
Channels / Subdomains
No data available
Community Reports
Log in to report and share your experience
Report & Take Down This Website
Impersonation / Spoofing Risk
This domain behaves more like an impersonation entry point. Preserve the spoofing and communication evidence first
If the domain is impersonating a brand, support flow, or official login, the key is to keep the domain, landing page, email, chat, and payment path inside one case package.
Recommended First
Move into the website-reporting flow
Use the reporting path first to preserve the domain, screenshots, chat trail, and payment-page evidence.
If you were affected, move into the action plan
If you already logged in, paid, installed software, or shared data, use the victim action plan to prioritize the response.
Verify the impersonated brand or entity
Confirm exactly which platform, merchant, or support identity is being spoofed.
Add the email and chat evidence
Preserve the email, support conversation, and any callback instructions together.
The results are based on multiple third-party data sources and AI models. False positives or negatives may occur. This report should not be used as the sole basis for any decision. Please verify with additional sources.
Preserve the account and payment evidence first
If you already logged in, paid, or shared data, move into the victim action plan first and then complete the formal report.
For impersonation sites, the priority is not more browsing. It is evidence preservation and loss containment.
Related Security Guides
Learn more about how to protect yourself from this type of threat.
Understanding this threat
FAQ
Is badge-to-submit.github.io safe to visit?
badge-to-submit.github.io received a trust score of 10/100 from ScamLens, indicating high risk. 3 threat intelligence sources flagged this domain as potentially dangerous. We strongly advise against visiting or sharing personal information.
Was badge-to-submit.github.io flagged by any threat databases?
badge-to-submit.github.io was flagged by 3 out of 30+ threat intelligence sources. Specifically flagged by: safe_browsing, dns_security, phishing_database. The detected threat categories include: general threat.
How old is badge-to-submit.github.io?
Registration date information for badge-to-submit.github.io is not publicly available through WHOIS records, which can itself be a risk indicator.
Does badge-to-submit.github.io use HTTPS and have a valid SSL certificate?
ScamLens could not verify the SSL certificate details for badge-to-submit.github.io during this scan. Treat this as unavailable evidence, not as proof that the site is safe or unsafe.
What security headers does badge-to-submit.github.io implement?
No security header information was available for badge-to-submit.github.io.
What does the ScamLens community think about badge-to-submit.github.io?
No community votes or reports have been submitted for badge-to-submit.github.io yet. You can be the first to share your experience.
Where is badge-to-submit.github.io hosted?
badge-to-submit.github.io is hosted by Fastly, Inc. in San Francisco, United States (ASN: ASAS54113 Fastly, Inc.).
Is this report useful?
Use this report to warn others to stop logging in, paying, or contacting the listed support before they verify it.
Forward to your parents — they deserve to browse safely too.
About this analysis
This report is generated from real-time data across 90+ threat intelligence sources, combined with AI analysis and community feedback.
Learn about our scoring methodology | Last analyzed: July 26, 2026