jamiefarrelly / popular-site-subdomains Goto Github PK

Hi,
I'd suggest to use a consistent naming scheme. For example domain.tld.txt or so.

Maybe we could even use directories?

$>tree . 
.
├── facebook.com
│   ├── 2015-10-10.txt
│   └── 2016-09-17.txt
└── google.de
    ├── 2013-01-01.txt
    └── 2016-10-01.txt

2 directories, 4 files

That way one could use "git diff" and so on...

www.v6.facebook.com

nslookup www.v6.facebook.com
Server: one.one.one.one
Address: 2606:4700:4700::1111

Non-authoritative answer:
Name: star-mini6.c10r.facebook.com
Address: 2a03:2880:f152:82:face:b00c:0:25de
Aliases: www.v6.facebook.com

there is a problem, what happens if new domains are added?

for example Uber.com list has

Not a massive issue but anyone working with the list will parse and clean/trim first before doing any work.

This could be very useful to people looking to find bugs for bug bounties.

Could have a comment at the start of each list with a link to that site's bug bounty page to confirm they actually do offer bug bounties. This would make the repo not just popular site subdomains, but popular site & bug bounty subdomains.

Anyone else think this could improve the repo?

https://github.com/JamieFarrelly/Popular-Site-Subdomains/blame/87efec80629c965a2c4459ca783c04e40ac18f96/LinkedIn.com.txt#L53

Unlike http://, www. is not a prefix but a subdomain itself. While it often redirects to the root domain or vice versa, they sometimes do point to different hosts. Also many sites use ww2., ww3., etc. - how does this rule affect them?

Which tool did you use to get all these data. Or simply if I may ask, how did you get this much vital information?