Understanding Results

Fuego provides detailed verification results for each email address. This guide will help you understand what each field means and how to use this information effectively.

Result Types

Each verified email will have one of these primary result types:

Result	Description	Recommended Action
deliverable	The email address exists and is deliverable	Safe to use in your campaigns
undeliverable	The email address does not exist or is undeliverable	Remove from your list
risky	The email may have deliverability issues	Use with caution or segment for special handling
unknown	We could not verify the email with confidence	Treat as risky or re-verify later

Reason Codes

The reason field provides more specific information about why an email received its result:

Undeliverable Reasons

invalid_email: The mailbox does not exist on the mail server
invalid_domain: The domain does not exist or has no mail servers
rejected_email: The mail server explicitly rejected this email
invalid_smtp: The email address format is invalid or SMTP validation failed

Risky Reasons

low_deliverability: The domain has accept-all configuration or other known deliverability issues
low_quality: The email address is considered low quality based on various factors

Unknown Reasons

timeout: The verification timed out while connecting to the mail server
no_connect: Could not connect to the mail server
unavailable_smtp: The mail server was unavailable or unresponsive
unexpected_error: An unexpected error occurred during verification

Additional Data Fields

Field	Description
email	The email address that was verified
result	The verification result (deliverable, undeliverable, risky, unknown)
reason	The specific reason for the result
role	Boolean indicating if the email is a role-based address (e.g., support@, info@)
cached	Boolean indicating if the result was from cache or a fresh verification
free	Boolean indicating if the email uses a free provider (e.g., gmail.com)
disposable	Boolean indicating if the email uses a disposable service
accept_all	Boolean indicating if the domain accepts all emails without validation
did_you_mean	Suggested correction for emails with likely typos (null if no suggestion)
domain	The domain part of the email address
user	The username part of the email address
success	Boolean indicating if the API request was successful

Domain Intelligence

The domain_insight field provides valuable information about the organization behind the email domain:

In some cases, this may be a simple string message like “No domain insight available” when we can’t determine organization details. For most business domains, you’ll receive a structured object with the following properties:

Field	Description
category	Type of organization (business, education, government, etc.)
name	Organization name
industry	Industry classification
country	Country code where the organization is based
ticker	Stock ticker symbol (if publicly traded)
employees	Approximate number of employees
description	Brief description of the organization

Using Results Effectively

For Marketing

Segment your lists: Create segments based on verification results
Prioritize outreach: Use domain intelligence to identify high-value prospects
Clean your database: Remove invalid emails to improve deliverability
Protect your sender reputation: Avoid sending to risky emails

For Sales

Qualify leads: Use domain intelligence to qualify leads before outreach
Personalize communication: Tailor messaging based on company information
Prioritize accounts: Focus on organizations in your target industries

For Registration Forms

Prevent fake signups: Block disposable email addresses
Suggest corrections: Use the did_you_mean field to suggest fixes for typos
Enhance user profiles: Add domain intelligence to enrich user data

Common Questions

Why might a valid email be marked as risky?

Several factors can cause a valid email to be marked as risky:

The domain uses catch-all configuration
The domain has temporary mail server issues
The email is a role-based address
The domain has known deliverability problems

What’s the difference between “accept_all” and “catch_all”?

Both indicate that the mail server accepts all email addresses, but:

accept_all: Detected during SMTP conversation
catch_all: Determined through additional domain analysis

Should I remove all risky emails?

Not necessarily. Risky emails may still be deliverable but have a higher chance of bouncing. Consider:

Creating a separate segment for risky emails
Using a more conservative sending strategy
Re-verifying them periodically