📖 Documentation & API
🔧 How It Works
Validation Process:
Regex Validation: Checks email format and syntax
MX Records: Verifies domain has mail servers
SMTP Validation: Tests actual mailbox existence
✅ SMTP Validation Details:
No emails are sent - Only SMTP handshake verification
Uses Amazon SES for authentication but validates against target domain servers
Production-grade validation with proper error handling and retry logic
Will NOT count against SES sending limits since no emails are actually sent
🔌 API Access
Endpoint:
GET https://truemail.computerdx.com/api/?email=ADDRESS
Authentication:
Authorization: truemail-prod-token
Example cURL Request:
curl -H "Authorization: truemail-prod-token" \
"https://truemail.computerdx.com/api/?email=test@example.com"
Response Format:
{
"success": true/false,
"email": "test@example.com",
"validation_type": "smtp",
"errors": {},
"smtp_debug": [...],
"mail_servers": [...],
"date": "2025-01-01 12:00:00 +0000"
}
💡 Usage Instructions
Web Interface:
Enter any email address in the form above
Select validation methods (all recommended for comprehensive checking)
Click "Validate Email" to see detailed results
Review step-by-step validation breakdown
API Integration:
Use GET requests with email as query parameter
Include authorization header with provided token
Parse JSON response for validation results
Check 'success' field for overall pass/fail status
💰 Cost-Effective: SMTP validation uses authentication but doesn't send emails,
so it won't consume your SES sending quota or incur sending charges.
⚙️ System Configuration
Current Settings:
Verifier Domain: computerdx.com
SMTP Provider: Amazon SES (us-east-2)
Timeout Settings: 5s connection, 5s response, 3 attempts
Validation Types: All enabled (regex, mx, smtp)
Safe Check: Enabled (parses SMTP error messages)
Debug Mode: Enabled (detailed SMTP logs)
Whitelisted Domains Full Validation
gmail.com, yahoo.com, hotmail.com, outlook.com, computerdx.com
🛡️ Security & Access
🔐 Protected Service: This dashboard is secured with basic authentication
and should only be accessed by authorized personnel.
Access Credentials:
- Authentication: HTTP Basic Auth required
- Contact: System administrator for access credentials
API Token Management:
API tokens should be rotated regularly
Current token is configured in Kubernetes secrets
Contact system administrator for token rotation
📊 Understanding Results
Validation Statuses:
✅ Passed: Validation step completed successfully
❌ Failed: Validation step found an issue
⚪ Skipped: Step skipped due to previous failure
Common Scenarios:
All Green (✅✅✅): Valid, deliverable email address
Regex Fail (❌⚪⚪): Invalid email format
MX Fail (✅❌⚪): Domain doesn't accept email
SMTP Fail (✅✅❌): Domain exists but mailbox doesn't