Checking now
Is Terms down?
Contacting terms.io from Dallas, Phoenix and San Jose…
- Dallas
- Dallas 2
- Phoenix
- San Jose
Checking now
Is Terms down?
Contacting terms.io from Dallas, Phoenix and San Jose…
terms.io is reachable but answered 403 to our probes. It is probably up and blocking automated or regional traffic — not an outage.
Checked 1 time since
What each region saw
| Region | Result | Response | DNS | TLS expires | Server |
|---|---|---|---|---|---|
| DallasDallas, US | HTTP 403 | 217 ms | 41 ms | — | cloudflare |
| Dallas 2Dallas 2, US | HTTP 403 | 334 ms | 169 ms | — | cloudflare |
| PhoenixPhoenix, US | HTTP 403 | 1007 ms | 159 ms | — | cloudflare |
| San JoseSan Jose, US | HTTP 403 | 985 ms | 1 ms | — | cloudflare |
Redirects: https://terms.io/ (302) → https://www.atom.com/name/Terms.io
Resolves to: 52.20.84.62, 104.18.16.52, 104.18.17.52, 2606:4700::6812:1034, 2606:4700::6812:1134
Median response across regions for each check of terms.io run on this site. Red markers = DOWN.
Not enough checks yet for a chart.
No user reports yet. Anonymous, no account needed.
One tap sends an anonymous report. You can add a comment afterwards.
The server answered HTTP 403 to automated requests from every region. That is a security policy (bot protection or geo-blocking), not an outage — the site is most likely fine in a normal browser.
ipconfig /flushdns, macOS sudo dscacheutil -flushcache.A live badge for your README, docs or status page. It updates on its own, checked from 4 regions.
<a href="https://isitdownorme.com/terms.io" title="terms.io status on IsItDownOrMe"><img src="https://isitdownorme.com/badge/terms.io.svg" alt="terms.io status" height="20"></a>terms.io is reachable but answered 403 to our probes. It is probably up and blocking automated or regional traffic — not an outage. Last checked 15 Nov 2026, 16:38 UTC.
If our servers reach the site but you cannot, the problem is local. Hard-refresh the page, try mobile data instead of Wi-Fi (or the other way round), switch DNS to 1.1.1.1 or 8.8.8.8 and flush your DNS cache, and turn off any VPN, firewall or parental filter that could block the site.
None of the 1 checks of terms.io run here since 15 Nov 2026, 16:35 UTC found it down.
We test from four servers in the United States: two separate networks in Dallas, one in Phoenix and one in San Jose. This check saw: Dallas: HTTP 403 in 217 ms; Dallas 2: HTTP 403 in 334 ms; Phoenix: HTTP 403 in 1007 ms; San Jose: HTTP 403 in 985 ms. If it works from all of them but not for you, your provider or a local block is the likely cause.
Opening this page requests terms.io from four servers in three US cities at once and records the HTTP status, response time, DNS answer and TLS certificate from each. The site counts as DOWN only when most regions fail, so one bad network path can't cause a false alarm.
Verdict rule: DOWN when most regions fail, DEGRADED when some fail or the median exceeds 3 s, RESTRICTED when the site answers 401/403/429 to our probes. Share this page: https://isitdownorme.com/terms.io