SSL certificate is invalid or expired. Issuer: Amazon / Amazon RSA 2048 M01
Evidence Summary
Critical
VirusTotal
3/91
OTX
1 community ref
URLScan
Stored capture
Analysis of bep.network indicates a newly registered domain created on 22 March 2026 that is being used for brand impersonation of TrustWallet. The site presented the page title “Send BBN | Trust Wallet”, aligning with the targeted brand. The domain is registered through NameCheap, Inc., and delegated to four Amazon Route 53 nameservers (ns-1323.awsdns-37.org, ns-2022.awsdns-60.co.uk, ns-61.awsdns-07.com, ns-683.awsdns-). DNS resolution points to the IP address 13.35.58.95, which belongs to Amazon.com, Inc. (AS16509) and is geolocated in Germany. The SSL certificate presented is an Amazon‑issued RSA‑2048 M01 certificate, confirming the hosting provider’s involvement but offering no legitimacy to the content.
Reputation signals are uniformly negative. Gridinsoft assigned a trust score of 0 / 100, and the domain appears on a single security blocklist. VirusTotal reports three detections out of ninety‑one scanned vendors, and AlienVault OTX references the domain in one threat‑intelligence pulse. PhishDestroy has also blocked the domain. The site’s current HTTP status is offline, indicating that the malicious content has been taken down or the infrastructure has been abandoned.
For defenders, the evidence suggests that bep.network was actively used to lure victims into sending Binance Coin (BNB) under the guise of a Trust Wallet transaction. Monitoring should include adding the domain and its IP address to blocklists, configuring DNS sink‑hole rules for the associated nameservers, and alerting users of Trust Wallet about the specific “Send BNB | Trust Wallet” page title that may appear in phishing emails. Since the domain is already offline, retrospective log analysis can help identify any compromise attempts that referenced the domain or its IP. Ongoing vigilance is recommended because the same registration and hosting patterns have been reused in other Trust Wallet impersonation campaigns.
Extracted from stored page analysis
Observed indicators
1 wallet · 0 Telegram
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
RegistrationCreated Mar 22, 2026 (206d)—Expires Mar 22, 2027
Time to First Unavailability6h
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 DetectedJun 24, 2026
DOM Analysisanalyzed Jun 24, 2026score 76/1001 brand signal
IoC Extractionscanned Jul 29, 20261 wallet · 0 Telegram IoC
Submitted URLhttps://bep.network/
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-13 01:09:02 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-07-08 22:17:00 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-07-08 22:17:00 UTC → 2026-09-30 16:14:55 UTC · 2,009.97hmidpoint estimate ≈ 2026-08-19 19:15:57 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.
11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Jun 25, 2026
Time to First Unavailability
6 hours elapsed from detection to the first unavailable 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.
6 evidence signal groups linked1 reports recordedContent unavailable
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 · bep.network
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 matches4
Same favicon hash or the same page title as this host.
