When a domain drop-catch is successful and the domain lands at a Newfold Digital registrar—primarily NetworkSolutions.com (and historically related brands like Register.com, Web.com, or SnapNames/NameJet catches that provision there):
- Do NOT update or change the domain’s contact information (especially registrant/owner name, email, or admin contacts).
- Doing so triggers a mandatory 60-day transfer prohibition lock (on top of the standard ICANN 60-day lock for new registrations/post-catch).
- This lock cannot be removed early, even with support escalation. You’ll be stuck unable to transfer out to your preferred registrar (e.g., GoDaddy, Namecheap, Dynadot) for the full period.
Newfold’s policy explicitly states: Changing the domain owner/registrant name or email imposes a 60-day lock for security reasons.
The Persistent Old Contact Data Problem
A common pain point: Even if you’ve previously updated or “purged” old personal info (from 25+ years ago!) across their system, it often reappears on newly caught domains.
Why this happens, possible theories:
- Their legacy databases (Network Solutions is the original .com registrar from the 1990s) retain historical account data tied to your user ID or payment methods.
- When provisioning a drop-catch win, the system pulls from old cached profiles instead of your current/clean one.
- Privacy/WHOIS changes don’t always propagate fully, leading to outdated info resurfacing.
This exposes you to spam, unwanted calls, or privacy risks—exactly what many try to avoid.
Best Practices to Avoid This Trap
- Check the catcher before backordering: Platforms like NameJet/SnapNames (also Newfold-owned) often deliver wins to NetworkSolutions. Prefer services that provision to friendlier registrars (e.g., DropCatch → NameBright, Dynadot drops).
- If it lands at NetworkSolutions:
- Leave contacts untouched until after the initial 60-day ICANN lock.
- Then wait the extra time if needed before transferring.
- Long-term: Consolidate away from Newfold brands where possible—many investors report ongoing headaches with transfers, support, and hidden locks.
This is a widespread frustration in the community, and I hope this warning will help others steer clear of the extra delays and privacy headaches. If you have details or examples from your catches, feel free to share—happy to brainstorm workarounds! 🚀