SecureSMTP · Setup guideLatest plugin: v1.25.0

Get started in a few minutes

Add your sending domain, install the WordPress plugin, paste your API key, and pick a template — your first form is live in a few minutes, plus the time your DNS host takes to publish the domain records. This guide walks through every step with screenshots, plus the things people usually get stuck on.

60-second animated walkthrough of SecureSMTP — settings, editor, designer, frontend form, dashboard submissions, mail log
A 60-second tour: connect → build → style → embed → review

Four things to do, then you’re shipping forms

Sign up for a free SecureSMTP account, add your sending domain, install the plugin on your WordPress site, and connect the two with an API key. After that, the rest is the form-builder inside WordPress.

STEP 01

Sign up

Create a free SecureSMTP account at securessmtp.com/signup. No credit card.

Sign up →
STEP 02

Add your sending domain

Add your domain under Sending domains and publish its DNS records: 1 record in Simple mode, 3 in Advanced.

Sending domains →
STEP 03

Install the plugin

Download v1.25.0 and upload it via Plugins → Add New → Upload Plugin.

Download zip →
STEP 04

Paste your API key

Copy the key from /app/forms/api-keys and paste it in WordPress → SecureSMTP → Settings.

Get my key →

Step-by-step setup

A few minutes, plus DNS time
  1. 1

    Create your SecureSMTP account

    Head to securessmtp.com/signup and create an account. Email + password, or sign in with Google. The free tier covers 100 form submissions per month, forever — no credit card required.

    Already have a SecureSMTP account? Log in.

  2. 2

    Add your WordPress site in the dashboard

    Open /app/forms/sites → click Add site → enter your site URL (e.g. https://acme-marketing.com). SecureSMTP generates a per-site API key automatically — that’s what the WordPress plugin uses to authenticate.

    Why per-site keys? If a key leaks, you only have to rotate that one site, not your entire account.

  3. 3

    Add your sending domain

    New accounts send email only from their own verified domain. Open /app/forms/email → add your domain under Sending domains and publish the DNS records it shows. Simple mode needs 1 record (a DKIM TXT record). Advanced adds an MX and an SPF record on a bounce subdomain, 3 records in all.

    DNS takes a few minutes to publish, sometimes longer. When all records are found, the status changes from Pending DNS to Verified. You can do the next steps while you wait. The Free plan includes 1 sending domain; Starter and higher have no limit. See Domains and DNS.

    Until the domain is verified, form notifications are not sent. Accounts created before 29 October send them from the shared address [email protected] until 12 November. A separate allowance of 10 test emails a day (per account, across all its sites) applies only to test emails sent with the plugin’s Send test, the API or SMTP, and only to the account’s own confirmed address. Form notifications do not use it.

  4. 4

    Copy the API key

    Go to /app/forms/api-keys. You’ll see the key for the site you just added (looks like qcs_live_a1b2c3...). Click the copy icon — keep this tab open, you’ll paste in WordPress shortly.

    Keep your key private. It’s a server-side credential — never paste it into a frontend file, never commit it to a public git repository.

  5. 5

    Install the plugin in WordPress

    Download securessmtp.zip (v1.25.0). In WordPress admin:

    1. Go to Plugins → Add New → Upload Plugin
    2. Click Choose File and pick the securessmtp.zip you just downloaded
    3. Click Install Now, then Activate Plugin

    After activation you’ll see a new SecureSMTP item in the WordPress sidebar.

  6. 6

    Paste the API key in WordPress

    In WordPress admin, go to SecureSMTP → Settings. Paste your API key into the SecureSMTP API key field and click Save and test connection. You should see a green Connected to SecureSMTP banner with your site name, plan, and usage.

    SecureSMTP Settings page in WordPress admin showing Connected to SecureSMTP status with site name, plan, and usage
    WordPress → SecureSMTP → Settings, after pasting your API key

    That’s the whole setup. Everything below is about using the plugin to build and embed forms.

  7. 7

    Create your first form from a template

    In WordPress admin: SecureSMTP → Add New. Pick from 13 ready-made templates — Contact, Quote, Newsletter, Demo, Booking, Support, Lead Magnet, Event RSVP, Job Application, Real Estate, Wedding, Restaurant Reservation, Feedback. You can always customise later, so just pick the closest one.

    WordPress form editor with drag-and-drop field cards, one being dragged with a tilt and blue border, one expanded showing label/type/placeholder/required controls
    Drag-and-drop field editor — click any field to expand it, drag the handle to reorder
  8. 8

    Edit fields and style the form

    Each field is a collapsible card. Click to expand the label / placeholder / required toggle. Drag the left-side handle to reorder. Need a different field type? Click + Add field.

    The Design meta-box on the same page lets you pick a brand colour, corner radius, field background tone, button alignment, and an optional card wrapper. Live preview updates as you edit.

    SecureSMTP Designer meta-box showing brand colour swatches, corner radius slider, field background, button alignment, card wrapper toggle, with a live preview of the form on the right
    Design meta-box — change one setting and the live preview updates immediately
  9. 9

    Publish and copy your shortcode

    Click Publish (top-right). The Embed meta-box in the sidebar shows the shortcode for this form — something like:

    > [securessmtp_form id="42"]

    Paste that shortcode into any page or post — Gutenberg Shortcode block, Classic editor, page-builder shortcode widget, or even inside a theme template via <?php echo do_shortcode('[securessmtp_form id="42"]'); ?>.

  10. 10

    Submit a test entry on the frontend

    Visit the page where you embedded the shortcode. You should see the form rendered with the styling you picked. Fill it in and submit — the submission shows up in your SecureSMTP dashboard right away. Once your domain is verified, the email lands in your notification inbox within about a second.

    Frontend contact page on acme-marketing.com with the SecureSMTP-rendered form on the right, name and email fields filled in, gradient send-message button, and 'Protected by SecureSMTP' footer
    The rendered form on a customer-facing page — protected by invisible spam checks
  11. 11

    Review submissions in your dashboard

    Open /app/forms/submissions to see every entry across all your sites. Each submission shows:

    • The visitor’s name, email, and message
    • An AI-generated classification (Genuine / Spam / Suspicious / Newsletter)
    • A spam score (0.00 = clearly genuine, 1.00 = clearly spam)
    • Email-delivery status (Delivered / Soft bounce / Held for review / Blocked)
    SecureSMTP dashboard submissions view: 4 stat cards (Last 30 days, Spam blocked, Avg response time, Email delivered) above a table of 7 submissions with avatars, form names, excerpts, classifications, scores, and email status
    SecureSMTP dashboard — every submission, AI-classified, with email delivery status

Shortcode reference

SecureSMTP gives you two shortcode flavours. The one you use depends on whether you want the form definition stored in WordPress or in the SecureSMTP dashboard.

WordPress-native form

Form built inside WordPress via SecureSMTP → Add New. Form lives in your WP database; you embed it by post ID.

> [securessmtp_form id="42"]

The ID comes from the Embed meta-box on the form’s edit screen.

SecureSMTP-hosted form multi-site

Form built in the SecureSMTP dashboard at /app/forms/builder. One definition, embeddable on any number of sites — edit once, propagates everywhere within 5 minutes.

> [securessmtp_form slug="contact"]

Particularly useful for agencies running the same form across multiple client sites.

Common questions

I clicked “Save and test connection” but I see a red error banner. What now?
Three usual culprits: (1) the API key has a typo or extra whitespace — re-copy from /app/forms/api-keys and re-paste. (2) the site URL you registered in SecureSMTP doesn’t match where you’re running — confirm at /app/forms/sites. (3) your WordPress host can’t reach securessmtp.com — rare, but check with your host or run curl -I https://securessmtp.com/api/v1/health from the WordPress server via SSH.
My submissions show up in the dashboard but the email never arrives.
Form emails go out from your own verified sending domain, signed with DKIM as that domain. If you have not verified a domain yet, the email is not sent. Add your domain under Sending domains in the dashboard and publish its DNS records (see Domains and DNS). DNS takes a few minutes to publish, sometimes longer. Until the domain is verified, form notifications are not sent. Accounts created before 29 October send them from the shared address [email protected] until 12 November. The 10 test emails a day apply only to test emails sent with the plugin’s Send test, the API or SMTP, to the account’s own confirmed address. Form notifications do not use that allowance. If your domain is verified, check your spam folder: the first one or two messages can land there until your inbox learns to trust the sender. The Mail Log inside WordPress (SecureSMTP → Mail Log) shows delivery status — look for the Soft bounce / Hard bounce indicators.
Do I need a paid plan to use the plugin?
No. The free plan covers 100 submissions per month forever — no time limit, no nag screen. Paid plans (see pricing) raise the submission quota and add advanced AI features. The plugin itself is GPL-licensed and free.
Can I add the plugin to multiple WordPress sites under one SecureSMTP account?
Yes. Add each site at /app/forms/sites to get a per-site API key. Drop the appropriate key into each site’s WP plugin settings. Submissions and analytics are tracked per site.
What does the plugin actually send to securessmtp.com?
For each form submission: the field values the visitor entered, their IP address (rate-limit + spam classification), User-Agent, the HTTP Referer, the page URL the form was on, and your site’s API key. Nothing else. No tracking, no third-party analytics, no advertising integrations. Full data inventory is in the plugin’s readme.txt under Privacy & Data Handling, and the SecureSMTP-side privacy policy is at /privacy.
How do I uninstall cleanly?
Deactivate the plugin in Plugins → Installed Plugins. To remove all plugin data (forms, settings, mail-log table), delete the plugin via WordPress — uninstall.php cleans up. Submissions in your SecureSMTP dashboard are unaffected by the plugin removal; delete them individually from /app/forms/submissions if you want.

Ready to ship your first form?

Sign up free — no credit card, 100 submissions a month forever. The whole flow above takes a few minutes, plus the time your DNS host takes to publish the domain records.