Systeme.io Emails Not Sending or Going to Spam Fix It With Hostinger DNS

If your Systeme.io emails are not sending, not reaching inboxes, or landing in the spam folder, the fix is almost always in your domain’s DNS settings.

Systeme.io requires domain authentication before emails can be delivered reliably. This means adding specific DNS records CNAME records and a DMARC TXT record to your Hostinger DNS zone so that receiving email servers recognise Systeme.io as an authorised sender for your domain. Without these records in place, emails either land in spam or never arrive at all.

This guide documents the complete setup for Hostinger users built from configuring this on a real project covering every record, every step, and what to check when authentication stays pending past 24 hours.

What causes Systeme.io emails to fail or go to spam

Domain authentication is the process of adding DNS records to your domain’s hosting account that tell receiving email servers Gmail, Outlook, and others that Systeme.io is authorized to send emails on your domain’s behalf.

When these records are missing or configured incorrectly in Hostinger, receiving servers cannot verify the source of the email. The result is one or more of these outcomes.

1 — Emails land in the spam or junk folder instead of the inbox.

2 — Emails are silently dropped and never delivered to the recipient.

3 — The sender address shows as unverified inside Systeme.io settings.

4 — Welcome emails do not send after a contact opts in through a funnel.

5 — Follow-up sequences stop delivering part way through a campaign as receiving servers flag the domain.

6 —The “from” name displays incorrectly because the sending domain has not been confirmed.

None of these problems are caused by your email content or your Systeme.io settings. They are caused by missing or incorrectly configured DNS records in Hostinger. The fix happens in Hostinger not inside Systeme.io.

What you need before starting

Before making any changes in Hostinger, confirm you have everything listed below. Having these ready before you start prevents interruptions mid-setup.

1 — A domain registered and active in Hostinger. Your domain must be connected to an active website not a parked page or a blank holding page. Systeme.io will not complete domain verification for a domain that does not resolve to live content. If your domain is not yet connected to a WordPress installation or a Systeme.io funnel page do that first.

2 — Access to Hostinger hPanel. You will be making changes in the DNS Zone editor. Log in to hPanel before starting and locate the DNS Zone section under your domain management. Knowing where it is before you need it saves time during the setup.

3 — Your Systeme.io account opened in a second browser tab. The DNS record values you will add to Hostinger are generated inside Systeme.io settings. Having both accounts open simultaneously means you can copy values directly without switching between tabs and risking transcription errors.

4 — An email address for DMARC reporting. The DMARC TXT record you will add in Step 3 requires a reporting email address; this is where DMARC diagnostic reports are sent. Use a real accessible email address. A dedicated address for this purpose is preferable to your main inbox as DMARC reports arrive frequently and are technical in nature.

5 — Access to DNSChecker and MXToolbox Both are free tools used to verify that DNS records have propagated correctly after being added in Hostinger. Systeme.io’s own verification interface can lag behind actual DNS propagation, these tools allow you to confirm records are resolving correctly before concluding something went wrong. No account required for either. dnschecker.org, mxtoolbox.com

How to fix Systeme.io email authentication in 6 steps

The following steps walk through the complete domain authentication setup from generating the DNS records inside Systeme.io to confirming the sender email address that contacts will see. The full process takes approximately 20 to 30 minutes. Most of that time is waiting for DNS propagation rather than active configuration.

Work through the steps in order. Each step depends on the one before it.

Step 1, Generate your DNS records in Systeme.io

The first step happens inside Systeme.io not in Hostinger. You are generating the specific DNS record values that your account requires. These values are unique to your domain and account. Do not use values from a screenshot or another tutorial.

Follow these steps inside your Systeme.io account.

1. Click the profile icon in the top right corner of the Systeme.io dashboard
2. Select Settings from the dropdown menu
3. Click Emails in the left sidebar
4. Scroll down to the Domains section
5. Click Add a domain
6. Enter your domain name for example “yourdomain.com” and click Generate DNS records

Systeme.io will now show a pending status for your domain. To view the actual record values click the eye icon below the DNS settings. Your records will appear, copy each one carefully into the next step.

The records generated will be:

3 CNAME records: these authenticate your domain as an authorised sender for Systeme.io. Each CNAME record has a Name value and a Value that points to a Systeme.io server address.

1 DMARC TXT record: this tells receiving email servers how to handle any emails from your domain that fail the authentication check. It also contains a reporting address, the rua field where DMARC diagnostic reports are sent. You will add the email address for this field in Step 3.

Leave your Systeme.io tab open. You will copy these values directly into Hostinger in the next step.

Step 1 is now complete and your DNS record values are now generated and visible in Systeme.io settings.

Step 2, Add the CNAME records in Hostinger

This step happens in the Hostinger hPanel. You are adding the three CNAME records generated in Step 1 to your domain’s DNS zone.

Navigate to the DNS Zone editor using this path:

hPanel → Hosting → Manage → DNS Zone

Before adding the records scan the existing DNS entries for any records with Name values that match the ones you are about to add. If any exist from a previous setup delete them before proceeding to avoid conflicts.

For each of the three CNAME records follow these steps.

1. Click Add Record
2. Select CNAME as the record type
3. In the Name field you will enter the subdomain portion of the value shown in Systeme.io. The full value in Systeme.io will look like “si1234567.yourdomain.com” enter only “si1234567” in Hostinger. Do not include your domain name.
4. In the Content or Points To field, paste the value from the Systeme.io Value column exactly as it appears. Do not add spaces before or after. Do not add line breaks.
5. Leave the TTL field at the Hostinger default 14400. Do not change this.
6. Click Save

Repeat for all three CNAME records.

The three records will follow this structure:

The exact values in the Name and Value columns come from your own Systeme.io account. The table above shows the format only, do not use these values directly your values will be different.

Step 2 is now complete: All three CNAME records are saved in your Hostinger DNS zone.

Step 3, Add the DMARC TXT record

Still in the Hostinger DNS Zone editor from Step 2.

The DMARC record tells receiving email servers what to do when an email from your domain fails authentication and where to send reports about those failures. Without it Systeme.io domain authentication will remain incomplete even if the three CNAME records from Step 2 are resolving correctly.

Before adding the record check your existing DNS entries for any TXT record with the Name value _dmarc. If one exists from a previous setup, delete it before proceeding. Two DMARC records on the same domain conflict with each other and will prevent authentication from completing.

Follow these steps to add the DMARC TXT record.

1. Click Add Record
2. Select TXT as the record type
3. In the Name field enter “_dmarc” exactly as shown, including the underscore. Do not add your domain name after it. Hostinger adds that automatically.
4. In the Content field use the DMARC value generated by Systeme.io in Step 1. It will follow this format:

“v=DMARC1; p=none; rua=mailto:youremail@yourdomain.com”

Replace “youremail@yourdomain.com” with a real email address you can access. This is where DMARC diagnostic reports will be sent. A dedicated address for this purpose is preferable to your main inbox, DMARC reports are technical and arrive regularly.

5. Leave the p=none policy value as is. This is the correct setting for a new domain authentication setup. It means emails that fail authentication are still delivered while failures are reported to your rua address. Do not change this to “p=reject” or “p=quarantine” until your authentication has been confirmed as working correctly for an extended period.
6. Leave the TTL field at the Hostinger default, 14400.
7. Click Save

The completed DMARC record will look like this in your DNS zone:

Step 3 complete: The DMARC TXT record is saved in your Hostinger DNS zone. All four authentication records are now in place.

Step 4, Wait for DNS propagation

DNS propagation is the process of a DNS change made in Hostinger spreading across DNS servers around the world. When you save a record in Hostinger it does not update everywhere instantly it spreads gradually over minutes to hours. Most records resolve within 30 minutes to a few hours. Full propagation across all global servers can take up to 24 hours.

Do not delete and re-add records during this period. Deleting a record resets its propagation timer and extends the wait. Check propagation status using DNSChecker before making any changes.

Checking CNAME propagation in DNSChecker

1. Go to dnschecker.org
2. Enter your domain name in the search field
3. Select CNAME from the record type dropdown
4. Click Check DNS
5. Review the results across server locations, green ticks indicate the record is resolving correctly at that location

A small number of servers showing as unresolved during the propagation window is normal. If the majority of servers are showing green within a few hours propagation is progressing correctly.

Checking TXT record propagation in DNSChecker

Repeat the same process for the DMARC TXT record.

1. Go to dnschecker.org
2. Enter your domain name in the search field
3. Select TXT from the record type dropdown
4. Click Check DNS
5. Look for the _dmarc record in the results it should show the DMARC value you entered in Step 3

Both the CNAME records and the TXT record need to be resolved correctly before moving to Step 5.

If records are not showing after 24 hours, go to the troubleshooting section at the end of this guide before making any changes in Hostinger.

Step 4 complete: DNS records are propagating and resolving correctly across global servers as confirmed in DNSChecker.

Step 5, Verify the records in MXToolbox

DNSChecker in Step 4 confirmed that your DNS records have propagated to global servers. MXToolbox does something different: it checks whether the email authentication records are correctly formatted and functioning as intended. A record can propagate correctly and still fail authentication if the values are not formatted correctly.

What MXToolbox checks

MXToolbox checks three email authentication standards simultaneously.

DKIM: DomainKeys Identified Mail. Verified through the CNAME records added in Step 2. Confirms that Systeme.io is authorised to sign emails sent from your domain.

DMARC: Domain-based Message Authentication Reporting and Conformance. Verified through the TXT record added in Step 3. Confirms the policy for handling emails that fail authentication.

SPF: Sender Policy Framework. For Systeme.io domain authentication the CNAME records added in Step 2 handle SPF authorisation. You do not need to add a separate SPF record in Hostinger for Systeme.io.

Running the verification

1. Go to mxtoolbox.com
2. Select DNS Lookup from the menu
3. Enter your domain name
4. Run the test by clicking DNS Lookup
5. Review the results for DKIM, DMARC, and SPF

Reading the results

A passing result for each test indicates that the record is present, correctly formatted, and functioning as intended.

If any test shows as failing, check the following before making changes in Hostinger.

Allow the full 24 hour propagation window to pass if you have not already done so. Records that have not fully propagated may show as failing in MXToolbox before they show as passing.

If DMARC shows as failing after 24 hours, verify that the TXT record Name in Hostinger is exactly “_dmarc” with no additional characters.

If DKIM shows as failing after 24 hours return to Step 2 and verify that all three CNAME record values were entered exactly as generated by Systeme.io with no spaces or line breaks.

Step 5 complete: DKIM, DMARC, and SPF are verified as passing in MXToolbox. Email authentication is correctly configured.

Step 6 Confirm domain verification and sender email in Systeme.io

This step confirms two things inside Systeme.io. First that the domain authentication records are recognised as correctly configured. Second, the sender email address is confirmed and ready to use. Both need to be completed before emails will be sent correctly from your custom domain address.

Checking domain verification status

1. Go to Settings in your Systeme.io account
2. Click Emails in the left sidebar
3. Check Domain Name
4. Check the status displayed next to your domain

The status should now show as Verified.

If the status still shows as Pending after 24 hours go to the troubleshooting section at the end of this guide before making any changes in Hostinger or Systeme.io.

Confirming your sender email address

Domain verification confirms that Systeme.io is authorised to send emails from your domain. The sender email address confirmation is a separate step that confirms the specific “from” address your contacts will see.

1. Still in Settings and in the Emails section
2. Locate the Verified Email Addresses section under the Domains Section, check the status displayed next to your Email Address, it should show as Verified.
3. Locate the Sender Email Section below the Verified Email Address section
4. In the Drop-down menu, select the email address you want to use as your “from” address; this must be an address at your verified domain. For example “hello@yourdomain.com” or “name@yourdomain.com”
5. Click Save Systeme.io will send a confirmation email to that address
6. Open the confirmation email and click the confirmation link

If the confirmation email does not arrive within 10 minutes check your spam folder first. If it is not there, confirm that your domain is resolving to an active website. Systeme.io does not send verification emails to domains that point to blank or parked pages.

Important: the sender email address must be at your authenticated domain. Using a Gmail or Yahoo address as your sender address will cause deliverability problems regardless of whether your domain authentication is complete.

Step 6 complete: Domain verification shows as Verified in Systeme.io and the sender email address is confirmed. The authentication setup is complete and emails sent through Systeme.io will now reach inboxes.

Troubleshooting domain still showing as Pending after 24 hours

Work through the checks below in order before making any changes in Hostinger or Systeme.io. Each check addresses a specific failure condition. Identify which one applies to your setup before taking any action.

Use this section only after the full 24 hour propagation window has passed and after you have checked record status in both DNSChecker and MXToolbox. Changes made before propagation is complete may compound the problem rather than fix it.

Check 1 — Incorrect CNAME Name field entry

The most common CNAME setup mistake is entering the full domain value in the Name field rather than the subdomain portion only.

The Name value in Systeme.io will look like “si1234567.yourdomain.com”. In Hostinger the Name field should contain only “si1234567”. If you entered the full value including your domain name delete the record and re-add it with the subdomain portion only.

Check all three CNAME records for this issue.

Check 2 — Conflicting CNAME records from a previous setup

If you have previously set up Systeme.io domain authentication and are repeating the process your DNS zone may contain old CNAME records with the same Name values as the new ones.

Two records with the same Name value in the same DNS zone conflict with each other and prevent correct resolution. Go to your Hostinger DNS Zone editor and check for duplicate CNAME records with the same Name values. Delete the older versions and keep only the records generated in your current Systeme.io setup.

Check 3 — Spaces or line breaks in pasted values

DNS record values that contain a space or an invisible line break character will fail to resolve correctly even though they appear to be correct when viewed in Hostinger.

This happens most often when values are copied from a PDF, an email, or a formatted document rather than directly from Systeme.io settings.

Delete the affected record. Re-add it by copying the value directly from your Systeme.io settings and pasting into Hostinger without any intermediate application. If the problem persists, retype the value manually rather than pasting.

Check 4 — Conflicting DMARC records

If your domain had an existing DMARC TXT record before you added the one in Step 3 you now have two _dmarc TXT records in your DNS zone. Two DMARC records conflict with each other and will prevent DMARC authentication from completing.

Go to your Hostinger DNS Zone editor and check for TXT records with the Name value _dmarc. If two exist, delete the older one and keep only the record added during this setup.

Check 5 — Domain not connected to an active website

Systeme.io will not complete domain verification for a domain that does not resolve to active content. If your domain is pointing to a parked page, a holding page, or returning an error, connect it to your Hostinger WordPress installation or your Systeme.io funnel page and attempt verification again.

This requirement applies specifically to the Systeme.io verification process. The domain must resolve to live content in the Systeme.io account where authentication is being completed.

Check 6 — Sender email address not at the authenticated domain

If your sender email address in Systeme.io is a Gmail, Yahoo, or any other address not at your authenticated domain, emails will have deliverability problems regardless of whether domain authentication shows as Verified.

Go to Systeme.io Settings, Emails, Under Sender email Section. Confirm that the “from” address is at your authenticated domain. For example “hello@yourdomain.com” not “yourname@gmail.com”.

If all checks pass and the domain still shows as Pending

If you have worked through every check above, confirmed all records are correctly entered in Hostinger, waited the full 24 hour propagation window, and the domain still shows as Pending in Systeme.io the issue is likely account-specific rather than a configuration problem.

Contact Systeme.io support directly with the following information.

Your domain name, the date and time you added the DNS records in Hostinger, A screenshot of your current DNS records in Hostinger DNS Zone editor, A screenshot of the domain status in Systeme.io Settings, Emails, Domains, The results of your DNSChecker and MXToolbox verification.

Providing this information upfront significantly reduces the time to resolution in support conversations.

A note from real experience

A note from the setup

I work full time in construction. This setup got done in the evenings and weekends not during business hours when support is easiest to reach.

During my own Systeme.io domain authentication setup on Hostinger I hit a point where the records looked correct in the DNS zone but I wanted to confirm I had not missed anything before waiting for the full propagation window.

What I found was more useful than I expected.

Hostinger has an AI assistant called Kodee that is connected directly to your account. It is not a generic chatbot that gives you documentation links. It can see your account, answer specific questions about your DNS configuration, connect you to customer support if needed and, this is the part most people do not know, it can make basic changes to your DNS settings directly if you describe what needs to be done.

I used Kodee to confirm my record entries were correct before waiting for propagation. The conversation was specific to my actual DNS zone, not a generic troubleshooting script.

If you hit a wall during this setup and are not sure whether to wait or make a change, open Kodee in your Hostinger hPanel. Describe exactly what you are seeing and what you have already done. It is faster than submitting a support ticket and more specific than searching documentation.

The Kodee assistant is in the bottom right corner of Hostinger hPanel. It is available whether or not Hostinger’s human support team is online.

Complete setup checklist, Systeme.io email authentication with Hostinger DNS

Use this checklist as a final verification once all six steps are complete. Every item should be confirmed before concluding the setup is finished.

Prerequisites

☐ Domain registered and active in Hostinger 

☐ Domain resolving to an active website not a parked or blank page 

☐ Dedicated email address ready for the DMARC rua reporting field

DNS records in Hostinger

☐ Three CNAME records added in Hostinger DNS Zone 

☐ Each CNAME Name field contains the subdomain portion only not the full domain value 

☐ Each CNAME Value field contains the exact value from Systeme.io with no spaces or line breaks 

☐ DMARC TXT record added with _dmarc as the Name real email address in the rua field 

☐ No duplicate CNAME records with the same Name values in the DNS zone 

☐ No duplicate _dmarc TXT records in the DNS zone

Propagation and verification

☐ DNS propagation waited minimum 2 hours before checking, up to 24 hours for full propagation 

☐ DNSChecker used to confirm CNAME records resolving correctly select CNAME from record type dropdown 

☐ DNSChecker used to confirm DMARC TXT record resolving correctly select TXT from record type dropdown 

☐ MXToolbox verification completed DKIM, DMARC, and SPF all passing

Systeme.io confirmation

☐ Domain showing as Verified in Systeme.io Settings, Emails, Domains 

☐ Sender email address entered at the authenticated domain not a Gmail or Yahoo address

☐ Sender email confirmation link clicked from the Systeme.io verification email

If something is not resolving correctly

Before contacting support, open Kodee in Hostinger hPanel. Kodee is connected to your account and can confirm whether your DNS records are correctly configured. It can also make basic DNS changes directly if needed. The Kodee assistant is in the bottom right corner of hPanel.

If all checklist items are confirmed and the domain still shows as Pending work through the troubleshooting section above before contacting Systeme.io support.

What comes next

Domain authentication is the foundation. With your domain verified in Systeme.io and your sender address confirmed your emails will now reach inboxes reliably.

The next step in the setup sequence is building the funnel that collects contacts, the opt-in page and thank you page that connects to your email configuration.

→ How to Build a Simple Funnel in Systeme.io coming soon

If you prefer video the full Systeme.io setup series covering every step in the correct order is on YouTube at LaunchWithDavid.

→ Systeme.io Setup for Beginners playlist, youtube.com/@launchwithdavid

The video companion for this specific article covering the domain authentication process with a live Hostinger DNS walkthrough is here.

→ Systeme.io Emails Not Sending or Going to Spam? Fix It With Hostinger DNS, YouTube

The tools used in this guide

If you are not yet set up on Hostinger or Systeme.io both have free or low cost entry points that cover everything in this guide.

Get started with Systeme.io free plan available: The free plan covers funnels, email, and domain authentication. No credit card required.

Get your domain with Hostinger: Domain registration and hosting. The DNS Zone editor used throughout this guide is inside Hostinger hPanel.

Affiliate disclosure: Some links in this article are affiliate links. If you sign up through them AffiliateTacticHive will earn a commission at no extra cost to you. Every tool linked here is one used on real projects. Full disclosure at affiliatetactichive.com/affiliate-disclosure