Add HiDNS.co and HiDNS.vip #2376
Conversation
Add HiDNS.co and HiDNS.vip
root@google:~/list# make test cd linter; \ ./pslint_selftest.sh; \ ./pslint.py ../public_suffix_list.dat; test_NFKC: OK test_allowedchars: OK test_dots: OK test_duplicate: OK test_exception: OK test_punycode: OK test_section1: OK test_section2: OK test_section3: OK test_section4: OK test_spaces: OK test_wildcard: OK test -d libpsl || git clone --depth=1 https://github.com/rockdaboot/libpsl; \ cd libpsl; \ git pull; \ echo "EXTRA_DIST =" > gtk-doc.make; \ echo "CLEANFILES =" >> gtk-doc.make; \ autoreconf --install --force --symlink; Cloning into 'libpsl'... remote: Enumerating objects: 985, done. remote: Counting objects: 100% (985/985), done. remote: Compressing objects: 100% (511/511), done. remote: Total 985 (delta 111), reused 899 (delta 95), pack-reused 0 (from 0) Receiving objects: 100% (985/985), 4.67 MiB | 16.62 MiB/s, done. Resolving deltas: 100% (111/111), done. Already up to date. autopoint: using AM_GNU_GETTEXT_REQUIRE_VERSION instead of AM_GNU_GETTEXT_VERSION Copying file ABOUT-NLS Creating directory build-aux Copying file build-aux/config.rpath Copying file m4/gettext.m4 Copying file m4/host-cpu-c-abi.m4 Copying file m4/iconv.m4 Copying file m4/intlmacosx.m4 Copying file m4/lib-ld.m4 Copying file m4/lib-link.m4 Copying file m4/lib-prefix.m4 Copying file m4/nls.m4 Copying file m4/po.m4 Copying file m4/progtest.m4 Copying file po/Makefile.in.in Copying file po/Makevars.template Copying file po/Rules-quot Copying file po/boldquot.sed Copying file po/[email protected] Copying file po/[email protected] Copying file po/insert-header.sin Copying file po/quot.sed Copying file po/remove-potcdate.sin libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'. libtoolize: linking file 'build-aux/ltmain.sh' libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'. libtoolize: linking file 'm4/libtool.m4' libtoolize: linking file 'm4/ltoptions.m4' libtoolize: linking file 'm4/ltsugar.m4' libtoolize: linking file 'm4/ltversion.m4' libtoolize: linking file 'm4/lt~obsolete.m4' configure.ac:1: warning: file `version.txt' included several times configure.ac:4: warning: file `version.txt' included several times aclocal.m4:765: AM_INIT_AUTOMAKE is expanded from... configure.ac:4: the top level configure.ac:369: warning: file `version.txt' included several times configure.ac:11: installing 'build-aux/ar-lib' configure.ac:10: installing 'build-aux/compile' configure.ac:13: installing 'build-aux/config.guess' configure.ac:13: installing 'build-aux/config.sub' configure.ac:4: installing 'build-aux/install-sh' configure.ac:4: installing 'build-aux/missing' fuzz/Makefile.am: installing 'build-aux/depcomp' parallel-tests: installing 'build-aux/test-driver' cd libpsl && ./configure -q -C --enable-runtime=libicu --enable-builtin=libicu --with-psl-file=/root/list/public_suffix_list.dat --with-psl-testfile=/root/list/tests/tests.txt && make -s clean && make -s check -j4 configure: WARNING: --enable-builtin=libicu is deprecated, use --enable-builtin (enabled by default) config.status: creating po/POTFILES config.status: creating po/Makefile Making clean in po Making clean in include Making clean in src rm -f ./so_locations Making clean in tools rm -f psl Making clean in fuzz rm -f libpsl_icu_fuzzer libpsl_icu_load_fuzzer libpsl_icu_load_dafsa_fuzzer Making clean in tests rm -f test-is-public test-is-public-all test-is-cookie-domain-acceptable test-is-public-builtin test-registrable-domain Making clean in msvc Making check in po Making check in include Making check in src CC libpsl_la-psl.lo CC libpsl_la-lookup_string_in_fixed_set.lo CCLD libpsl.la Making check in tools CC psl.o CCLD psl Making check in fuzz CC libpsl_fuzzer.o CC main.o CC libpsl_load_fuzzer.o CC libpsl_load_dafsa_fuzzer.o CCLD libpsl_icu_fuzzer CCLD libpsl_icu_load_dafsa_fuzzer CCLD libpsl_icu_load_fuzzer PASS: libpsl_icu_load_dafsa_fuzzer PASS: libpsl_icu_fuzzer PASS: libpsl_icu_load_fuzzer ============================================================================ Testsuite summary for libpsl 0.21.5 ============================================================================ # TOTAL: 3 # PASS: 3 # SKIP: 0 # XFAIL: 0 # FAIL: 0 # XPASS: 0 # ERROR: 0 ============================================================================ Making check in tests CC test-is-public.o CC common.o CC test-is-public-all.o CC test-is-cookie-domain-acceptable.o CC test-is-public-builtin.o CC test-registrable-domain.o CCLD test-is-public CCLD test-is-cookie-domain-acceptable CCLD test-is-public-all CCLD test-is-public-builtin CCLD test-registrable-domain PASS: test-is-public-builtin PASS: test-registrable-domain PASS: test-is-cookie-domain-acceptable PASS: test-is-public PASS: test-is-public-all ============================================================================ Testsuite summary for libpsl 0.21.5 ============================================================================ # TOTAL: 5 # PASS: 5 # SKIP: 0 # XFAIL: 0 # FAIL: 0 # XPASS: 0 # ERROR: 0 ============================================================================ Making check in msvc |
Thanks to William's reply, I’ve learned how to check the certificate issuance status using https://crt.sh/?q=hidns.co and https://crt.sh/?q=hidns.vip. I also noticed that the number of subdomains shown on https://www.virustotal.com/gui/domain/hidns.co/relations and https://www.virustotal.com/gui/domain/hidns.vip/relations is quite limited. Therefore, I’ve uploaded a screenshot of the HiDNS management panel to demonstrate the actual number of users. |
|
We don't have a way to verify said screenshots are legitimate, especially as our tools show very different numbers. A subdomain finder also shows a limited amount of subdomains: https://subdomainfinder.c99.nl/scans/2025-02-03/hidns.co Do you know how many subdomains are actively being used? |
I understand this. HiDNS has been open for registration for just over a month. I will require users to apply for SSL certificates for their registered domains and bind them to their own blogs to meet the third-party verification of user count. Then, I will reapply for inclusion in the PSL to address the cookie isolation issue. William, could you please review this application again? Besides the concern about the number of users, are there any other issues? I’d like to fully address all the unmet requirements so that the next application can be approved in one go. Thank you! |
|
All looks good to me, it's just the user count. |
I've noticed that some users have set A records pointing to 127.0.0.1 or 192.168.0.1. Others have configured MX records, and many have changed their NS records to point to third-party name servers. This makes it difficult for me to determine whether a domain is active. It wasn't until today that you told me I could use crt.sh to check for issued SSL certificates. |
Thank you. I’m new to managing public suffixes, and I’ll reach out to everyone for advice if I have any questions in the future. |
Public Suffix List (PSL) Submission
Checklist of required steps
Description of Organization
Robust Reason for PSL Inclusion
DNS verification via dig
Each domain listed in the PRIVATE section has and shall maintain at least two years remaining on registration, and we shall keep the
_pslTXT record in place in the respective zone(s).Submitter affirms the following:
Abuse Contact:
Abuse contact information ([email protected]) is available and easily accessible.
URL where abuse contact or abuse reporting form can be found:
https://www.hidoha.net
For PRIVATE section requests that are submitting entries for domains that match their organization website's primary domain, please understand that this can have impacts that may not match the desired outcome and take a long time to rollback, if at all.
To ensure that requested changes are entirely intentional, make sure that you read the affectation and propagation expectations, that you understand them, and confirm this understanding.
PR Rollbacks have lower priority, and the volunteers are unable to control when or if browsers or other parties using the PSL will refresh or update.
(Link: about propagation/expectations)
Description of Organization
HiDNS is a free third-level domain registration platform created by the "Programmers' Technical Exchange Community." Anyone can register and use domains with the hidns.co or hidns.vip suffix for free.
The "Programmers' Technical Exchange Community" is a long-standing Telegram group (https://t.me/HiaiFeng) with over 3,000 members and 6 administrators. Most members work in computer-related fields, sharing and learning knowledge about technology. We use bots to remove advertisements or illegal content, with administrators handling any violations the bots might miss. The community operates smoothly with an active and engaging atmosphere.
HiDNS is jointly maintained by the administrators of the "Programmers' Technical Exchange Community" to ensure stable service and prevent the misuse of public suffixes.
The reason behind creating the HiDNS free third-level domain registration platform is quite simple. As a programmer, I often find myself with perfectionist tendencies. I always prefer using "ifeng" when registering accounts or emails. I even regret not securing the "[email protected]" address. Although many free third-level domain services are available online, popular domains are often already taken, leaving users unable to claim their preferred short domains. This inspired the creation of HiDNS to provide more options for everyone.
By default, hidns.co and hidns.vip domains have DNSSEC enabled to enhance DNS security. If users choose to host their HiDNS subdomains with other DNS providers, they can still configure DS records through the HiDNS management panel.
Since its launch, HiDNS has attracted thousands of users who find the service ideal for personal use, early-stage project development, and testing. HiDNS domains can be used for any legal purpose, such as creating websites, setting up DDNS, establishing VPN services, enabling remote access, and connecting home IoT devices.
While HiDNS has an open registration policy and does not conduct pre-approval content reviews, we actively work to prevent domain abuse. Recently, after comprehensive data analysis, we suspended several accounts and their associated domains due to abuse. Additionally, we use third-party libraries to block registrations with temporary or disposable email addresses and monitor security platforms (e.g., otx.alienvault.com and virustotal.com) for subdomain activity. Any detected abuse is promptly addressed.
I am ifeng, the technical lead at HiDNS, responsible for the maintenance and improvement of domain names.
Organization Website:
https://www.hidoha.net
Abuse Contact:
[email protected]
Reason for PSL Inclusion
Our domain service is designed to allow registrations based on subdomains, meaning each website on a subdomain operates independently. For security reasons, we need to restrict cookies to their respective subdomains and ensure data isolation between subdomains to prevent potential security risks.
The domain hidns.co and hidns.vip has more than two years before expiration.
Number of users this request is being made to serve:
After suspending multiple accounts and their associated domains due to abusive behavior, we currently have 1,254 active registered users and 2,231 active domain registrations, including 1,203 under hidns.co and 1,028 under hidns.vip.
DNS Verification