Skip to security report
Domain security report
basevexora.io favicon

basevexora.io

“Basevexora | Homepage”

Threat verdict
Assessment sources

Assessment based on the stored source evidence below. Review sources →

Availability Last known active Latest stored reachability observation Observed · HTTP probe
VirusTotal detections: 6/89 Spamhaus DBL: DBL_PHISH Stored blocklist matches: 2 Automated brand label: MetaMask
OTX: 4 refs Sep 9, 2026 MetaMask
API
Registrar
Namecheap
Resolved IP
63.250.38.225
Registered
May 20, 2025
2 sources
Stored TLS certificateHostname mismatchReview certificate names and collection time
This domain has been flagged as malicious
Security engines reporting a detection: 6. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
Additional indicators at a glance
Spamhaus DBL
DBL_PHISH
VirusTotal
VirusTotal
6 det.
OTX references
URLScan
URLScan
TLS Certificate
Expired or unverified
Age
1.4 yr
Observed status
Last known active 302
PhishDestroy
DestroyList
Listed

Source evidence

8 · sources

These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.

VirusTotal

6 / 89

Report
Interpretation & limits

Engine detections from this stored analysis. Vendors and collection times may differ from other sources.

Public blocklists

2 external matches

Details
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Spamhaus DBL

DBL_PHISH

Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

OTX

4 community references

Report
Interpretation & limits

Community publication references, not a vendor verdict or evidence of a common operator.

CF Radar

provider verdict: clean

Observation time not recorded
Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

URLScan capture

stored report

View stored capture ↗
Report
Interpretation & limits

A preserved page image documents what the collector received; a capture is not a safety verdict.

URLScan verdict

Analysis completed

Report
Interpretation & limits

This is the recorded automated analysis. Completion alone is not a safety verdict.

Google Safe Browsing

Checked; no threat flag recorded

Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Evidence Summary

Critical
VirusTotal
6/89
OTX
4 community refs
URLScan
Stored capture

Stored narrative · generated . Provider checks below retain their own observation dates.

Assessment

Stored evidence for basevexora.io: VirusTotal recorded 1 detections among 89 scanners on 2026-09-09. That ratio reproduces the stored check in its original units and is not converted into another measure. MetaMask and SEAL appear as named external blocklist observations for basevexora.io. Each item in this report remains at the scope supplied by its dated source record.

Read the full analysis6

Detection Evidence

VirusTotal records 1 detections among 89 scanners in the stored snapshot dated 2026-09-09. The numerator describes scanners that produced detections, while the denominator describes scanners included in that check. The reverse order would materially alter the stored result. The VirusTotal snapshot dated 2026-09-09 supplies no common rationale covering the included scanners, and this report adds none. A later VirusTotal snapshot may contain different values, so any comparison should preserve the exact ratio and date of each snapshot.

Source Context

MetaMask and SEAL are recorded as named external blocklist observations for basevexora.io in the snapshot dated 2026-09-09. The stored MetaMask and SEAL blocklist records supply names and entries, but they supply no shared method or common rationale. PhishDestroy’s catalogue also contains basevexora.io as a publisher record. That PhishDestroy record is counted separately from the MetaMask and SEAL external blocklist observations. This separation keeps the origin of every entry visible and prevents a single stored item from being counted again under another source label.

Reachability and Timeline

The record first observed basevexora.io on 2026-09-09. The MetaMask and SEAL blocklist snapshot is dated 2026-09-09 and remains a separate event in the stored timeline. The registration date is separately recorded as 2025-05-20. A URLScan reference was stored on 2026-09-09 as a dated artifact for review. Each timestamp qualifies only the adjacent observation in this timeline. Later collection results should be compared with these dated values without replacing the earlier snapshot.

Registration and Infrastructure

For basevexora.io, the registrar field records NAMECHEAP INC; this is kept as an exact source value. The source stores 63.250.38.225 as the observed address in this record. The registration date for basevexora.io is recorded as 2025-05-20. These fields preserve registration, network, and certificate context stored in this record. The report preserves each label and number as a separate source value instead of combining them into an invented aggregate. Keeping the fields separate leaves every infrastructure value traceable to the record that supplied it.

Conclusion

The basevexora.io record states that VirusTotal recorded 1 detections among 89 scanners on 2026-09-09. MetaMask and SEAL remain named blocklist observations from the snapshot dated 2026-09-09. PhishDestroy remains a separate publisher catalogue entry in the stored record. For basevexora.io, the registrar field records NAMECHEAP INC; this remains separate from the other source fields. The observed address field in this record contains 63.250.38.225. The supported conclusion is bounded to the exact stored observations for basevexora.io. Any statement beyond those source values would require additional dated material.

Recommended Actions

Avoid submitting sensitive information to basevexora.io during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain basevexora.io as an exact indicator and preserve relevant DNS, proxy, and endpoint records. Compare later VirusTotal snapshots and MetaMask and SEAL blocklist records with the dated values above instead of replacing them. Keep each later observation with its source date so changes remain visible during follow-up review. If a defensive rule is needed, keep its scope to basevexora.io. The stored record does not justify extending that rule to 63.250.38.225 or to other infrastructure records.

Data coverage & collection21 · datasets with records / 10 · not recorded

What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.

Recorded dataPartial recordUTC
VirusTotal
6 / 89 · engine detections
URLScan analysis
Automated verdict retained
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
4 · community references
External blocklists
2 · external matches
Cloudflare Radar
cleanCollection time not recorded
Spamhaus DBL
DBL_PHISH
Domain registration
NAMECHEAP INCCollection time not recorded
Network & DNS
63.250.38.225 · 2 · nameserversCollection time not recorded
TLS certificate
Sectigo Limited / Sectigo Public Server Authentication CA DV R36
Page captures
2 · retained captures
Page analysis
1 · automated brand labels
Observed indicators
0 · wallet / Telegram indicators
Detection & evasion
Stored browser and crawler comparison
PageSpeed performance
56/100 · mobile performance
Recorded subdomains
1 · retained hostnamesCollection time not recorded
Availability history
28 · stored state changes
Source observation history
2 · stored source events
Lookalike relationships
79 · retained relationshipsCollection time not recorded
IP reputation
Network-level observations
Wayback archive
Archive link retained
Not recorded in this report 10

These checks have no retained result. This does not mean they passed or that a scan is running.

  • URLQuery
  • PhishStats
  • DNS security filters
  • Gridinsoft
  • Scamadviser
  • HTML archives
  • Site configuration files
  • Response records
  • Community reports
  • Chainabuse records
Download the dated observations and supporting metadata.
Blocklist records2 · external source matches

Public Blocklist Status

Domain, network & archiveNAMECHEAP INC · 63.250.38.225 · DNS, TLS and retained responses

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Reputation abuse score 2/100 1 report PhishingBad Web Bot checked Oct 10, 2026
OTX tags 2026-09activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar Namecheap US(US)
RegistrationCreated May 20, 2025 — Expires May 20, 2027
HTTP Status302 Found (Temporary)
Technical detailsProvenance & timestamps
First DetectedSep 9, 2026
DOM Analysisanalyzed Sep 10, 2026score 95/1001 brand signal
Submitted URLhttp://basevexora.io/
Favicon Hash

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
63.250.38.225
Network ASN
AS22612
Organization
Namecheap, Inc.
Observed location
Los Angeles, US
Server header
LiteSpeed

Nameservers 2

  • dns1.namecheaphosting.com
  • dns2.namecheaphosting.com

Mail routing 1 MX record

  • mail.basevexora.iopriority 0

Location describes the IP network.

TLS certificate

Issuer
Sectigo Limited / Sectigo Public Server Authentication CA DV R36
Valid from
2026-06-13 00:00:00
Valid until
2026-12-28 23:59:59
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-09-09 22:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprint6ae4b37c9fe9330cb5083cd4c8fb64873a2764cba578f1146c45aa69cd8e7011
Certificate names · 1 SANs
  • www.basevexora.io

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Latest Classified Outcome 2026-10-15 10:13:29 UTC

Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-10-15 10:13:29 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-15 10:13:29 UTC last content: 2026-10-12 22:18:56 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.
Recorded subdomains1

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • www.basevexora.ioDomain record

The original observation time is not recorded for these hostnames.

Technologies · 6 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

6 / 89 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 6 detections
alphaMountain.ai
CRDF
Forcepoint ThreatSeeker
Fortinet
Gridinsoft
SOCRadar

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of basevexora.io · checked Sep 9, 2026

56
Needs Work
Performance
FCP
5.76s
First Contentful Paint
LCP
93s
Largest Contentful Paint
CLS
0.031
Cumulative Layout Shift
TBT
101ms
Total Blocking Time
SI
7.85s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Detection & evasion checksStored browser and crawler observations
Detection-evasion analysis

Cloaking suspected: scanner and visitor titles differ

Not yet scanned No crawler-versus-browser difference has been recorded yet

Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.

Stored cloaking flag
Not yet scanned
Last cloaking scan
Server header seen by scanner
LiteSpeed

Scanner note: redirect: raw=redirect_302; http=302; via=https_proxy; location=https://basevexora.io/cgi-sys/suspendedpage.cgi; server=LiteSpeed

Title shown to the security scanner302 Found
Title shown to a browser visitorBasevexora | Homepage
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
Waiting
Timeline & responseCollection history, report status and investigation channels

Forensic History & Detection Timeline

ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
  1. VirusTotal Detections Update 2026-09-09 20:41:16 UTC
    Source: VirusTotal
    Event details
    VirusTotal scanner detections updated from 0 to 1. Added scanner alerts: Forcepoint ThreatSeeker.
  2. Threat First Observed 2026-09-09 19:06:34 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain ingestion complete. Initial state is marked as alive pointing to IP 63.250.38.225.
Stored observation history30

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  2. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  3. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  4. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  5. Availability monitor · Recorded state

    live_content→redirected

    http_redirect

Earlier observations 25
  1. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  2. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  3. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  4. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  5. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  6. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  7. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  8. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  9. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  10. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  11. Availability monitor · Recorded state

    live_content→redirected

    http_redirect

  12. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  13. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  14. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  15. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  16. Availability monitor · Recorded state

    live_content→Unknown

    stale_current_evidence

  17. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  18. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  19. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  20. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  21. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  22. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  23. Availability monitor · Recorded state

    Unknown

    probe_inconclusive

  24. VirusTotal · Detection count

    0→1

  25. Availability monitor · First collection record

    Reachable

Threat Response Pipeline

Discovery
Analysis
Monitoring

13 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Threat Ingested
basevexora.io detected and queued for full analysis
Sep 9, 2026
Spamhaus DBL
Spamhaus DBL recorded DBL_PHISH
Oct 10, 2026
URLScan.io Capture
Stored URLScan report with capture artifacts
Sep 9, 2026
Cloudflare Radar Report
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
Web Archive
Preserved in Wayback Machine — historical evidence archived
Sep 23, 2026
VirusTotal
6/89 recorded on VirusTotal
Sep 21, 2026
Blocklist Detection
Found in 2 blocklists: MetaMask, SEAL
Oct 16, 2026
OTX Community References
4 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
Oct 10, 2026
Brand Impersonation
Impersonation of MetaMask
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
Sep 9, 2026
Technical Analysis Recorded
The report contains stored technology or forensic-analysis results.
Oct 16, 2026
VT Detection +1
+1 new detection (0 → 1): Forcepoint ThreatSeeker
Sep 9, 2026
DestroyList Published
Sep 9, 2026
Monitoring Continues
The domain remains reachable or access-restricted; future checks may update this observation.
How we investigate & report

Public scans, evidence and abuse channels

We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.

Public Blocklist Status

Related infrastructureShared hosting, registrar records and related domains

Lookalike domains

79 stored lookalike domains

Show all (67)
metasmask.io insertion Internal report metramask.io insertion Internal report mewtamask.io insertion Internal report mmetamask.io homoglyph Internal report mtamask.io omission Internal report mwetamask.io insertion Internal report nmetamask.io homoglyph Internal report metamark.io bitsquatting Internal report metamaskj.io addition Internal report metammask.io homoglyph Internal report metamnask.io homoglyph Internal report emtamask.io transposition m-etamask.io hyphenation meamask.io omission meatmask.io transposition meramask.io replacement mertamask.io insertion metaamask.io repetition metaamsk.io transposition metaask.io omission metalmask.io insertion metamaask.io insertion metamadsk.io insertion metamaek.io replacement metamak.io omission metamas.io omission metamasak.io insertion metamasdk.io insertion metamask-io.com various metamasl.io replacement metamasm.io replacement metamsak.io transposition metamsk.io omission metamusk.io vowel-swap metamzsk.io replacement metarnask.io homoglyph metmaask.io transposition metmask.io omission metsamask.io insertion metsmask.io replacement mettamask.io repetition metwmask.io replacement metyamask.io insertion metzmask.io replacement meyamask.io replacement meytamask.io insertion mitamask.io vowel-swap mnetamask.io homoglyph mretamask.io insertion mrtamask.io replacement mstamask.io replacement mteamask.io transposition mwtamask.io replacement rnetamask.io homoglyph matamask.io bitsquatting mdtamask.io bitsquatting metamasi.io bitsquatting metamasj.io bitsquatting metamaska.io addition metamaskk.io addition metamaskl.io addition metamaso.io bitsquatting metamesk.io bitsquatting metamqsk.io bitsquatting metemask.io bitsquatting netamask.io homoglyph xn--metamas-bhb.io homoglyph
Evidence & investigation toolsOriginal reports, independent checks and evidence links
Help & reportingRecovery steps, reporting contacts and complaint drafts

Were You Affected by This Site?

4 evidence signal groups linked 0 reports recorded Last 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.

Europol
Find the official reporting channel for your EU country
National police directory
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 →

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

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

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Live Threat Feed Appeal This Listing
Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/basevexora.io"
  title="PhishDestroy threat report for basevexora.io"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>