Back to How it Works Index
Technical Deep-Dive

Credentials Vault & DNS Compliance Flow

Understand the core mechanics, queues, and logic routines running on our servers when processing this module.

System Execution Pipeline

Below is the step-by-step sequence of events executed by our background workers.

1

Add SMTP Account

User inputs email credentials in the Connection Wizard.

2

Live SMTP Check

System triggers an EHLO SMTP handshake. If validation passes, credentials are encrypted and stored.

3

OTP Dispatch

An OTP is sent to that specific email inbox. Once validated, status changes to PENDING_DNS.

4

DNS Scan

Background workers resolve the domain's TXT records to confirm SPF, DKIM, and DMARC are active.

5

READY Status

The account joins the active sharding rotation pool.

Developer & Architect Notes

Technical Architecture

This module operates as a stateless service hosted across horizontally scalable server nodes. Distributed state coordinates through highly optimized Redis transactions to ensure consistency without deadlocks.

Vault CryptographyAES-256-CBC with Node.js Crypto
DNS Resolutiondns.resolveTxt + dns.resolveCname

Edge Fail-Safe Rules

Critical protocols (like connection failure retries, cool-down timers, and data limits) are verified before outbound dispatches. Failures degrade gracefully, prioritizing list health and preventing blacklisting.

Verification Window10-Minute Sliding Window
Quota DatabaseMongoDB Plan Enforcement Layer
Technical FAQ

How credentials vault & dns compliance behaves.

Answers about the execution flow, failure handling and limits of this module.

How are my SMTP credentials protected?

Credentials are encrypted at rest with AES-256 in a vault kept separate from your account record, decrypted only in memory at the moment a message is relayed, and never written to logs or shown back to you in full after saving.

Does the platform check my SPF, DKIM and DMARC setup?

Yes. Adding a domain triggers live DNS TXT lookups that report which records are present, valid or misconfigured, so you can fix authentication before it costs you a campaign rather than after.

How do you confirm a sending account actually works?

A real SMTP handshake is performed against the host before the account is accepted, so a wrong password or a blocked port surfaces at setup time instead of mid-campaign.

What happens if I hit my plan's domain or mailbox limit?

Quotas are enforced at the API level. You are prompted to upgrade rather than silently charged for the overage or allowed to exceed the limit.