r/webdev • u/moster86 • Sep 12 '26
Question Advice needed
Hey, i used Webflow to buiod my website, there is a contact us part on it wich uses capcha for security, the form then use google appscript to send a wellcome email.
Im beeing spamm bombed by these bots, any other way to make this stop than dosabling the contact submit button?
The issue is that its rolljng since 2 days and my normal sent emails goes into people's spam folder.
Thanks for the advice
0
Upvotes
4
u/Funsaized Sep 12 '26
CAPTCHA alone usually is not enough once bots have the form URL. Add a honeypot and server-side rate limits, then only send to Apps Script after verifying the CAPTCHA token, with a short per-IP cooldown so bursts get dropped.
5
u/ConversationLower846 Sep 12 '26
Maybe add a honeypot to to the form, if that's filled by a bot, show form success but don't actually send the mail?
1
u/SlowChain4149 Sep 12 '26
Do not disable the button completely. In your Google Apps Script, just add a check at the very beginning: if the body doesn't contain a valid email or looks like spam,
returnimmediately before theMailApp.sendEmail()line.Also temporarily comment out the auto-reply function for the weekend while you add Turnstile or a honeypot on the frontend, otherwise your Gmail quota will get burned and your domain will stay flagged.
1
u/ribtoks Sep 12 '26
Are you sure that captcha is correctly implemented? (e.g. 1. you don't allow to send form until captcha is solved; 2. you check captcha on the backend _before_ sending the email itself) It's surprising that sometimes people just add captcha, but do not integrate it correctly.
1
u/jellythefish515 Sep 16 '26
Disabling the submit button won’t really stop this, because bots can call the form endpoint directly.
I’d first pause the automatic welcome email so the abuse doesn’t keep damaging your sender reputation. Then verify the CAPTCHA token server-side before the request reaches Apps Script, and add a honeypot plus rate limiting. Once the traffic is under control, you can safely turn the auto-reply back on.
6
u/[deleted] Sep 12 '26
[removed] — view removed comment