Contact the Awazon Team

The only supported communication line is the Awazon thread on the Dread forum. There is no email inbox, no Telegram bot, and no Discord ticket system. If a message claims to be from "Awazon Support" elsewhere, verify its PGP signature before trusting anything written inside. Direct channels minimize the risk of impersonation and keep interactions traceable against known signatures. Stick to the established path to avoid losing resources to intermediaries who may not exist.

Post on Dread

Open the Awazon thread and create a new reply describing your problem. Public replies often receive attention faster than private ones. Other community members frequently spot errors or confirm fixes before the team responds. A short factual post in the thread keeps the conversation visible and prevents duplicate accumulation. Visibility helps everyone. Keep it concise. State the issue once clearly rather than posting multiple variations hoping one lands.

Make the report useful

For a dead mirror, include the full onion address, the date, and approximate time you noticed the failure. Add the exact error text displayed by Tor Browser. For suspected phishing clones, specify where you found the address, such as a chat, Telegram, or forum. Attach a screenshot showing the layout difference. Note how many characters differ from the official string. Five precise lines save the team twenty minutes of back-and-forth. Vague reports like "site slow" or "strange popup" provide no starting point for diagnosis.

What this channel does not handle

Order tracking, dispute resolution, refunds, and appeals for blocked accounts fall outside this thread scope. Route these problems to the market dispute center or the specific vendor thread. A refund request posted in the general Awazon thread will not speed up the process. The team monitors this thread for infrastructure and communication issues, not for mediating individual transactions. Know where to send each type of query to get results.

Response times

Expect a response within twelve hours on weekdays. Weekends run longer, sometimes exceeding twenty-four hours, because the team works shifts and coverage thins. Phishing reports receive priority handling. A clone sitting on a popular forum can siphon logins for hours, so those threads jump the queue. If your post lacks a response after forty-eight hours on a weekday, add a short ping quoting the original post. Do not start a new thread for the same issue.