Skip to content
🚀 10 tools live, free forever — the toolbox keeps growing
Contact

How can we help?

We are here to help with any question, bug, or idea about our tools. No account needed, and we read every message.

✉️

Email support

The best way to reach us is by email. We are glad to help with support questions, feedback and suggestions, or bug reports.

contact@buildtoolforge.com
  • Support inquiries
  • Feedback and suggestions
  • Bug reports
🔒 Privacy first

Your email is used only to reply to you. We never share it.

⏱ Quick response

We aim to reply within 24 to 48 hours on weekdays.

📊

Our impact

24-48h
Response time
No
Signup required
0
Data collected
Free
Always
❓

Frequently asked questions

How quickly will I get a response?⌄

We usually reply within 24 to 48 hours on weekdays. Bug reports that break a tool are prioritized and often looked at sooner.

Do I need an account to contact you?⌄

No. Just like our tools, support needs no sign-up. Email us directly and we will get back to you.

What should I include in a bug report?⌄

The most helpful reports mention which tool you were using, what you were trying to do, what happened versus what you expected, and your browser and device. A screenshot helps a lot.

Can I request a new tool or feature?⌄

Yes, and we welcome it. We cannot build every request, but we prioritize ideas that would help many people, and popular ones often ship within a month or two.

Is my contact information kept private?⌄

Yes. We use your email only to reply to you. We never sell it, add you to marketing lists, or share it with third parties.

Can I contribute or partner with you?⌄

We are happy to hear from developers and partners. Reach out by email and tell us what you have in mind.

How to reach the BuildToolForge team

Have a question, found a bug, or want to suggest a new tool? We would love to hear from you. The fastest way to reach BuildToolForge is by email, and we read every message. To help us respond quickly, please include as much detail as you can — the tool or page you were using, what you expected to happen, what actually happened, and your browser or device if the issue looks technical.

We welcome feedback of every kind: feature requests, corrections to a guide, ideas for free tools that would save you time, and partnership or contribution enquiries. While we cannot promise a specific response time, we aim to reply to genuine questions as soon as we reasonably can, and there is no account or signup required to get in touch.

What to include in your message

A clear first message gets a faster and more useful answer. These details let us reproduce what you see without a round of follow-up questions.

For a bug report

Tell us which page you were on, what you entered — a domain, a URL or a sample value, never a real password or private key — what you expected and what happened instead. A screenshot and the name of your browser help, especially if the problem only appears on a phone.

For a wrong or confusing result

Include the domain or input you checked and the time of the check. DNS records and certificates change, so the time lets us compare our answer with what your provider shows at that moment.

For a new feature or guide

Describe the task you are trying to finish and the result you need. Requests that come with a real example are the easiest to plan, and several items on our roadmap started exactly this way.

Keep private details out

Only send what is needed to reproduce the issue. If a token, header or record contains private details, replace them with placeholders; the structure is usually enough for us to see what is wrong.

For partnerships or permissions

For a partnership, feedback on a guide or permission to quote our content, say so in the subject line. It helps the message reach the right person faster and lets us reply with everything you need in one email.

What we cannot do

We cannot access your hosting, registrar or email accounts, and we cannot make changes on your behalf. We can explain what a result means and which setting usually fixes it, so you or your provider can make the change with confidence.

Following up on an earlier message

If you have not heard back within two working days, reply to your original email rather than starting a new one. Keeping the thread together means we see the full history straight away.

Every message is read and answered by a person, usually within one to two working days, and your email address is used only to reply to you.

Last updated: November 1, 2026
Share this page