Built a secondary domain registration system using react+nodejs vibe

https://registry.kevsrv.me/

暂时还没发布源码 可以先收藏一下网址 完成PRIORITIZED TASKS就开源 bro要发就发功能完全的 :xhj22:
目前还在测试一些edge cases之类的 可能还需要一些时间
用英文写的然后翻译中文 可能有点奇怪看起来 部分提示还没翻译完全


支持pdns了

To-dos

PRIORITIZED TASKS

  • Domain activeness status on domain details page for user - remind user to start using or loosing
  • Need to fix sensitive/active/security check scripts - scan all SSL sub-subdomains for sensitive content scanning, implement google safe browsing API to check if any sub-domain ans sub-subdomains from SSL cert monitor are tagged dangerous.
  • Some type of restriction on multiple accounts per person, (kyc not feasible. mobile - require PAID API + had to cover all country codes: not feasible, US numbers w/ can achieve e-mail to sms but limited and unreliable. email verification: def dupe emails per person. pay a dime to activate account - maybe or credit card verification like oracle cloud - pay nothing, be strict on temp cc issuers or supermarket prepaid cards. DupeIP - already implemented but users may use same proxy causing 20 dupe ips per account: need manual verification).
  • VirusTotal scan complete - still need to verify if API calls (approx. 1 req per domain) would not trigger VT’s free rate limit. OR find a better way to reduce API calls while covering all sub-domains
  • If domain suspended, do not allow user to delete the domain: frontend disable delete + backend check stats
  • E-mail domain whitelist/blacklist
  • NEED TO THOROUGHLY TEST OAUTH - require restart backend if oauth added/deleted

NOT UNTIL NEXT UPDATE

  • Implement choice to enable domain expiry date and a way to extend
  • Edit ns records
  • PUSH domains to other user, admin enable/disable
  • User individual domain limit setting (use GLOBAL_LIMIT±# in db field and do calculation while registering or req individual limits)
  • DNSSEC
  • User individual domain count
  • Payment system integration Paypal, Crypto, Alipay, Wechat pay(ability to purchase premium [specified or regex] sub-domains)
  • System setup script
  • NS server verifier
  • Invitation system: still considering…
  • Whois lookup + if privacy, can provide a form to contact: ext feat: message inbox in dashboard

COMPLETED

  • fix a lot of captchas
  • CANNOT EXIST 2 SAME NS SERVERS
  • Able to change minimum length of subdomains
  • Add email verification for registering, could use approach to send none mysqled hashed link to verify email or use recaptcha
  • Email API: mailjet for now
  • 2FA
  • Extend SSO providers to not just google
  • Add admin domain filter for status
  • Add tos and privacy
  • Remove or link unused buttons and shit
  • Account status: no registering if account disabled: disable account domains
  • Extend to more dns providers + local dns authoritative server
  • fix mobile compatibility
  • try reduce calls to api
  • language switch on hcaptcha
  • only load setting once when site loads
  • Add register domain modal in domain details page

AI TRANSLATED NO ACCURACY GUARANTEED

待办事项(To-dos)

优先任务(PRIORITIZED TASKS)

  • 在域名详情页显示域名活跃状态 – 提醒用户开始使用,否则可能被回收
  • 修复敏感/活跃/安全检查脚本 – 扫描所有 SSL 子子域名的敏感内容;整合 Google Safe Browsing API 检查 SSL 证书监控中所有子域名是否被标记为危险
  • 限制每人多个账户的问题(KYC 不可行;手机验证需付费 API 且需覆盖全球号码,不可行;美国号码可用 email-to-SMS 但不稳定;邮箱验证会导致一人多个邮箱;付费激活账户或信用卡验证可能可行,但需屏蔽临时卡与超市预付卡;重复 IP 已实现但代理共享会造成几十个重复 IP,需要人工审核)
  • VirusTotal 全量扫描已完成 – 仍需确认 API 调用(约每域名 1 调用)不会触发 VT 免费额度限制;或设计更好的方案在覆盖所有子域的同时减少 API 请求
  • 如果域名被封禁,不允许用户删除域名:前端禁用删除按钮 + 后端强制检查状态
  • 邮箱域名白名单 / 黑名单
  • 必须彻底测试 OAuth – 添加或删除 OAuth 配置后需重启后端

下次更新前不处理(NOT UNTIL NEXT UPDATE)

  • 实现域名过期时间与续期功能
  • 可编辑 NS 记录
  • 允许管理员将域名转移给其他用户
  • 用户单独域名数量限制(数据库字段存 GLOBAL_LIMIT±#,注册时计算)
  • DNSSEC
  • 用户域名数量统计
  • 支付系统整合:PayPal、Crypto、支付宝、微信支付(允许购买指定或正则匹配的高级子域)
  • 系统一键部署脚本
  • NS 服务器验证器
  • 邀请系统:仍在考虑中…
  • Whois 查询 + 若隐私保护开启,可提供联系表单(扩展功能:仪表盘消息收件箱)

已完成(COMPLETED)

  • 修复大量验证码问题
  • 不允许存在两个相同的 NS 服务器
  • 可修改最小子域名长度
  • 注册新增邮箱验证,可用 MySQL 外链式哈希验证或 Recaptcha
  • 邮件 API:Mailjet
  • 2FA
  • 增加更多 SSO 登录提供方,不局限于 Google
  • 管理员可根据状态过滤域名
  • 添加 ToS 与隐私政策
  • 移除未使用的按钮
  • 账号状态:禁用账号后不可注册;禁用账号域名
  • 扩展到更多 DNS 提供商 + 本地权威 DNS 服务器
  • 修复移动端兼容性
  • 尝试减少 API 调用
  • hCaptcha 支持语言切换
  • 设置仅在站点加载时读取一次
  • 在域名详情页新增“注册域名”弹出框

做个小survey 会用email+密码功能的人多吗 我在想第一个版本要不要加验证邮箱功能

  • 我只用SSO(google github)/OAUTH2 (关闭email密码登陆功能)
  • 我会用email+密码
0 投票人
  • 我需要域名注册期限+账户余额(兑换码)功能
  • 我不需要域名注册期限+账户余额(兑换码)功能
0 投票人
17 Likes

Not bad, looking forward to open source.

1 Like

awesome

4 Likes

When will the master open source it?

3 Likes

I’ll open source it once I finish the todo.

3 Likes

Write a proper review. I used the code written by Sixqu (六趣大神), but it cannot prevent packet sniffing from writing data. This is very important. There are always some programmers who, in order to showcase their superb skills, write garbage for you and insert it into the database.

1 Like

My front-end and back-end matching are the same, and the back-end has an even stricter matching.
All API endpoints are separated: some can be accessed by users, some by admin. There should be no problem you mentioned.

1 Like

Great, does your support for self‑built DNS use bind9 or powerDNS? I hope to integrate it with the Hestia system; this system’s DNS uses a DNS server built with bind9.

2 Likes

I’ll look into it then.

1 Like

Looking forward to open source.

1 Like

This is good looking forward to the finished product

1 Like

The effect is quite good! Looking forward to open source. Looking forward to integrating NL OAUTH.

2 Likes

Does NL’s OAUTH provide an email parameter?

1 Like

I might prioritize supporting PowerDNS because it seems that BIND9 stores data locally and doesn’t support databases.

2 Likes

some

1 Like

The newer version of bind9 no longer supports MySQL.

It really looks great, looking forward to it being open‑source.

Must support :xhj41:

Not bad, looking forward to the expert’s project being fully refined and open-sourced soon.

You’re awesome, looking forward to the open source.