Skip to content
English
Back to directory

nextjs.org

200 OK

Next.js brings routing, rendering, and server features to React

Developer ToolsGoogle AnalyticsNext.jsReact

Current website response

The latest stored check is a dated observation, not a live uptime guarantee.

Rechecks public website and registration data
HTTP
200
Observed
Request time
97 ms
Last checked
Observed
Aug 27, 2026
UTC
TLS expires
Oct 21, 2026
HTTPS certificate

Public DNS records

A
216.230.86.1
MX
1 aspmx.l.google.com.10 alt3.aspmx.l.google.com.10 alt4.aspmx.l.google.com.5 alt1.aspmx.l.google.com.5 alt2.aspmx.l.google.com.
NS
ns1.vercel-dns.com.ns2.vercel-dns.com.
TXT
google-site-verification=BsXDDAvxM3KYqCMD-vaPIxduP9YLqllhaBlERyhjsgwgoogle-site-verification=VUelRm0rDJ9Mxpi3RYfJ0M_Qqbxyo8mSYdn0grLEFIUgoogle-site-verification=h7m7xPSl46-ALWigMUJfFFOFZjKe3jZECHyXSomzXvMgoogle-site-verification=roTfUbzRkjTgiiXb6Lbsh2sQyaAlS_sN32t5nMz8kTQv=spf1 include:_spf.google.com include:servers.mcsv.net include:sendgrid.net ~all
CAA
0 issue "letsencrypt.org0 issue "pki.goog0 issue "sectigo.com
SOA
ns1.vercel-dns.com. hostmaster.nsone.net. 1655261024 43200 7200 1209600 600
No response
AAAACNAMESRVHTTPSSVCBNAPTRDSDNSKEY

HTTPS certificate

Issuer
Let's Encrypt
Expires
Oct 21, 2026
Protocol
HTTPS

Recent observations

Newest first. Refreshing creates another dated observation instead of replacing history.

ObservedHTTPResponse and latencyVerdict
20097 msSafe
200395 msSafe

How to read the status cards

The status view describes how nextjs.org responded when the displayed checks were performed. It concerns the official Next.js website and documentation endpoint, not the availability of every application built with Next.js.

Use the timestamp shown with each card. HTTP responses, certificates, and DNS records can change, so an older result should be treated as historical evidence rather than a promise about the present.

What each signal means

Card What it can establish What it cannot establish
HTTP Whether the tested URL returned a response and which status class was observed That every page, region, or future request will respond identically
TLS Whether the tested connection presented a certificate accepted for that hostname at that time That all content, packages, or third-party links are trustworthy
DNS Which public records were returned for the hostname during the lookup Permanent ownership, future routing, or private infrastructure details

An HTTP 2xx response generally indicates that the request succeeded. A 3xx response indicates redirection and should be followed to its final official destination. A 4xx result may reflect a missing page, access rule, or unsuitable request, while a 5xx result indicates that the responding service could not complete the request.

Useful follow-up checks

  • Open https://nextjs.org/docs when looking for maintained framework documentation.
  • Confirm that the browser remains on nextjs.org after any redirect.
  • Check certificate dates and the exact hostname if a TLS warning appears.
  • Retry unexpected failures from another connection before assuming a broad outage.
  • Consult the official repository when the website and installed package documentation appear inconsistent.

A healthy website response does not validate an application's architecture or dependencies. Conversely, a temporary website failure does not mean that deployed Next.js applications have stopped working. Interpret every card within its stated hostname, time, and request scope.

Continue exploring

More published records in Developer Tools.

View all alternatives

How Astro turns content into HTML and adds interaction selectively

Developer ToolsTailwind CSS

Gatsby connects React websites to structured content and flexible rendering

Developer ToolsGoogle Analytics

nuxt.com

200 OK

Build Vue websites and applications with routing, server logic and flexible rendering

Developer ToolsNuxtVercel