Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

User-controlled subdomains of top domains #254

Open
mosajjal opened this issue Nov 15, 2023 · 3 comments
Open

User-controlled subdomains of top domains #254

mosajjal opened this issue Nov 15, 2023 · 3 comments

Comments

@mosajjal
Copy link

Hi,

the title might be a bit out of context. I'm looking for a list that has all the domains (possibly well-known ones) that offer a user-controlled subdomain content. eg:

workers.dev
r2.dev
herokuapp.com
azurewebsites.net

these domains are very popular in phishing, and having this list will allow the analyst to resort to "newly observed subdomain" through passive dns data and determine if the subdomain is new or not.

Looked around and didn't see anything similar to this. any ideas?

@adulau
Copy link
Member

adulau commented Nov 29, 2023

It's a very good question. It's kind of the dynamic-dns list but more for SaaS and alike. I'm not aware of such list, maybe we could start one in the misp-warning-lists.

@cxcorp
Copy link

cxcorp commented Dec 12, 2024

The Public Suffix List contains all name suffixes under which an internet user can or at some point could register names. Both Chrome and Firefox use this list. It contains both the ICANN top-level domains etc., as well as private domains under which users can register domains, including workers.dev, r2.dev, herokuapp.com, and thousands of more.

https://github.com/publicsuffix/list/blob/54119e116bb0dc5be5b1c0f4218eaa057db17d92/public_suffix_list.dat#L12448-L12449

https://github.com/publicsuffix/list/blob/54119e116bb0dc5be5b1c0f4218eaa057db17d92/public_suffix_list.dat#L13651-L13653

You would just need to filter the file to remove the ICANN names and select only the private domains after // ===BEGIN PRIVATE DOMAINS===

@mosajjal
Copy link
Author

this is awesome. thanks for sharing. I think it's worth it to create a small script to translate this into a warninglist format and update it daily/weekly as well. but looks like the work is (mostly) done!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants