ScamLens analyzed aiyoav.xyz using 90+ threat intelligence sources and assigned a trust score of 28/100, classifying it as high risk.
Trust Score: 28/100
Risk Level: High Risk
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
- + HTTPS encryption supported
Concerns
- - Domain registered only 2 month ago
- - 2 security sources flagged as suspicious
Score Breakdown
Was this assessment accurate?
AI Risk Assessment
High RiskWhat matters right now
With a high-risk result, the priority is not reading more pages. It is immediate containment, credential resets, evidence preservation, and the reporting path.
aiyoav.xyz presents mixed signals. Safe Browsing is clean 1 and 26 of 28 threat feeds responded clean 3, but 2 feeds flagged concerns: shodan_internetdb detected suspicious ports 2 and dns_security reported DNS malware blocking 2. [FACT] The domain is 69 days old 4, reducing extreme newness risk, but operates on .xyz, a high-abuse TLD 5. [INFERENCE] The dual threat feed flags (suspicious ports + DNS malware association) suggest potential infrastructure misuse or compromise, despite no brand impersonation detected. The absence of community reports 3 leaves attribution uncertain. [UNVERIFIED] The nature of the suspicious ports and DNS malware context requires deeper investigation—this could indicate hosting abuse, C2 infrastructure, or a false positive from security tools.
Recommendation
Treat as suspicious pending verification. Do not interact with this domain. [INFERENCE] Cross-reference the flagged threat feeds (Shodan and DNS security providers) for specifics on port activity and malware associations. If you received this domain unsolicited, report it to the registrar (Namecheap) 4. Legitimate users should contact the domain owner directly via alternative verified channels to clarify its purpose.
Sources
- Threat intelligence feeds (2 flagged)Threat intel
shodan_internetdb (SUSPICIOUS_PORTS); dns_security (DNS_BLOCKED_MALWARE)
- 26/28 threat feeds responded cleanThreat intel
- WHOIS registration dataWHOIS
Registered 2026-02-13T12:03:16.0Z (69 days ago), registrar: Namecheap
- TLD risk classification: .xyz (high risk)Analysis
Based on APWG / Spamhaus / Interisle 2024 abuse rankings
Powered by ScamLens AI· Check sources to verify important claims
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
- Created
- February 13, 2026
- Expires
- February 13, 2027
- Domain Age
- 2 months
- DNSSEC
- Disabled
- Nameservers
- evan.ns.cloudflare.com, margaret.ns.cloudflare.com
- Domain Status
- server transfer prohibited client transfer prohibited
SSL/TLS Certificate
No data available
Server Information
- IP Address
- 104.21.53.67
- Hosting Provider
- Cloudflare, Inc.
- ASN
- AS13335 Cloudflare, Inc.
- Server Location
- Toronto, Canada
- Organization
- Cloudflare, Inc.
Related Intelligence
Technical Details (DNS / Headers / Subdomains)
DNS Records
Email Security
SPF Not Configured DMARC Not Configured| Type | Value |
|---|---|
| A | 104.21.53.67 |
| A | 172.67.209.171 |
| AAAA | 2606:4700:3033::ac43:d1ab |
| AAAA | 2606:4700:3031::6815:3543 |
| NS | evan.ns.cloudflare.com |
| NS | margaret.ns.cloudflare.com |
HTTP Security Headers
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.
FAQ
Is aiyoav.xyz safe to visit?
aiyoav.xyz received a trust score of 28/100 from ScamLens, indicating several security concerns. 2 threat intelligence sources flagged this domain. Proceed with extreme caution.
Was aiyoav.xyz flagged by any threat databases?
aiyoav.xyz was flagged by 2 out of 90+ threat intelligence sources. Specifically flagged by: shodan_internetdb, dns_security. The detected threat categories include: general threat.
How old is aiyoav.xyz?
aiyoav.xyz was first registered on February 13, 2026, making it approximately 2 months old. While relatively new, the domain has been active for several months.
Does aiyoav.xyz use HTTPS and have a valid SSL certificate?
aiyoav.xyz does not appear to have a valid SSL certificate configured. This means data transmitted to and from this site is not encrypted, which is a significant security concern.
What security headers does aiyoav.xyz implement?
aiyoav.xyz 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 aiyoav.xyz?
No community votes or reports have been submitted for aiyoav.xyz yet. You can be the first to share your experience.
Where is aiyoav.xyz hosted?
aiyoav.xyz is hosted by Cloudflare, Inc. in Toronto, Canada (ASN: ASAS13335 Cloudflare, Inc.).
What should I do about aiyoav.xyz?
Treat as suspicious pending verification. Do not interact with this domain. [INFERENCE] Cross-reference the flagged threat feeds (Shodan and DNS security providers) for specifics on port activity and malware associations. If you received this domain unsolicited, report it to the registrar (Namecheap) [4]. Legitimate users should contact the domain owner directly via alternative verified channels to clarify its purpose.
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.
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: April 10, 2026