VirusTotal
4 / 89
“Web3 Connect - DeFi, Wallet”
web3connected.online returned an HTTP 200 status on 2026-10-01, a recorded server response on that date. The domain also carried a PageSpeed performance score of 70, measured on 2026-09-15, and first appeared in the records on 2026-09-04.
OTX recorded three pulses for web3connected.online as of 2026-09-16. VirusTotal reported 4 detections across 89 scanners on 2026-09-18. The domain appeared in the PhishDestroy internal listing, and its SSL certificate, issued by Let's Encrypt / YE2, was scanned on 2026-09-15. The registrar is PDR Ltd. d/b/a PublicDomainRegistry.com, with registration dated 2026-06-01.
The named sources describe different aspects of web3connected.online rather than one uniform picture. The HTTP response and PageSpeed score concern server behavior, while the OTX and VirusTotal records concern security-related observations, and the PhishDestroy listing concerns catalogue membership. Because the dates span several weeks, a reader can compare what each source recorded without treating the records as a single measurement.
For web3connected.online, preserve the OTX and VirusTotal records as separate items for later comparison. Retain the PhishDestroy listing entry alongside the HTTP response record, and compare the PageSpeed observation against future measurements. Keep each source record distinct so that later reviews can trace which observation came from which source.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
nginxScanner note: alive_content: raw=ok; http=200; via=https_proxy; server=nginx
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.
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.
nsc.go54.commail.web3connected.onlinepriority 10Location describes the IP network.
85effaef43115b98bdb1605b27f9e9944963f2958d66d7d8f55422589f26b1e9ftp.web3connected.onlinemail.web3connected.onlinepop.web3connected.onlinesmtp.web3connected.onlinewww.web3connected.onlineSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of web3connected.online · checked Sep 15, 2026
7 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
1 community report
CategoryOTHER_INVESTMENT_SCAM
The suspect reached out to me on twitter and wanted me to pay for his sniping bot after he gave me some successful calls on meme coins. I used it and tried to withdraw and then he blocked me and I received no money. I lost around $800
“The suspect reached out to me on twitter and wanted me to pay for his sniping bot after he gave me some successful calls on meme coins. I used it and tried to withdraw and then he blocked me and I received no money. I lost around $800”
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive