The domain protocol-v4-aave.limited was registered on 12 October 2025 through Atak Domain. Infrastructure analysis shows it resolves to the IPv4 address 196.251.66.67, which is geolocated to the Netherlands. The domain is hosted on nameservers ns1.plesk.axxel1.com and ns2.plesk.axxel1.com, and the web server returns the page title “Axxel Plesk”. No TLS certificate is presented, indicating the site operates without HTTPS. The site is classified as a crypto‑related brand impersonation campaign targeting Aave, as indicated by the “Impersonates: Aave” label and the “Crypto Scam” tag.
The domain appears on a single security blocklist and is actively blocked by PhishDestroy. VirusTotal analysis recorded three positive detections out of ninety‑five scanners, confirming malicious activity. Gridinsoft assigns a trust score of 0 out of 100, reinforcing the low reputation. Because the site is currently taken offline, content analysis is limited to the page title; the exact phishing landing page or credential‑stealing mechanisms have not been observed. No Safe Browsing, OTX, or additional blocklist entries are reported, leaving the broader distribution network unknown.
Defenders should add protocol‑v4‑aave.limited and its resolving IP 196.251.66.67 to deny lists across perimeter and endpoint controls. Monitoring of the associated nameservers and the Atak Domain registrar for new domains with similar naming patterns is advised. Given the absence of TLS, any attempt to serve content over HTTPS would be a clear indicator of a shift in tactics. Continuous re‑scanning with multi‑engine services is recommended to capture any future changes.
RegistrationCreated Oct 12, 2025 —Expires Oct 12, 2026
Time to First Unavailability213 days
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedOct 13, 2025
DOM Analysisanalyzed Apr 23, 2026score 56/1001 brand signal
Submitted URLhttp://protocol-v4-aave.limited/
ICANN OVERSIGHT
Accreditation and RAA context
Registrar accreditation and DNS abuse obligations
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-19 01:09:40 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-06-01 10:15:49 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-06-01 10:15:49 UTC → 2026-09-30 16:14:55 UTC · 2,909.99hmidpoint estimate ≈ 2026-08-01 01:15:22 UTC · precision very low · basis bounded
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Check for cloaking
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
No cloaking flag in this check
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='protocol-v4-aave.limited', port=80): Max retries exceeded with url: / (Caused by NewConnec
protocol-v4-aave.limited
Stored observation history10
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Infrastructure map · protocol-v4-aave.limited
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Content matches3
Same favicon hash or the same page title as this host.
4 evidence signal groups linked0 stored notification recordsContent unavailable
Listed domains receive at least one abuse report; this entry has no retained notification history.
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident
Recommendations & Advice for Victims
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
What should I do immediately?
Urgent
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Change all passwords — email, exchange accounts, anything that shares the same password
Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
Freeze cards if you entered banking details on the phishing site
What information should I collect for my report?
FBI guidelines
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Exact dates & times — of each transaction and first contact with scammer
Screenshots — scam website, chat messages, emails, wallet transactions, social media
All URLs & domains used by the scammer (including protocol-v4-aave.limited)
Communications — emails, texts, phone numbers, usernames the scammer used
Even if you don't have all details — file a report anyway. Partial information still helps investigations.
Where should I report the scam?
FBI IC3 — Internet Crime Complaint Center (US federal reporting)
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
Local police — creates an official record, even if they can't act immediately
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
How do phishing scams typically work?
Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
Bookmark official sites — never click links from emails, DMs, or ads
Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
"Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines
About this reportSources, observation dates and corrections
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.
(TR)
