Issue Station
Sign In
Tools hereToolbox

nextjs - 💡(How to fix) Fix nextjs.dev resolves to Squarespace and redirects to remix.run

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Code Example

N/A — This issue is not related to a specific Next.js project or runtime environment.
It affects the public domain https://nextjs.dev at the DNS/hosting level.
RAW_BUFFERClick to expand / collapse

Link to the code that reproduces this issue

https://nextjs.dev

To Reproduce

Steps to Reproduce

  1. Open a browser
  2. Navigate to https://nextjs.dev
  3. Observe that it redirects to https://remix.run/

Alternative (CLI):

curl -I https://nextjs.dev

Current vs. Expected behavior

Current Behavior

Accessing https://nextjs.dev results in an HTTP 301 redirect to https://remix.run/.

Observed details:

  • Server: Squarespace
  • DNS A record: 198.185.159.144
  • www CNAME: ext-sq.squarespace.com

This indicates the domain is currently served via Squarespace infrastructure and not Vercel.

Expected Behavior

https://nextjs.dev should either:

It should not redirect to an unrelated third-party site.

Provide environment information

N/A — This issue is not related to a specific Next.js project or runtime environment.
It affects the public domain https://nextjs.dev at the DNS/hosting level.

Which area(s) are affected? (Select all that apply)

Not sure, Redirects

Which stage(s) are affected? (Select all that apply)

Vercel (Deployed)

Additional context

Additional Information

  • Reproducible across different networks and environments
  • Not browser-specific
  • Occurs on both desktop and mobile

DNS and HTTP diagnostics indicate:

  • A record resolves to Squarespace IP (198.185.159.144)
  • www CNAME points to ext-sq.squarespace.com
  • HTTP response returns 301 redirect to https://remix.run/
  • Server header: Squarespace

RDAP data shows recent domain changes (February 2026), suggesting a domain or DNS misconfiguration.

extent analysis

TL;DR

The issue can likely be resolved by updating the DNS configuration for the nextjs.dev domain to point to the correct hosting infrastructure, such as Vercel, instead of Squarespace.

Guidance

  • Investigate the recent domain changes (February 2026) and verify the current DNS settings for nextjs.dev to ensure they are correct and up-to-date.
  • Check the Squarespace configuration to see if there is a redirect rule in place that is causing the 301 redirect to https://remix.run/.
  • Consider updating the DNS A record and www CNAME to point to the correct hosting infrastructure, such as Vercel, to resolve the issue.
  • Verify that the Server header is correctly set to the intended hosting platform (e.g., Vercel) instead of Squarespace.

Example

No code snippet is provided as this issue appears to be related to DNS and hosting configuration rather than code.

Notes

The issue seems to be related to a domain or DNS misconfiguration, and resolving it may require updating the DNS settings or configuring the hosting infrastructure correctly. The recent domain changes in February 2026 may be a contributing factor.

Recommendation

Apply workaround: Update the DNS configuration for the nextjs.dev domain to point to the correct hosting infrastructure, such as Vercel, instead of Squarespace. This should resolve the issue by ensuring that the domain is served by the intended hosting platform.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#integration issue#index setup#retrieval issue#search optimization#API routing

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING