Skip to contentAPILayer: production APIs with free plansExplore APILayer

Is TrustLookup API down?

Current status, daily uptime history and troubleshooting for the TrustLookup API (Email).

No, TrustLookup is up

TrustLookup answered our last daily check (Nov 15, 2026, 13:58 UTC) in 1247 ms with HTTP 200.

Checking TrustLookup now…

Sending a request from our server.

TrustLookup API uptime history

30 days agoLatest check
Uptime
100% of 4 checks
Last check
Nov 15, 2026, 13:58 UTC
Response
1247 ms · HTTP 200
Last up
Now

We check TrustLookup's listed URL (https://trustlookup.io/docs) once a day. History started when TrustLookup was first checked, so new entries show fewer than 30 days.

TrustLookup API not working for you?

  1. TrustLookup needs an API key. A 401 or 403 usually means a missing, expired or mis-sent credential: check whether it belongs in a header or the query string.
  2. A 429 response means you're being rate-limited. Slow down, cache responses, and respect any Retry-After header.
  3. TrustLookup doesn't send CORS headers, so browsers block calls made directly from a web page. Call it from your server instead.
  4. If it works from one network but not another, check firewalls, VPNs and regional blocks.
  5. Check the provider's documentation, status page or social accounts for planned maintenance or a changed endpoint.

Email APIs up at their last check

  1. 1Kickbox logo

    Kickbox API

    Online · 754 ms

    Email verification API. A free email API by Powered by Kickbox.

    • No API key needed
    • 100% uptime (30 days)
    • Callable from the browser (CORS)
    • HTTPS
    No authHTTPSCORS
  2. 2mail.gw logo

    mail.gw API

    Online · 602 ms

    API for creating temporary email accounts.

    • No API key needed
    • 100% uptime (30 days)
    • Callable from the browser (CORS)
    • HTTPS
    No authHTTPSCORS
  3. 3mail.tm logo

    mail.tm API

    Online · 625 ms

    Temporary Email Service. A free email API by Mail.tm.

    • No API key needed
    • 100% uptime (30 days)
    • Callable from the browser (CORS)
    • HTTPS
    No authHTTPSCORS
  4. 4StopMailing logo

    StopMailing API

    Online · 738 ms

    Disposable email addresses with a free, no-signup REST API.

    • No API key needed
    • 100% uptime (30 days)
    • Callable from the browser (CORS)
    • HTTPS
    No authHTTPSCORS
  5. 5Vetto logo

    Vetto API

    Online · 1170 ms

    Check email domains in bulk for disposable providers and dead domains, no key needed.

    • No API key needed
    • 100% uptime (30 days)
    • Callable from the browser (CORS)
    • HTTPS
    No authHTTPSCORS

Compare all TrustLookup alternatives · APIs down right now

TrustLookup API status FAQ

Is TrustLookup API down right now?

TrustLookup answered our last daily check (Nov 15, 2026, 13:58 UTC) in 1247 ms with HTTP 200. This page also runs a live check from our server when you open it, so you can see whether TrustLookup is responding at this moment.

How do you check whether TrustLookup API is up?

Once a day our checker requests TrustLookup's listed URL (https://trustlookup.io/docs) and records whether it answers within 15 seconds. Answers like 401 (needs a key), 403 (blocks bots) or 429 (rate-limited) count as up, because the server responded. The listed URL is often the documentation page, so an API endpoint can occasionally fail while its docs stay up.

How reliable is TrustLookup API?

TrustLookup answered 100% of our last 4 daily checks. Above 99% is excellent for a free API; below 95% means you should cache responses and keep a fallback ready.

What can I use if TrustLookup API is down?

Free Email APIs that were up at their last check include Kickbox, mail.gw, mail.tm. See the full list of TrustLookup alternatives for a comparison.

Why does TrustLookup API work for others but not for me?

TrustLookup needs an API key. A 401 or 403 usually means a missing, expired or mis-sent credential: check whether it belongs in a header or the query string. A 429 response means you're being rate-limited. Slow down, cache responses, and respect any Retry-After header. TrustLookup doesn't send CORS headers, so browsers block calls made directly from a web page. Call it from your server instead.