DevOps rollout

Pipeline in motion

Progressing through each release checkpoint

Initialize Cloud Infra

Spinning VPCs, subnets, and base services

Running

Prime Delivery Pipeline

CI runners warm, caches hydrated

Queued

Secure Artifacts

Images signed, SBOMs verified

Queued

Deploy Portfolio

Rolling out containers with health gates

Queued

Stabilize Observability

Dashboards green, alerts quiet

Queued
0% complete
Back to projects

Valid8 Email Verification

Asynchronous email verification service with deep SMTP and MX checks.

Problem

  • Regex-only validation wasn’t enough for production data quality and led to higher bounce rates.
  • Needed deeper verification with clear risk signals for downstream systems.

Solution

  • Designed and built the backend for Valid8 with deep validation: MX lookups, SMTP handshakes, and domain-level risk profiling.
  • Supports both real-time checks and bulk list verification.

How it works

  • Celery handles async workloads; Redis caches repeat checks to improve performance and reduce repeated network calls.

Decisions & tradeoffs

  • Optimized for accuracy and scalability using async processing instead of blocking request threads.
  • Used caching to keep costs and latency under control for repeated domains/emails.

Flow

Request / CSV upload
│
├─ Queue job (Celery)
│   ├─ MX lookup
│   ├─ SMTP handshake
│   ├─ Risk profiling
│   └─ Cache results (Redis)
│
└─ Return result / export

Project Info

Type: Email Verification ServiceRole: SoftwareStatus: Production

Key Outcomes

Async at scale
SMTP + MX checks
Bulk + realtime
Redis caching

Tech Stack

FlaskCeleryRedisSMTP/MX checks
GitHubLinkedin
© 2026 Maad Mustafa

Running systems, not just code.