qevvax.courses is a phishing page detected by PhishDestroy on 2026-06-10. Risk: critical (100/100). Registrar: Sav.com. Status: Last known active. Hosting: Google LLC. PhishDestroy sent 1 abuse report. VirusTotal: 12/91 engines flag it. Listed on Spamhaus DBL. Do not enter credentials or connect a wallet.
Security engines reporting a detection: 12. Exercise extreme caution — do not enter credentials or personal information.
ABUSE NOTICE · 7D+ OPEN
Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse.support@h4g.co.
The latest stored availability evidence still shows the domain reachable; 4 months has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations.
This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
The domain qevvax.courses is currently active and flagged as a high-risk generic phishing threat targeting users of educational or course-related platforms. Analysis indicates the domain does not impersonate a specific brand but instead mimics a generic course portal, likely designed to harvest credentials or distribute malicious content under the guise of legitimate educational resources. The domain remains operational as of the latest verification, posing an ongoing risk to unsuspecting users. Infrastructure analysis reveals the domain resolves to the IP address 34.76.205.124 and was registered on February 18, 2026, through Sav.com LLC. Security vendors have flagged qevvax.courses as malicious, with 9 out of 95 VirusTotal engines detecting it as a threat. The domain appears on one security blocklist and lacks an SSL certificate, further indicating its suspicious nature. The page title, 'Index of /', suggests an exposed directory listing, which is atypical for legitimate educational portals and may be used to host phishing kits or malware payloads. Current status confirms the domain remains active and unmitigated. Organizations and individuals are advised to block access to qevvax.courses at the network level and update endpoint protection rules to include this domain. Users should be educated to recognize generic phishing tactics, particularly those leveraging educational themes. Security teams are recommended to monitor for connections to the associated IP 34.76.205.124 and investigate any related network traffic for signs of compromise or data exfiltration.
Collected source details
Stored page, network and scanner observations, grouped by source and observation time.
No. PhishDestroy classifies qevvax.courses as a phishing page (risk: critical, 100/100); it was first detected on 2026-06-10. VirusTotal: 12/91 engines flag it. Listed on Spamhaus DBL. Treat the site as unsafe.
Is qevvax.courses safe to connect a wallet?
No. Do not connect a wallet, sign messages or approve tokens on qevvax.courses. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
What should I do if I used qevvax.courses?
Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.
RegistrationCreated Feb 18, 2026 (246d)—Expires Feb 18, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedJun 10, 2026
DOM Analysisanalyzed Oct 9, 2026score 98/100
Submitted URLhttp://qevvax.courses/75775dd
Case ID
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.
Accountability draft
Nothing is sent automatically.
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
34.76.205.124
Network ASN
AS396982
Organization
Google Cloud (europe-west1)
Observed location
Brussels, BE
Server header
Caddy
Nameservers 1
ns2.all-harmless.domains
Location describes the IP network.
TLS certificate
Issuer
Let's Encrypt
Valid until
2026-09-05 00:00:00
Validity
Stored certificate expired
Collection time
2026-10-22 16:02:11 UTC
Collection source
PhishDestroy collector
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observationLive contentOrdinary HTTP content served90%2026-10-22 10:34:18 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-22 10:34:18 UTClast content: 2026-10-22 10:34:18 UTC
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.
Technologies · 1 identified
A
Apache HTTP Server
Web servers
Apache is a free and open-source cross-platform web server software.
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Infrastructure map · qevvax.courses
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.
7 evidence signal groups linked1 stored notification recordsLast known active
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 qevvax.courses)
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.
(US)
