Security engines reporting a detection: 7. Public blocklists reporting a match: 2. 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@namecheap.com.
The latest stored availability evidence still shows the domain reachable; 7 days 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.
Stored evidence for aevachain.com: VirusTotal recorded 4 detections among 91 scanners on 2026-09-27. 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 aevachain.com. Each item in this report remains at the scope supplied by its dated source record.
Detection Evidence
VirusTotal records 4 detections among 91 scanners in the stored snapshot dated 2026-09-27. 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-27 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 aevachain.com in the snapshot dated 2026-09-27. 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 aevachain.com 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 aevachain.com on 2026-09-27. The MetaMask and SEAL blocklist snapshot is dated 2026-09-27 and remains a separate event in the stored timeline. The registration date is separately recorded as 2026-09-20. A URLScan reference was stored on 2026-09-27 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 aevachain.com, the registrar field records NAMECHEAP INC; this is kept as an exact source value. The source stores 31.43.161.6 as the observed address in this record. The registration date for aevachain.com is recorded as 2026-09-20. The stored ASN observation records 16509 in this record. The observed server header is recorded as Framer/26fa766 in this record. 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 aevachain.com record states that VirusTotal recorded 4 detections among 91 scanners on 2026-09-27. MetaMask and SEAL remain named blocklist observations from the snapshot dated 2026-09-27. PhishDestroy remains a separate publisher catalogue entry in the stored record. For aevachain.com, the registrar field records NAMECHEAP INC; this remains separate from the other source fields. The observed address field in this record contains 31.43.161.6. The supported conclusion is bounded to the exact stored observations for aevachain.com. Any statement beyond those source values would require additional dated material.
Recommended Actions
Avoid submitting sensitive information to aevachain.com during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain aevachain.com 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 aevachain.com. The stored record does not justify extending that rule to 31.43.161.6 or to other infrastructure records.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo 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.
DOM Analysisanalyzed Sep 27, 2026score 100/1001 brand signal
Submitted URLhttp://aevachain.com/
Favicon Hash
Case ID
Page Title
Aeva | The Asset-Native L1 Blockchain
Impersonates
Across
TLS Certificate
Hostname coverage not recorded·
Issued by YE2
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
31.43.161.6
Network ASN
AS16509
Organization
Framer B.V
Observed location
Amsterdam, NL
Server header
Framer/26fa766
Nameservers 2
dns1.registrar-servers.com
dns2.registrar-servers.com
Mail routing 2 MX records
mx2.privateemail.compriority 10
mx1.privateemail.compriority 10
Location describes the IP network.
TLS certificate
Issuer
YE2
Hostname coverage
Hostname coverage not recorded
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.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-03 10:20:27 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-03 10:20:27 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 · 4 identified
F
Framer Sites
CMSPage builders
Framer is a no-code web design platform for designing and publishing responsive websites.
Google PageSpeed Insights — mobile performance audit of aevachain.com· checked Sep 27, 2026
82
Needs Work
Performance
FCP
2.26s
First Contentful Paint
LCP
4.51s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
8ms
Total Blocking Time
SI
2.26s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
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.
VirusTotal Detections Update2026-09-27 06:46:13 UTC
VirusTotal scanner detections updated from 0 to 4. Added scanner alerts: BitDefender, Forcepoint ThreatSeeker, G-Data, Kaspersky.
Threat First Observed2026-09-27 02:38:46 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 31.43.161.6.
Threat Response Pipeline
Discovery
Analysis
Notifications
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
aevachain.com detected and queued for full analysis
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.
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+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
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.
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
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · aevachain.com
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 matches1
Same favicon hash or the same page title as this host.
(IS)
