EntityMap — FormReceipt

Evidence

"FormReceipt provides contact form monitoring: we use browser automation to open pages you configure, attempt test submissions, store run results and related artifacts, and send service-related email."

Privacy Policy — FormReceipt — published by FormReceipt

"Contact-form monitoring made simple: we submit your real form on a schedule, save screenshots and proof, email your team one yes/no question, and alert you with context if delivery fails."

FormReceipt — Know every contact form actually delivers — published by FormReceipt

Evidence

"We test your contact form like a visitor, save proof, and email your team a link to confirm the lead notification arrived. If it didn't, you get alerts and saved context in the product."

How it works — FormReceipt — published by FormReceipt

"Plans scale by how many forms you monitor—the workflow stays the same: real submission, proof on file, inbox confirmation, and alerts when things go wrong."

Pricing — FormReceipt — published by FormReceipt

Evidence

"We email your team a link to confirm the lead notification arrived after each automated test submission."

How it works — FormReceipt — published by FormReceipt

"Yes/No on Confirm the test email is clickable immediately; receipt confirmation records whether the expected notification reached the team inbox."

Getting started with FormReceipt — published by FormReceipt

Evidence

"Public test IDs are lowercase (fr-YYYY-MM-DD-…) with case-insensitive IMAP matching so submitter notification emails reliably tie to the run."

Sites and forms — published by FormReceipt

Evidence

"When you add a form by URL, FormReceipt probes the page and returns an access assessment before save: blocked, manual only, or automate OK."

Allowlisting FormReceipt automation — published by FormReceipt

"Run a probe when you add a form. Re-run it when the form changes, for example after a plugin update, a theme redesign, or field edits."

Sites and forms — published by FormReceipt

Evidence

"When the site sends an auto-reply to the test submitter address, the run shows a supplemental submitter notification detected hint during receipt confirmation without auto-completing the test."

Test email or receipt not received — published by FormReceipt

Evidence

"A successful submit is not the same as a delivered lead: HTTP 200, a thank-you page, and a green SMTP plugin do not guarantee anyone received the message."

A successful submit is not the same as a delivered lead — published by FormReceipt

"Delivery means the message exists somewhere the team can act on it. That is the bar that matters for lead-gen sites."

A successful submit is not the same as a delivered lead — published by FormReceipt

Evidence

"FormReceipt automates the first and last miles: real browser submission, proof of what happened on the page, and tracking whether the expected receipt showed up."

A successful submit is not the same as a delivered lead — published by FormReceipt

"Missing email can come from two different places: the run may have failed before sending, or mail may have been sent but filtered."

Test email or receipt not received — published by FormReceipt

Evidence

"SPF lets receiving mail servers check whether an outbound server is authorized to send mail for your domain. The domain publishes a DNS TXT record listing permitted senders."

SPF records explained — published by FormReceipt

"You should publish only one SPF TXT record for a given domain or label. Multiple SPF TXT records invalidate SPF for many receivers."

SPF records explained — published by FormReceipt

Evidence

"DKIM adds a cryptographic signature to outgoing messages. Receivers fetch the public key from DNS via the selector and verify the message was not altered in transit."

DKIM signing explained — published by FormReceipt

Evidence

"A DMARC DNS TXT record at _dmarc.example.com declares your policy (none, quarantine, reject) and where reports should be sent."

DMARC explained — published by FormReceipt

"DMARC passes when either SPF or DKIM aligns with the header From domain and passes authentication—depending on strict or relaxed alignment settings."

DMARC explained — published by FormReceipt

Evidence

"Fix SPF so legitimate sending IPs and includes are correct, enable DKIM signing with your provider, publish DMARC in p=none while monitoring aggregate reports, then tighten policy."

Using SPF, DKIM, and DMARC together — published by FormReceipt

Evidence

"Confirm SMTP host, username, and password or token, then confirm the expected port and encryption mode from your provider docs before checking provider logs."

SMTP authentication errors when sending — published by FormReceipt

"Port 587 usually expects STARTTLS. Port 465 usually expects implicit TLS. Mismatched port and TLS mode can fail even with correct credentials."

SMTP authentication errors when sending — published by FormReceipt

Evidence

"Blocked means HTTP 403/429/451 or a stuck interstitial. Manual only means CAPTCHA or a password gate on the form. Automate OK means proceed with field mapping and schedules."

Allowlisting FormReceipt automation — published by FormReceipt

Evidence

"FormReceipt runs checks on a schedule so you can spot breakages quickly without manual testing. Paid plans can set timezone, preferred time, and active weekdays. Free runs once per week at signup weekday and local time with no schedule customization."

Scheduling and timing — published by FormReceipt

Evidence

"The safest fix is targeted allowlisting for known FormReceipt markers: allowlist identity headers and user agent on your form route only, not the entire domain."

Allowlisting FormReceipt automation — published by FormReceipt

"Do not bypass your entire challenge or WAF stack. Avoid global allowlist rules at the domain root."

Allowlisting FormReceipt automation — published by FormReceipt

Evidence

"FormReceipt uses browser automation to open pages you configure and attempt test submissions, storing run results, screenshots, and timeline events as proof."

Privacy Policy — FormReceipt — published by FormReceipt

Evidence

"Each saved form is tied to its page URL so checks stay focused on the right form and do not target a hidden duplicate on the same template."

Sites and forms — published by FormReceipt

Evidence

"Every plan includes the same workflow: real submission, saved proof, and inbox confirmation. Pricing scales by number of monitored forms."

Pricing — FormReceipt — published by FormReceipt

"Annual billing saves 33% (about two months free) versus monthly on paid tiers. All paid plans include daily monitoring by default and customizable schedule time zone and weekdays."

Pricing — FormReceipt — published by FormReceipt

Evidence

"Free plan: $0 for 1 monitored contact form with 1 browser check per week at your signup weekday and local time, real submission proof, and inbox confirmation. Schedule is fixed at signup—no custom time zone, time, or weekdays."

Pricing — FormReceipt — published by FormReceipt

Evidence

"Paid plan for 1 monitored form: $12/month or $120/year (about $10/mo billed annually), 3 checks per week, customizable schedule, and enhanced challenge recovery."

Pricing — FormReceipt — published by FormReceipt

Evidence

"Paid plan for 3 monitored forms: $24/month or $240/year, 3 checks per week, and customizable schedule time zone and weekdays."

Pricing — FormReceipt — published by FormReceipt

Evidence

"Paid plan for 10 monitored forms: $60/month or $600/year, daily checks including weekends, and customizable schedule."

Pricing — FormReceipt — published by FormReceipt

Evidence

"Paid plan for 50 monitored forms: $120/month or $1,200/year, daily checks including weekends, and customizable schedule."

Pricing — FormReceipt — published by FormReceipt