Website submissions
hello@web3seeker.comSuggest established Web3 tools with official domains, clear utility, and useful safety context.
Best for wallets, bridges, DEXes, explorers, security tools, and dev resources.
Contact
Official channels for Web3 navigation coordination.
Route website submissions, domain corrections, safety notices, and product feedback through the right channel so each request can be reviewed with clear context.
ChannelsSubmission checklistContact formSafety reportingResponse guidanceTypical response: 1-3 business days
Contact channels
Route requests to the right inbox.
Each channel uses a subject preset so submissions, corrections, and safety reports remain easier to triage.
Domain corrections
hello@web3seeker.comReport stale URLs, official-domain changes, duplicate listings, or inaccurate verification context.
Include the current listing URL and the official source for the correction.
Safety notices
security@web3seeker.comFlag phishing risk, compromised domains, misleading listings, or wallet-connection concerns.
Use this for urgent safety context that should be reviewed before normal listing updates.
Product feedback
hello@web3seeker.comShare feedback about search quality, categories, card density, keyboard UX, or starter routes.
Concrete examples help improve routing and verification language faster.
Safety reporting
Report suspicious routing context.
Use the safety channel for suspected phishing domains, wrong official links, compromised project URLs, or listings that may cause users to connect wallets in the wrong place.
Safety inbox
security@web3seeker.comInclude the affected listing, observed domain, expected official source, and urgency.
Response guidance
Help review happen faster.
Clear requests reduce back-and-forth and keep verification decisions auditable.
Use a clear subject line that matches the request type.
Include the exact website URL, official source, and expected correction.
For safety reports, include the observed domain, steps to reproduce, and why it may mislead users.
Contact form
Send a structured request.
The form mirrors the old Web3Seeker contact flow: request type, name, email, optional company and website, subject, and message.
This v2 site has no backend, so submitting prepares a prefilled email draft instead of storing data on a server.
Submission checklist
- Website name and official URL.
- Evidence that the URL is the official domain or an official app/docs subdomain.
- Best matching category.
- Supported chains and supported user actions.
- Short reason the site is useful.
- Whether wallet connection or a financial action is involved.
- Known safety, custody, regional, or smart contract risk users should understand.
Quality bar
A listing needs more than a title and URL. It should explain what the site does, who should use it, what a visitor can accomplish there, and what limitations or risks should be checked. Submissions are not guaranteed to be reviewed or listed.