ScamLens analyzed akaka.dev using 90+ threat intelligence sources and assigned a trust score of 11/100, classifying it as dangerous.
Trust Score: 11/100
Risk Level: Dangerous
This domain already shows strong risk signals. Stop interacting, preserve the page, chat, phone, and payment evidence, and move into response or reporting immediately.
Quick Answer
This domain already shows strong risk signals. Stop interacting, preserve the page, chat, phone, and payment evidence, and move into response or reporting immediately.
Positive Signals
- +Google Safe Browsing: Safe
Concerns
- -3 security sources flagged as suspicious
- -Cross-domain redirect detected
Score Breakdown
Was this assessment accurate?
akaka.dev 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_browsingclean
- urlhausclean
- cloudflare_radarclean
- cert_transparencyclean
- alienvault_otxclean
- phishstatsclean
- virustotalflagged
- ipqsclean
- abuseipdbclean
- securitytrailsclean
- phishdestroyflagged
- threatfoxclean
- shodan_internetdbclean
- phishtankclean
- urlscanclean
- rdapclean
- maltiverseclean
- dns_securityclean
- wanted_domainsclean
- darkwebclean
- metamask_blocklistflagged
- 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
Redirect Chain
1 hopCross-domain redirect detected
This domain redirects to a different domain. This is commonly used by phishing sites to evade detection.
akaka.dev → myfritz.net
akaka.dev
Status: 301Final destination
gn3vixin0qmezlx8.myfritz.net
Server Information
- IP Address
- 93.203.0.249
- Hosting Provider
- Deutsche Telekom AG
- ASN
- AS3320 Deutsche Telekom AG
- Server Location
- Langen, Germany
- Organization
- Deutsche Telekom AG
Related Intelligence
Technical Details (DNS / Headers / Subdomains)
DNS Records
Email Security
SPF Not ConfiguredDMARC Not Configured| Type | Value |
|---|---|
| A | 93.203.0.249 |
| AAAA | 2003:ec:8fff:2fd9:e228:6dff:fec5:9ff6 |
| MX | 10 mail.akaka.dev |
| NS | 2-can.njalla.in |
| NS | 1-you.njalla.no |
| NS | 3-get.njalla.fo |
HTTP Security Headers
1/6max-age=15768000; includeSubDomains; preload
Channels / Subdomains
No data available
Community Reports
Log in to report and share your experience
Report & Take Down This Website
High-Risk Signals
The risk signals are strong enough. Move on evidence preservation, reporting, and victim response now
This result is no longer just a normal verification case. Moving the chat, phone, payment, and official-reporting path in parallel is usually more important than waiting for more data.
Recommended First
Move into the victim action plan
If you already paid, logged in, or installed tools, use the action plan first to prioritize containment and evidence work.
Move into the website-reporting flow
Move the site, payment evidence, chat trail, and contact points into the formal reporting path.
Add the chat, DM, and payment-pressure trail
Keep the Telegram, WhatsApp, social DM, and payment-pressure trail in the same timeline.
Check the callback number and SMS
If the actor also used calls, SMS, or one-time codes, verify that phone path next.
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.
If a loss already happened, move into the response flow now
Delay is the main risk with high-risk domains. Prioritize freezes, credential resets, reporting, and evidence preservation now.
If no loss happened yet, continue with the website-reporting and official-agency paths next.
Related Security Guides
Learn more about how to protect yourself from this type of threat.
Understanding this threat
FAQ
Is akaka.dev safe to visit?
akaka.dev received a trust score of 11/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 akaka.dev flagged by any threat databases?
akaka.dev was flagged by 3 out of 30+ threat intelligence sources. Specifically flagged by: virustotal, phishdestroy, metamask_blocklist. The detected threat categories include: general threat.
How old is akaka.dev?
Registration date information for akaka.dev is not publicly available through WHOIS records, which can itself be a risk indicator.
Does akaka.dev use HTTPS and have a valid SSL certificate?
ScamLens could not verify the SSL certificate details for akaka.dev during this scan. Treat this as unavailable evidence, not as proof that the site is safe or unsafe.
What security headers does akaka.dev implement?
akaka.dev is missing important security headers: Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, Strict-Transport-Security, Referrer-Policy, Permissions-Policy. Missing security headers can leave visitors vulnerable to cross-site scripting (XSS) and other web-based attacks.
What does the ScamLens community think about akaka.dev?
No community votes or reports have been submitted for akaka.dev yet. You can be the first to share your experience.
Where is akaka.dev hosted?
akaka.dev is hosted by Deutsche Telekom AG in Langen, Germany (ASN: ASAS3320 Deutsche Telekom AG).
Is this report useful?
Use this report to tell others to stop interacting now and move straight into containment, evidence preservation, and reporting.
Forward to your parents — they deserve to browse safely too.
Lost crypto to this scam?
We offer a paid forensic trace across 18 blockchains with sanctions screening — from $99.
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: August 7, 2026