Email Validation Glossary
Every term you need to understand email validation, sending, and deliverability. 50+ definitions with cross-references and practical context.
A
Accept-All (Catch-All)
A mail server configuration where the server accepts mail for any address at the domain, whether the mailbox exists or not. This makes individual mailbox verification impossible because the server returns a positive response for every address.
Why it matters: Accept-all domains inflate your list with potentially invalid addresses. Since the server never rejects, you cannot confirm deliverability through SMTP verification alone. Marking these addresses separately lets you make informed decisions about whether to send.
B
BIMI (Brand Indicators for Message Identification)
A DNS-based protocol that allows domain owners to display their brand logo next to authenticated emails in supporting email clients. BIMI requires a DMARC policy of quarantine or reject, a Verified Mark Certificate (VMC) from a qualifying certificate authority, and an SVG Tiny PS logo published at a specific DNS TXT record.
Why it matters: BIMI provides a visible trust signal in the inbox, increasing brand recognition and recipient confidence. Because it requires strict DMARC enforcement, adopting BIMI also strengthens your overall authentication posture. Recipients are more likely to open and engage with emails that display a recognizable brand logo.
Bounce (Email Bounce)
When an email cannot be delivered and is returned to the sender. Bounces are classified as hard (permanent) or soft (temporary). The bounce message, also called a Non-Delivery Report (NDR), contains diagnostic codes that explain the failure reason.
Why it matters: Bounces directly damage your sender reputation. ISPs track bounce rates per sender and start throttling or blocking delivery when rates exceed 2%. Processing bounces quickly and removing failed addresses is essential for maintaining inbox placement.
Bounce Processing
The automatic handling of bounce notifications returned by receiving mail servers. A bounce processing system parses Non-Delivery Reports (NDRs), classifies them as hard or soft bounces, correlates them to the original recipient using VERP or message headers, and updates suppression lists accordingly.
Why it matters: Without automated bounce processing, failed addresses accumulate in your list and generate repeated bounces that compound reputation damage. Manual bounce handling does not scale beyond a few hundred emails. Automated processing ensures hard bounces are suppressed immediately and soft bounce patterns are tracked over time.
Bounce Rate
The percentage of sent emails that bounce. Calculated as (bounced emails / total emails sent) x 100. ISPs flag senders with bounce rates above 2% as suspicious, and rates above 5% can lead to account suspension with email service providers.
Why it matters: Bounce rate is one of the most closely monitored sender metrics. A single campaign with a high bounce rate can damage your domain reputation for weeks. Regular list validation before sending keeps bounce rates well below the danger threshold.
C
Click-Through Rate (CTR)
The percentage of email recipients who clicked at least one link in an email. Calculated as (unique clicks / emails delivered) x 100. CTR measures the overall effectiveness of an email at driving action, combining both the open and content engagement steps.
Why it matters: CTR is a more reliable engagement metric than open rate because it requires a deliberate action from the recipient. ISPs use click behavior as a positive engagement signal when evaluating sender reputation. A declining CTR often indicates list fatigue, irrelevant content, or deliverability problems that need investigation.
Click-to-Open Rate (CTOR)
The percentage of email openers who clicked a link. Calculated as (unique clicks / unique opens) x 100. Unlike CTR, which measures the full funnel from delivery to click, CTOR isolates content engagement by only considering recipients who already opened the message.
Why it matters: CTOR reveals whether your email content and calls to action are effective, independent of subject line performance or deliverability. A high open rate with a low CTOR means your subject line works but the content does not compel action. CTOR is especially useful for A/B testing email body content and layout.
Complaint Rate
The percentage of recipients who mark an email as spam. Calculated as (spam complaints / emails delivered to inbox) x 100. Google and Yahoo require complaint rates below 0.3% for bulk senders. Microsoft uses similar thresholds through their Smart Network Data Services (SNDS) program.
Why it matters: Complaint rate is the fastest way to destroy sender reputation. Even a brief spike above 0.3% can trigger spam filtering for your entire domain. Validating addresses, using confirmed opt-in, and honoring unsubscribes keeps complaint rates low.
Conversion Attribution
The process of connecting email interactions (opens, clicks) to downstream business actions such as purchases, signups, or form submissions. Attribution models range from simple last-click (crediting the most recent email interaction) to multi-touch models that distribute credit across multiple touchpoints in the customer journey.
Why it matters: Without attribution, you cannot measure the true ROI of your email program. Knowing which campaigns, segments, and send times drive actual conversions lets you optimize spending and focus on high-performing strategies. Attribution also helps justify email marketing budgets with concrete revenue data.
D
DANE/TLSA (DNS-Based Authentication of Named Entities)
A protocol defined in RFC 6698 that uses DNSSEC to publish TLS certificate information in DNS TLSA records. For email, DANE allows a receiving mail server to advertise its TLS certificate fingerprint in DNS, enabling sending servers to verify they are connecting to the authentic server and not a man-in-the-middle.
Why it matters: DANE eliminates the need to trust certificate authorities for SMTP connections by anchoring trust in DNSSEC-validated DNS records. It provides stronger transport encryption guarantees than opportunistic TLS alone, preventing downgrade attacks where an attacker strips STARTTLS from the connection. DANE adoption is growing, particularly among European ISPs and government domains.
Disposable Email Address
A temporary email address from services like Mailinator, Guerrilla Mail, or Temp Mail. These addresses are created for one-time use and are typically abandoned within hours or days. MailOdds detects 190,000+ disposable domains through a continuously updated database.
Why it matters: Disposable addresses signal low-intent users who do not want ongoing communication. Sending to abandoned disposable addresses generates bounces and wastes resources. Detecting and flagging them at signup lets you enforce business email requirements or adjust your engagement expectations.
DKIM (DomainKeys Identified Mail)
An email authentication method that allows the sender to digitally sign emails with a cryptographic key. The sending server adds a DKIM-Signature header to each message, and the receiving server verifies this signature against a public key published in the sender's DNS records. Modern implementations use dual signing with both Ed25519 (compact, fast) and RSA (broad compatibility) to maximize verification coverage across all receiving servers.
Why it matters: DKIM proves that an email was authorized by the domain owner and was not modified in transit. Without DKIM, receiving servers cannot verify message integrity, which reduces trust and deliverability. DKIM is required by Google and Yahoo for bulk senders. MailOdds uses dual DKIM signing (Ed25519 + RSA-2048) on all outbound mail to ensure signatures verify regardless of whether the receiving server supports modern or legacy algorithms.
DMARC (Domain-based Message Authentication, Reporting, and Conformance)
An email authentication protocol that builds on SPF and DKIM. DMARC tells receiving servers what to do with emails that fail authentication: none (monitor only), quarantine (send to spam), or reject (block entirely). It also provides reporting so domain owners can see who is sending email on their behalf. DMARC alignment ensures the domain in the visible From header matches the domains used in SPF and DKIM checks, preventing spoofing even when individual checks pass.
Why it matters: DMARC closes the gap between SPF and DKIM by adding a policy layer and alignment checks. Without DMARC, spoofed emails can pass SPF or DKIM individually while still impersonating your domain. DMARC with a reject policy provides the strongest protection against phishing. MailOdds enforces strict DMARC alignment on all sending domains, with org-domain fallback for subdomains, ensuring your messages consistently pass authentication at receiving servers.
DNS (Domain Name System)
The system that translates human-readable domain names (like mailodds.com) to IP addresses. In the context of email, DNS stores critical records including MX records (which servers receive email), SPF records (which servers are authorized to send), DKIM public keys, and DMARC policies.
Why it matters: Email validation uses DNS lookups as an early verification step. If a domain has no MX records, it cannot receive email, and any address at that domain is invalid. DNS misconfigurations are a common cause of deliverability problems.
Domain Warmup
The process of gradually increasing email sending volume from a new domain to establish a positive sending reputation with ISPs. Similar to IP warmup but focused on domain reputation, which persists even when switching IPs. A typical domain warmup takes 2 to 4 weeks, starting with small volumes sent to the most engaged recipients.
Why it matters: Domain reputation is increasingly the primary factor ISPs use for filtering decisions, especially at Gmail and Microsoft. Even with a warm IP, a new domain starts with no reputation and will face throttling or spam placement if volume ramps too quickly. A disciplined domain warmup, paired with clean lists and strong authentication, builds the foundation for long-term deliverability.
E
Email Validation
The process of checking whether an email address is valid, deliverable, and safe to send to. A comprehensive validation pipeline includes syntax checking (RFC 5322 compliance), DNS verification (MX record lookup), SMTP verification (mailbox existence check), and reputation analysis (disposable, role account, and spam trap detection).
Why it matters: Email validation is the foundation of list hygiene. Without it, you are sending blind, accumulating bounces, hitting spam traps, and degrading your sender reputation with every campaign. Validating before sending is cheaper and more effective than dealing with deliverability problems after the fact.
Email Verification
Often used interchangeably with email validation. Technically, verification specifically refers to confirming the mailbox exists via SMTP commands, while validation is the broader process that includes syntax checks, DNS lookups, and reputation analysis.
Why it matters: Understanding the distinction helps when evaluating email validation services. A service that only performs SMTP verification misses syntax errors, disposable domains, and role accounts. Full validation covers all layers for the most accurate results.
Engagement Scoring
A system that assigns a numerical score to each recipient based on their interaction patterns with your emails. Scoring factors typically include recency and frequency of opens, clicks, replies, forwards, website visits after clicking, and purchases. Scores decay over time for inactive recipients and increase with each positive interaction.
Why it matters: Engagement scoring enables data-driven segmentation for send frequency, content personalization, and re-engagement campaigns. Sending primarily to engaged recipients improves deliverability because ISPs reward high engagement rates with better inbox placement. Scoring also identifies candidates for suppression before they become complainers or spam trap risks.
Envelope Sender (Return-Path)
The email address where bounces are sent, specified in the SMTP MAIL FROM command. This is different from the From header visible to recipients. The envelope sender is set by the sending infrastructure and is used for SPF alignment and bounce processing.
Why it matters: A properly configured return-path is essential for bounce processing. Without it, you cannot track which emails bounced or correlate bounces to specific recipients. VERP encoding in the return-path enables automated, per-recipient bounce handling at scale.
ePrivacy Directive
EU Directive 2002/58/EC (amended by 2009/136/EC) governing privacy in electronic communications. It regulates the use of cookies, tracking pixels, and similar technologies that access information on a user's device. The directive requires informed consent before placing tracking technologies, with limited exceptions for technologies strictly necessary for service delivery.
Why it matters: The ePrivacy Directive applies directly to email tracking pixels and web beacons used to measure opens and engagement. Senders targeting EU recipients must consider whether their tracking practices require consent under applicable national implementations. As open-rate tracking becomes less reliable due to both privacy regulations and technical changes like Apple MPP, senders are shifting toward click-based and conversion-based metrics.
F
Feedback Loop (FBL)
A service provided by ISPs that notifies senders when recipients mark their emails as spam. Major providers like Yahoo, Outlook, and Comcast offer FBL programs. Gmail uses a different mechanism through Postmaster Tools rather than traditional FBL reports.
Why it matters: Processing FBL reports and immediately removing complainers is critical for maintaining sender reputation. Continuing to send to recipients who have complained triggers escalating penalties from ISPs, potentially leading to full domain or IP blocks.
Free Email Provider
Email services like Gmail, Yahoo, Outlook, and ProtonMail that offer free email accounts to anyone. Free email addresses are legitimate but may indicate consumer rather than business users. Some B2B companies restrict signups to business (corporate) domains only.
Why it matters: Knowing whether an address is from a free provider helps segment your audience. For B2B lead generation, a high percentage of free email signups may indicate low-quality leads. For B2C, free email addresses are perfectly normal and expected.
G
Greylisting
A spam filtering technique where the mail server temporarily rejects emails from unknown senders with a "try again later" response (4xx SMTP status code). Legitimate mail servers retry delivery after a delay; spammers typically do not. The greylisting server remembers the sender and accepts subsequent attempts.
Why it matters: Greylisting causes false negatives in email validation if the validation service does not handle retries properly. A naive SMTP check would see the temporary rejection and incorrectly mark the address as undeliverable. MailOdds accounts for greylisting in its verification process.
H
Hard Bounce
A permanent delivery failure indicated by a 5xx SMTP status code. Common causes include: the mailbox does not exist (550 User unknown), the domain is invalid or has no MX records, or the server permanently refuses delivery for policy reasons.
Why it matters: Hard bounced addresses should be immediately and permanently removed from your list. Unlike soft bounces, hard bounces will never resolve on retry. Sending repeatedly to hard-bounced addresses is the fastest way to damage your sender reputation and get blacklisted.
I
IP Reputation
A score assigned to a sending IP address based on its email sending history. Factors include bounce rates, complaint rates, spam trap hits, volume consistency, and authentication compliance. Services like Sender Score (by Validity), Barracuda Reputation, and Google Postmaster Tools track IP reputation.
Why it matters: Your sending IP's reputation directly determines whether your emails reach the inbox. A low IP reputation means emails are sent to spam or blocked entirely, regardless of content quality. Shared IPs (common with email service providers) mean other senders' behavior affects your deliverability.
IP Warmup
The process of gradually increasing email volume from a new or dormant IP address to build sender reputation with ISPs. A typical warmup schedule starts with a few hundred emails per day and doubles volume every few days over 2 to 4 weeks, prioritizing the most engaged recipients first.
Why it matters: Sending a large volume from a new IP without warmup triggers spam filters because ISPs have no sending history to evaluate. A proper warmup plan, combined with clean lists and strong authentication, establishes your IP as a trustworthy sender from the start.
ISP Throttling
Rate limiting imposed by receiving mail servers that restricts how many emails a sender can deliver within a given time window. Throttling is based on sender reputation, sending volume, recipient engagement, and authentication compliance. Common throttling responses include 4xx temporary deferrals with messages like "too many connections" or "rate limit exceeded."
Why it matters: Throttling is an early warning sign of reputation problems. ISPs throttle before they block, so hitting throttle limits repeatedly without adjusting indicates that your sending practices or list quality need attention. Properly handling throttle responses (backing off and retrying with exponential delay) prevents temporary deferrals from escalating to permanent blocks.
M
MTA-STS (Mail Transfer Agent Strict Transport Security)
A protocol defined in RFC 8461 that allows a receiving domain to declare that it supports TLS for inbound email and that sending servers should refuse to deliver over unencrypted connections. The policy is published as a text file at a well-known HTTPS URL and advertised via a DNS TXT record. MTA-STS does not require DNSSEC, unlike DANE.
Why it matters: MTA-STS prevents TLS downgrade attacks where an attacker intercepts the SMTP connection and strips the STARTTLS offer, forcing plaintext delivery. Without MTA-STS or DANE, sending servers fall back to unencrypted delivery if STARTTLS negotiation fails, exposing message contents. MTA-STS is simpler to deploy than DANE because it uses standard HTTPS infrastructure instead of requiring DNSSEC.
MX Record (Mail Exchange Record)
A DNS record that specifies which mail servers accept email for a domain. MX records include a priority value (lower number = higher priority) that determines the order in which servers are tried. A domain can have multiple MX records for redundancy.
Why it matters: If a domain has no MX records, it cannot receive email, and any address at that domain is definitively invalid. MX record lookup is one of the earliest and most efficient checks in the email validation pipeline, quickly eliminating addresses at non-email domains.
O
Open-Rate Inflation (Apple MPP)
The artificial inflation of email open rates caused by Apple Mail Privacy Protection (MPP), introduced in iOS 15, macOS Monterey, and later. MPP pre-fetches all email content, including tracking pixels, through Apple proxy servers regardless of whether the recipient actually reads the message. This registers a false open for every email delivered to an Apple Mail user with MPP enabled.
Why it matters: Apple MPP made open rate an unreliable metric for a significant portion of email recipients. Depending on your audience, 40% to 60% of opens may be machine-generated. Senders should shift to click-based metrics (CTR, CTOR) and conversion data for measuring engagement. Segmentation strategies that relied on opens to identify active subscribers need to incorporate click and purchase signals instead.
R
RFC 5321
The Internet standard (published by the IETF) that defines the Simple Mail Transfer Protocol (SMTP). It specifies how email is transmitted between servers, including the SMTP commands (EHLO, MAIL FROM, RCPT TO, DATA), response codes, and address format requirements for the message envelope.
Why it matters: RFC 5321 defines the rules that all email servers must follow. Understanding these rules explains why certain addresses are valid or invalid at the protocol level, and why SMTP verification works the way it does.
RFC 5322
The Internet standard that defines the format of email messages, including header fields (From, To, Subject, Date) and the addr-spec syntax for email addresses. It specifies which characters are allowed in the local part and domain of an email address.
Why it matters: Email validation uses RFC 5322 rules as the first layer of syntax checking. Addresses that violate these rules are invalid regardless of whether the domain or mailbox exists. Proper syntax validation catches malformed addresses before more expensive DNS and SMTP checks.
Role Account
An email address associated with a function or department rather than a specific person. Common examples include info@, support@, admin@, sales@, billing@, webmaster@, and postmaster@. Role accounts typically forward to multiple recipients or are managed by teams.
Why it matters: Role accounts have higher complaint rates because messages reach multiple people who may not have individually opted in. Many email marketing best practices recommend excluding role accounts from marketing campaigns. MailOdds flags role accounts so you can handle them separately.
S
Sender Reputation
An overall score that ISPs assign to a sender based on multiple signals: bounce rates, complaint rates, spam trap hits, engagement metrics (opens, clicks, replies), volume consistency, authentication compliance, and sending patterns. Reputation is tracked per domain and per IP.
Why it matters: Sender reputation is the single biggest factor in email deliverability. A strong reputation means inbox placement; a poor reputation means spam folder or outright blocking. Every email decision, from list acquisition to sending frequency, affects your reputation. Validation protects it by preventing bounces and spam trap hits.
SMTP (Simple Mail Transfer Protocol)
The standard protocol for transmitting email between servers, defined in RFC 5321. An SMTP session involves a series of commands: EHLO (identify the sender), MAIL FROM (specify the envelope sender), RCPT TO (specify the recipient), and DATA (transmit the message content). Servers respond with numeric status codes.
Why it matters: SMTP is the foundation of all email delivery. Understanding SMTP helps explain how email validation works, why certain addresses cannot be verified, and what bounce codes mean. SMTP verification leverages the protocol to check mailbox existence without sending a message.
SMTP Relay
The process of forwarding email through an intermediary SMTP server rather than delivering directly from the originating server to the recipient's mail server. Relay services accept outbound email from your application or mail server and handle delivery, including queue management, retry logic, TLS negotiation, and IP reputation management.
Why it matters: Using an SMTP relay offloads the complexity of email delivery infrastructure from your application. Relay providers maintain warm IP pools, handle throttling and retries, and provide delivery analytics. For senders without the volume or expertise to manage their own sending infrastructure, a relay service provides better deliverability than sending from application servers directly.
SMTP Verification
The process of connecting to a recipient's mail server and using SMTP commands (EHLO, MAIL FROM, RCPT TO) to check if a mailbox exists and accepts mail, without actually sending a message. The session is terminated before the DATA command. This is the most accurate form of email validation.
Why it matters: SMTP verification is the gold standard for confirming deliverability because it checks the actual mail server. However, it has limitations: catch-all servers always accept, some servers block verification attempts, and greylisting can cause false negatives. A robust validation service handles all these edge cases.
Soft Bounce
A temporary delivery failure indicated by a 4xx SMTP status code. Common causes include: the mailbox is full (over quota), the server is temporarily unavailable, the message is too large, or the server is applying greylisting. Sending servers typically retry delivery for soft bounces.
Why it matters: Soft bounces may resolve on retry, but addresses that consistently soft bounce should be removed from your list. A pattern of repeated soft bounces to the same address indicates an abandoned mailbox or persistent server issues. Most email platforms suppress addresses after 3 to 5 consecutive soft bounces.
Spam Trap
An email address used by ISPs and anti-spam organizations to identify senders with poor list hygiene. There are two main types: recycled spam traps (old, abandoned addresses repurposed for monitoring) and pristine spam traps (addresses that were never used by a real person and should never receive email).
Why it matters: Sending to a spam trap is one of the most damaging things you can do to your sender reputation. A single pristine spam trap hit can cause immediate blacklisting. Recycled traps indicate you are not cleaning your list regularly. Email validation helps by identifying addresses that show characteristics of spam traps.
SPF (Sender Policy Framework)
An email authentication method where domain owners publish a DNS TXT record listing the IP addresses and servers authorized to send email on behalf of their domain. Receiving servers check the sending IP against the SPF record to verify authorization.
Why it matters: SPF prevents unauthorized servers from sending email as your domain. Without SPF, anyone can forge your domain in the envelope sender, enabling phishing attacks. SPF is one of the three authentication pillars (along with DKIM and DMARC) required by Google and Yahoo for bulk senders.
Suppression List
A centralized list of email addresses that must not receive email. Suppression lists aggregate addresses from multiple sources: hard bounces, spam complaints (via FBL), manual unsubscribes, role accounts flagged for exclusion, and addresses added by compliance or legal requirements. The suppression list is checked before every send to prevent delivery to any listed address.
Why it matters: A well-maintained suppression list is the last line of defense against sending to addresses that will generate bounces, complaints, or legal violations. Failing to suppress hard bounces leads to repeated delivery failures that compound reputation damage. Failing to suppress complainers or unsubscribers can violate CAN-SPAM, GDPR, and CASL regulations, resulting in fines and blacklisting.
Syntax Validation
The first step in email validation: checking that the email address conforms to the format rules defined in RFC 5322. This includes verifying the presence of exactly one @ sign, valid characters in the local part and domain, proper domain format, and reasonable length limits.
Why it matters: Syntax validation is fast, free, and catches the most obvious errors: missing @ signs, spaces, invalid characters, and malformed domains. It is the cheapest validation step and should be applied in real-time on signup forms to catch typos before they enter your database.
T
TLS-RPT (TLS Reporting)
A reporting mechanism defined in RFC 8460 that allows domain owners to receive reports about TLS connection failures when other servers attempt to deliver email to their domain. The domain publishes a DNS TXT record specifying where to send reports, and sending servers that support TLS-RPT generate daily aggregate reports detailing successful and failed TLS negotiations.
Why it matters: TLS-RPT provides visibility into transport encryption failures that would otherwise go undetected. Without reporting, a misconfigured certificate or a downgrade attack could silently cause email to be delivered in plaintext or deferred entirely. TLS-RPT works alongside MTA-STS and DANE to create a complete transport security monitoring system.
Tracking Pixel
A 1x1 transparent image embedded in an email that loads from the sender's server when the recipient opens the message. The HTTP request generated by loading the image records the open event along with metadata such as the time, IP address, and email client. Tracking pixels are the standard mechanism for measuring email open rates.
Why it matters: Tracking pixels have been the primary open-rate measurement tool for decades, but their reliability has declined significantly. Apple Mail Privacy Protection pre-fetches all images (inflating open rates), some email clients block remote images by default, and privacy regulations like the ePrivacy Directive may require consent for tracking. Senders should treat open rates as directional rather than precise and supplement with click and conversion metrics.
Typo Detection
An email validation feature that identifies common misspellings in email domains and suggests corrections. Examples include gmial.com instead of gmail.com, yaho.com instead of yahoo.com, and hotmal.com instead of hotmail.com. Advanced typo detection also catches local-part patterns.
Why it matters: Typos are the most fixable category of invalid addresses. Rather than silently rejecting a mistyped address, suggesting a correction recovers a valid lead or customer. Real-time typo detection on signup forms dramatically reduces bounce rates from new registrations.
V
VERP (Variable Envelope Return Path)
A technique where each outgoing email gets a unique return-path address that encodes the recipient information. For example, bounce+user=example.com@sender.com encodes that the original recipient was user@example.com. When the email bounces, the encoded return-path identifies exactly which recipient failed.
Why it matters: Without VERP, bounce processing relies on parsing the bounce message body, which varies wildly between mail servers and is unreliable. VERP provides deterministic bounce attribution regardless of the receiving server's bounce format, enabling accurate automated bounce handling at scale.
W
Web Pixel
A JavaScript snippet installed on a website that tracks visitor behavior after they click through from an email. Web pixels record page views, form submissions, purchases, and other conversion events, connecting them back to the email campaign and recipient that generated the visit. Common implementations include first-party tracking scripts and tag manager integrations.
Why it matters: Web pixels bridge the gap between email engagement and business outcomes. Without post-click tracking, you know someone clicked a link but not whether they converted. Web pixel data feeds conversion attribution models, enables revenue-per-email calculations, and provides the signals needed for engagement scoring that goes beyond inbox behavior.
Related Resources
Email Deliverability Guide
Put these concepts into practice with authentication and list hygiene strategies.
How to Choose a Validation API
Evaluation framework for comparing email validation providers.
GDPR Compliance Guide
Data residency and compliance for EU email validation.
Free Email Validator
Try validation in your browser with no signup required.
Ready to validate your email list?
MailOdds checks every term on this page in one API call: syntax, DNS, SMTP verification, disposable detection, role account flagging, and more.