Add localtonet.com and localto.net

[BurakIsleyicii]

Checklist of required steps

• Description of Organization
• Robust Reason for PSL Inclusion
• DNS verification via dig
• Run Syntax Checker (make test)
• Each domain listed in the PRIVATE section has and shall maintain at least two years remaining on registration, and we shall keep the _psl TXT record in place in the respective zone(s).
• This request was not submitted with the objective of working around other third-party limits.
• The submitter acknowledges that it is their responsibility to maintain the domains within their section. This includes removing names which are no longer used, retaining the _psl DNS entry, and responding to e-mails to the supplied address. Failure to maintain entries may result in removal of individual entries or the entire section.
• The Guidelines were carefully read and understood, and this request conforms to them.
• The submission follows the guidelines on formatting and sorting.

Abuse Contact:

• Abuse contact information (email or web form) is available and easily accessible.

  URL where abuse contact or abuse reporting form can be found:
  https://localtonet.com/abuse

---

• Yes, I understand. I could break my organization's website cookies and cause other issues, and the rollback timing is acceptable. Proceed anyways.

---

Description of Organization

Localtonet is a tool that allows users to make web applications or services running on a local machine or local network (localhost) accessible from the internet. Normally, web servers that can only be accessed locally or within a local network can be shared publicly through tools like Localtonet. This is especially useful for developers or users who want to quickly share their projects or applications for testing or collaboration purposes.

Key Features of Localtonet:
Tunneling: Localtonet creates a secure tunnel to expose a locally running application to the internet with a publicly accessible URL, allowing remote access.

Secure Access: Localtonet provides HTTPS support, ensuring encrypted and secure connections to the tunneled services.

Development and Testing: Developers can easily showcase their projects or test integrations with external APIs using Localtonet, without needing to deploy the application first.

Port Forwarding: It allows forwarding of specific ports from a local machine to be accessible via the internet.

In summary, Localtonet accelerates development and testing processes by making local applications and services available to the internet.

I am Burak ISLEYICI, one of the developers and co-founders of Localtonet, who informed you of this.

Organization Website:
https://localtonet.com

Reason for PSL Inclusion

Security and Privacy Controls
Cookie Management
Accurate URL Handling

Number of users this request is being made to serve:
There are 96232 users registered on the Localtonet platform and it has been serving in the Tunneling sector for approximately 3 years.

DNS Verification

dig +short TXT _psl.localtonet.com
"https://github.com/publicsuffix/list/pull/2233"

dig +short TXT _psl.localto.net
"https://github.com/publicsuffix/list/pull/2233"

Results of Syntax Checker (make test)

TOTAL: 5
PASS: 5
SKIP: 0
XFAIL: 0
FAIL: 0
XPASS: 0
ERROR: 0

[wdhdev]

• You cannot have both wildcard and non-wildcard entries, you have to choose one.
  From what I see in certificate logs, I would recommend removing the wildcards and keeping the non-wildcards.
• localto.net expires 2025-02-10, please make sure this is >2y.
• Are you using simple wildcard SSLs for customers (e.g. *.localto.net) instead of individual SSLs per customer? Because if not, your certificate logs do not check out.

[simon-friedberger]

@wdhdev

• You cannot have both wildcard and non-wildcard entries, you have to choose one.

Why?

[wdhdev]

@simon-friedberger Don't you have to only have one? It might break how some software interprets the PSL, no?

We don't seem to have any existing usage of someone having both as far as I know.

[BurakIsleyicii]

• You cannot have both wildcard and non-wildcard entries, you have to choose one.
  From what I see in certificate logs, I would recommend removing the wildcards and keeping the non-wildcards.
• localto.net expires 2025-02-10, please make sure this is >2y.
• Are you using simple wildcard SSLs for customers (e.g. *.localto.net) instead of individual SSLs per customer? Because if not, your certificate logs do not check out.

I updated the public_suffix_list.dat file as you indicated.
localto.net's certificate is created dynamically as our customers' tunnels are created, so it is not used for the same purpose as the certificate used by localtonet.com

[wdhdev]

@BurakIsleyicii Thank you. Just to confirm you are wanting to "declare" all subdomains at the 3rd level (e.g. blog.example.com) as eTLD+1's, so domains at the 4th level act as root domains (e.g. root.domain.example.com)?

[BurakIsleyicii]

@BurakIsleyicii Thank you. Just to confirm you are wanting to "declare" all subdomains at the 3rd level (e.g. blog.example.com) as eTLD+1's, so domains at the 4th level act as root domains (e.g. root.domain.example.com)?

Our customers create tunnels on the localto.net domain address by creating Random or Custom subdomains, for example example-subdomain.localto.net. SSL is created specifically for each tunnel, or customers install their own SSL.

[wdhdev]

In that case, remove the *. bit before each domain as it will not work as intended otherwise.

[wdhdev]

@BurakIsleyicii For this to be approved, we need the following:

• localto.net to be renewed for >2y.
• Confirmation on whether you want a wildcard or non-wildcard entry (from your use case, I would recommend a non-wildcard)
• I would recommend expanding on your rationale for PSL inclusion as it is quite vague.

[BurakIsleyicii]

@wdhdev
1-) The certificate for localto.net was renewed yesterday.
2-) It will be used as *.localto.net.
3-) We want to participate in PSL to increase the reliability of our domains and service

[wdhdev]

I'm talking about the domain expiry and the entry you are wanting listed on the PSL, not SSL certificates. If you are using a *.localto.net SSL for customer domains, you should update the entry on the PSL to localto.net as it will declare localto.net itself as a public suffix, whereas *.localto.net will declare customer subdomains like example.localcert.net as public suffixes.

[BurakIsleyicii]

I'm talking about the domain expiry and the entry you are wanting listed on the PSL, not SSL certificates. If you are using a *.localto.net SSL for customer domains, you should update the entry on the PSL to localto.net as it will declare localto.net itself as a public suffix, whereas *.localto.net will declare customer subdomains like example.localcert.net as public suffixes.

Updated.

[BurakIsleyicii]

_psl TXT definitions were made again. Can you run validate again?

[wdhdev]

If you pull the latest changes from the main branch into your fork it should re-run the checks.

[BurakIsleyicii]

I did and found that it could not resolve the TXT record. I renewed your TXT record and now I am waiting for you to continue the process.

[wdhdev]

localto.net's domain registration needs to be renewed so it is >2 years.

[BurakIsleyicii]

localto.net's domain registration needs to be renewed so it is >2 years.

Completed. Can you check again please?

[wdhdev]

According to WHOIS it is still showing up as 2025-02-10.

[BurakIsleyicii]

According to WHOIS it is still showing up as 2025-02-10.

It seems to be updated now.

[simon-friedberger]

Did you sort out the wildcard question?

[wdhdev]

@BurakIsleyicii I would recommend removing the wildcard for localtonet.com as well.