ScamLens analyzed bad12c4de4a0.ngrok.io using 90+ threat intelligence sources and assigned a trust score of 63/100, classifying it as moderate risk.
Trust Score: 63/100
Risk Level: Caution
This result is still in the investigation range, so the domain alone is not enough for a decision. The next step is to cross-check the email, phone number, company identity, and scenario.
Quick Answer
This result is still in the investigation range, so the domain alone is not enough for a decision. The next step is to cross-check the email, phone number, company identity, and scenario.
Positive Signals
- +Google Safe Browsing: Safe
- +HTTPS encryption supported
Concerns
- -2 security sources flagged as suspicious
Score Breakdown
Was this assessment accurate?
Mixed signals on bad12c4de4a0.ngrok.io
We did not find direct threat-feed hits, but coverage is thin or other signals warrant care.
- Verify the company exists offlineSearch the registered company name + 'reviews' or 'scam'. Real businesses leave a long trail of independent mentions.
- Pay only via reversible methodsUse credit cards or PayPal Goods & Services. Avoid wire transfers, crypto, gift cards — those are non-reversible.
- Confirm the contact detailsLook up the phone number and email address separately. Free webmail addresses or VoIP numbers are a red flag.
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 — 2 flagged this domain
Show source breakdown
Threat-intelligence sources
Checked across 28 sources — 2 flagged this domain
- safe_browsingclean
- 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
- 3.134.39.220
- Hosting Provider
- Amazon.com, Inc.
- ASN
- AS16509 Amazon.com, Inc.
- Server Location
- Dublin, United States
- Organization
- AWS EC2 (us-east-2)
Related Intelligence
Technical Details (DNS / Headers / Subdomains)
DNS Records
Email Security
SPF Not ConfiguredDMARC Not Configured| Type | Value |
|---|---|
| A | 3.134.39.220 |
| A | 3.134.125.175 |
| A | 3.14.182.203 |
| A | 3.17.7.232 |
| A | 3.22.30.40 |
| AAAA | 2600:1f16:d83:1201:6cd5:bf8e:1af8:c9da |
| AAAA | 2600:1f16:d83:1201:b91d:e4e5:6e14:df4 |
| AAAA | 2600:1f16:d83:1202:318e:b97e:3530:436a |
| AAAA | 2600:1f16:d83:1200:19d9:6ba:5b9f:5b9 |
| AAAA | 2600:1f16:d83:1202:586c:b39b:b5a4:d61f |
HTTP Security Headers
Channels / Subdomains
No data available
Community Reports
Log in to report and share your experience
Report & Take Down This Website
Continue Investigating
The result is still in the investigation range. Cross-check the email, phone, and entity data next
Medium-risk domains are easiest to misread when you only check one signal. The decision gets more reliable once you cross-check the email, phone number, company identity, and business scenario together.
Recommended First
Analyze the related email or invoice
Confirm whether the billing notice, restriction alert, or support email actually matches the site.
Check the company or seller identity
Compare the domain against the company identity, merchant profile, or hiring details.
Check the related phone number
If the actor wants a callback, phone verification, or one-time code readout, verify that number next.
Open the matching scenario guide
If the case involves investing, shopping, or recovery services, verify it through the matching scenario guide.
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.
Verify the related evidence objects first
Medium-risk cases are easiest to misread when you only check one signal. Verify the email, phone, and entity before deciding whether to report or stop the transaction.
If you already paid or exposed account access, skip the investigation loop and move into the action plan.
Related Security Guides
Learn more about how to protect yourself from this type of threat.
Understanding this threat
FAQ
Is bad12c4de4a0.ngrok.io safe to visit?
bad12c4de4a0.ngrok.io received a trust score of 63/100 from ScamLens. Some minor concerns were identified but no critical threats were found. Exercise normal caution.
Was bad12c4de4a0.ngrok.io flagged by any threat databases?
bad12c4de4a0.ngrok.io was flagged by 2 out of 30+ threat intelligence sources. Specifically flagged by: dns_security, phishing_database. The detected threat categories include: general threat.
How old is bad12c4de4a0.ngrok.io?
Registration date information for bad12c4de4a0.ngrok.io is not publicly available through WHOIS records, which can itself be a risk indicator.
Does bad12c4de4a0.ngrok.io use HTTPS and have a valid SSL certificate?
ScamLens could not verify the SSL certificate details for bad12c4de4a0.ngrok.io during this scan. Treat this as unavailable evidence, not as proof that the site is safe or unsafe.
What security headers does bad12c4de4a0.ngrok.io implement?
No security header information was available for bad12c4de4a0.ngrok.io.
What does the ScamLens community think about bad12c4de4a0.ngrok.io?
No community votes or reports have been submitted for bad12c4de4a0.ngrok.io yet. You can be the first to share your experience.
Where is bad12c4de4a0.ngrok.io hosted?
bad12c4de4a0.ngrok.io is hosted by Amazon.com, Inc. in Dublin, United States (ASN: ASAS16509 Amazon.com, Inc.).
Is this report useful?
Use this report to prompt others to keep cross-checking the email, phone number, and entity details instead of clearing it too early.
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