ScamLens analyzed autobaenasl.com using 90+ threat intelligence sources and assigned a trust score of 58/100, classifying it as moderate risk.
Trust Score: 58/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
- + Valid SSL certificate
- + HTTPS encryption supported
Concerns
- - Domain registered only 2 month ago
- - 2 security sources flagged as suspicious
Score Breakdown
Was this assessment accurate?
Mixed signals on autobaenasl.com
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.
Threat-intelligence sources
Checked across 27 sources — 2 flagged this domain
Show source breakdown
Threat-intelligence sources
Checked across 27 sources — 2 flagged this domain
- safe_browsing clean
- urlhaus clean
- cloudflare_radar clean
- cert_transparency clean
- alienvault_otx info
- phishstats clean
- virustotal clean
- ipqs clean
- abuseipdb clean
- securitytrails clean
- phishdestroy clean
- threatfox clean
- shodan_internetdb clean
- phishtank clean
- urlscan clean
- rdap clean
- maltiverse clean
- dns_security flagged
- wanted_domains clean
- darkweb clean
- hagezi_tif flagged
- openphish clean
- scam_blocklist clean
- maltrail clean
- crypto_scam_feed clean
- phishing_army clean
- red_flag_domains clean
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
- Registrar
- NameCheap, Inc.
- Created
- March 21, 2026
- Expires
- March 21, 2027
- Domain Age
- 2 months
- DNSSEC
- Disabled
- Nameservers
- DNS1.NAMECHEAPHOSTING.COM, DNS2.NAMECHEAPHOSTING.COM
- Domain Status
- client transfer prohibited
SSL/TLS Certificate
- Issuer
- C=GB, O=Sectigo Limited, CN=Sectigo Public Server Authentication CA DV R36
- Valid From
- March 21, 2026
- Valid To
- October 5, 2026
- Status
- Valid
Server Information
- IP Address
- 192.64.117.129
- Hosting Provider
- Namecheap
- ASN
- AS22612 Namecheap, Inc.
- Server Location
- Phoenix, United States
- Organization
- Web-hosting.com
Related Intelligence
Technical Details (DNS / Headers / Subdomains)
DNS Records
Email Security
SPF Configured DMARC Configured| Type | Value |
|---|---|
| A | 192.64.117.129 |
| MX | 5 mx1-hosting.jellyfish.systems |
| MX | 10 mx2-hosting.jellyfish.systems |
| MX | 20 mx3-hosting.jellyfish.systems |
| NS | dns1.namecheaphosting.com |
| NS | dns2.namecheaphosting.com |
| TXT | v=spf1 +a +mx +ip4:192.64.117.3 +ip4:192.64.117.15 include:spf.web-hosting.com ~all |
HTTP Security Headers
0/6Channels / Subdomains
1 subdomains found| Subdomain | Title |
|---|---|
| www.autobaenasl.com | - |
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.
FAQ
Is autobaenasl.com safe to visit?
autobaenasl.com received a trust score of 58/100 from ScamLens. Some minor concerns were identified but no critical threats were found. Exercise normal caution.
Was autobaenasl.com flagged by any threat databases?
autobaenasl.com was flagged by 2 out of 30+ threat intelligence sources. Specifically flagged by: dns_security, hagezi_tif. The detected threat categories include: general threat.
How old is autobaenasl.com?
autobaenasl.com was first registered on March 21, 2026, making it approximately 3 months old. While relatively new, the domain has been active for several months.
Does autobaenasl.com use HTTPS and have a valid SSL certificate?
autobaenasl.com uses an SSL certificate issued by C=GB, O=Sectigo Limited, CN=Sectigo Public Server Authentication CA DV R36, valid until October 5, 2026. The certificate is from a commercial certificate authority, which provides a higher level of validation.
What security headers does autobaenasl.com implement?
autobaenasl.com 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 autobaenasl.com?
No community votes or reports have been submitted for autobaenasl.com yet. You can be the first to share your experience.
Where is autobaenasl.com hosted?
autobaenasl.com is hosted by Namecheap in Phoenix, United States (ASN: ASAS22612 Namecheap, 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: June 19, 2026