This is an endeavor to find porn domains and list them in the shortest possible format it can be done. This means we are not generating any pre-configured output zone files in this project, we are simply only storing, and verifying the availability of the records.
- Porn Records
- Who can use this project
- Combining the Source Matrix
- Classifications Definitions
- Underage material (CSAM)
- DNS zones
- How to Contribute
- Support and comments
- Reporting tool
- File structure explained
- Why contributing
- Test result
- Conclusion
- The most common name for porn domain-name
- Buzz words and keyword
- Contact
We do however serve a full DNS RPZ Firewall zone from adult.mypdns.cloud purely based on the records from this repository.
This said we will maintain a RFC:952 (Hosts files) do to numerous requests, as unfortunately a significant lack of support for DNS RPZ and just in general, the capability to block unwanted adult porno domains with wildcards.
If you, like the rest of the world, who knows just a bit about
DNS and how an OS (Operating System) is handling DNS queries over
the network protocols, you have of curse updated your local network to
use a local DNS resolver that have the full support of the
Response Policy zones, such as the
PowerDNS Recursor or ICS Bind9+,
while unbound only have partial support of DNS RPZ, you will be excluded
from the benefits of the wildcard.rpz-nsdname.
If you are stocked on the very weird and extremely outdated way of
blocking DNS queries with a hosts
file. You'll need to combine all the above files into a flat hosts
file except README.md, rpz-ip and wildcard.rpz-nsdname,
however, this WILL gives you too many records,
as not necessary all domains are served over both www.$domain.tld and
$domain.tld equally, you will however be covered in full.
You can see the full matrix for where your hosts file is located here.
Since Pi-hole are crippled from using wildcard lists for blacklisting through they have support for regex, then this is capped to be used for internal management only. Read more about it in What lists to use in pi-hole by @pallebone
These Adult filters are supported by the AdGuard project just as well as there are for Pi-Hole thanks to the Domains-Only Syntax
This project should be supporting a variety of adblockers such as
uBlock Origin, AdGuard or less effective
software such as adblockplus.org with their "Acceptable Ads", which
means who pays them to be "accepted" - this is not hidden information,
it is just not listed on the frontpage.
The common thing is you can include an external list to those default setups. How this is done depends on the Software you have chosen.
| File | Contents / Purpose | Used by: DNS RPZ |
Used by: Pi-Hole |
Used by: Hosts files |
Used by: AdGuard |
Used by: Ad blockers |
|---|---|---|---|---|---|---|
| Intro: | The difference between files inside submit_here/adult.mypdns.cloud and submit_here/strict.adult.mypdns.cloud is that the strict folder contains domains that otherwise also hosts SFW contents, while records found in the adult.mypdns.cloud is mainly adult domains.The description of the files contents is equal independent of the folder |
|||||
domains.list |
This file is only for domains that can not be blocked with the wildcard.list. This is a list of subdomains, which solely is used for porn hosting, This file is relevant in IE. open blogs domains as *.blogspot.TLD or disqus.com (Adult Only). |
✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
hosts.txt |
This list is unrelated to domains.list and contains only supplementary records required by dumb hosts files, such as lang.$domain.$TLD or cdn.$domain.$TLD as hosts files requires exact match to function rfc:952 and rfc:1123. You should also take a look at this wiki page to read more about the hosts file. |
✖️ | ✔️ | ✔️ | ✔️ | ✔️ |
mobile.txt |
Same as hosts.txt but only mobile specific domains like m.example.net as this is otherwise covered by the wildcard.list. This list is probably as good as dead, tanks to the responsive design nowadays. This list is swallowed by the ordinary hosts or subsidiary the domain.list |
✖️ | ✔️ | ✔️ | ✔️ | ✖️ |
rpz-ip |
To block any #NSFW by there IP addresses, yes, yet another cool DNS RPZ feature, hosts files doesn't have. | ✔️ | ✖️ | ✖️ | ✖️ | ✖️ |
snuff.list |
Snuff Porno (No wildcard this far as the zone is way to small for that) These records will be part of the adult.mypdns.cloud RPZ Firewall zone | ✔️ | ✔️ | ✔️ | ✔️ | ✖️ |
tld.list |
This list contains Top Level Domains like .xxx which with wildcard allow us to make a huge impact on adult specific domain. A very short list, made to avoid FP while testing with @Pyfunceble. |
✔️ | ✖️ | ✖️ | ✖️ | ✔️ |
wildcard.list |
This is the core domains for the rest of the "sub" files for which domains primarily hosting Porno and therefore can be in wildcard formats used by proper DNS recursor's that in full supports DNS RPZ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
white.list |
The locally hosted list for domains that never should be put into any of the above categories or lists | ✔️ | ✖️ | ✖️ | ✖️ | ✖️ |
wildcard.rpz-nsdname |
This file is to blacklist any DNS servers, that is solely used for serving porn. By using a zone like this, we can actually minimize the entire number of entries quit a bit, as ex. all .xxx domains is served from the same root server. Read more about how the rpz-nsdname records on this wiki page |
✔️ | ✖️ | ✖️ | ✖️ | ✔️ |
README.md |
See submit_here/README.md |
The ~"NSFW::Porn" are used for any domains for which the contents is pornographic (NSFW) concept. This means explicit nudity or sexual acts for pornographic entertainment purposes only
This list serve two goals, blocking domains that ordinary might be
considered as SFW but does in fact serves a tremendous amount of porn like
*.bp.blogspot.com, the other purpose is to also include the less NSFW
content which as such should not be classified as NSFW.
What is NOT strict- or porn is a site that is or can be categorized as educational or art
These files will contain domains which primary is used to host non-adult related contents and for that, you might feel like experiencing a number of False Positive's while they in fact are in there right blacklists.
In addition please see the README.md to get the most updated information's about the Strict lists project.
Domains or sites that host any nude or explicit content used for a
educational purpose, like telling about x and/or teaching about y
is to not be classified in this project.
Any requests to block any of that kind of content should probably be redirected to the Matrix project instead.
What should be considered as art is content that could be found at a museum for arts.
News and Articles (-like) content that is an article or reporting an accident, based on facts should have a wider range of acceptant for usage of NSFW content as long it relate to the article(s).
The following is examples of what My Privacy DNS projects will not be blocking access to domains that host contents for which it isn't hard to find in the western public sphere and for which is NOT intended as Adult entertainment; such as girls in bikinis, going to the beach a summer day and there are plenty of topless humans there as well.
This kind of new religious and Amish/Mormons/Muslim perception of acceptable behaviors or endangerments for which should be "parental" blacklisted is falling outside of this project.
If you find any underage material online and you thinking of committing
it to our project, we will be honored and respectfully ask you to mention
this in the very beginning of the issue with a big letter, a single # at
the beginning of the text and please do NOT post any media as proof.
If you choose to report to all resources please do inform them about the issue here at mypdns.org to keep track of the situation.
Second, you should report your found to any of the following projects.
- Red Barnet (safe the children) online service at https://redbarnet.dk/anmelddet/
- Arachnid Project at https://projectarachnid.ca/en/
- Your local (uncorrupted) police authority if there is such thing in your country or region.
If you are so lucky that you have updated your system to use a DNS
resolver rather than abusing your disk-IO with the hosts file, we also
generate a few zone files for Unbound, dnsmasq and regular RPZ supported
resolvers.
Note: If you will read more about why you should switch to a local DNS resolver, please read this wiki
Additionally, there is a source file that will enforce Safe Search in the safer and more privacy-aware duckduckgo.
For unsafe search portals, we have added Bing and Google "safe search
IP's".
However, it has not been tested yet as both are blocked privately for Spywares issues with both domains in question. It can be found here
You can use the following quick links to open the proper domain report.
Please do use our Support board for any non-Blacklist rules questions.
For any rule based comments, edits or contribution, we only support that at https://mypdns.org/my-privacy-dns/porn-records
NOTE: When you first start to commit issues, the Akismet ,our antispam system, is unfortunately very fast to mark you as a spammer, but don't worry as this is happening for everyone even admin accounts.
When this happens, please message this text "Ping @spirillen, I've got mark as spam"
to issue and we will
get your account back on track.
This is where you contribute with new domains matching any of these subfiles.
You can also use our new MyPDNS Reporter, which is both a Browser-based add-on and a CLI (Command LIne Interface), for which you can choose between as you prefer.
submit_here
├── submit_here/adult.mypdns.cloud
│ ├── submit_here/adult.mypdns.cloud/domains.list
│ ├── submit_here/adult.mypdns.cloud/hosts.list
│ ├── submit_here/adult.mypdns.cloud/mobile.list
│ ├── submit_here/adult.mypdns.cloud/rpz-ip
│ ├── submit_here/adult.mypdns.cloud/snuff.list
│ ├── submit_here/adult.mypdns.cloud/tld.list
│ ├── submit_here/adult.mypdns.cloud/white.list
│ ├── submit_here/adult.mypdns.cloud/wildcard.list
│ └── submit_here/adult.mypdns.cloud/wildcard.rpz-nsdname
├── submit_here/README.md
├── submit_here/strict.adult.mypdns.cloud
│ ├── submit_here/strict.adult.mypdns.cloud/README.md
│ ├── submit_here/strict.adult.mypdns.cloud/strict.domains.list
│ ├── submit_here/strict.adult.mypdns.cloud/strict.hosts.list
│ ├── submit_here/strict.adult.mypdns.cloud/strict.rpz-ip
│ ├── submit_here/strict.adult.mypdns.cloud/strict.white.list
│ ├── submit_here/strict.adult.mypdns.cloud/strict.wildcard.list
│ └── submit_here/strict.adult.mypdns.cloud/strict.wildcard.rpz-nsdname
└── submit_here/white.list| File / path | Description - Attended Usage / Covering |
|---|---|
submit_here/adult.mypdns.cloud/: |
|
| domains.list | This file is used to blacklist subdomain, for which can't be covered by using a wildcard methods, because either the main- or other sub-domains do not match a ~"NSFW::Porn" rule |
| hosts.list | This file should only be used as a support to RFC:952 based BlackList in combination with a wildcard blacklisted domain. This list have nothing to do with the domain.list as this is ONLY addition's for hosts driven blacklists |
| mobile.list | This list is considered dying, as the time where responsive webdesigns have taken over the initial days with specific webdesign for mobile devices. There will (probably) not be added further to this lists. |
| rpz-ip | A lists is .in-addr.arpa. reverse styled IP Blacklist to be used for DNS RPZ Response IP Address |
| snuff.list | This list is used for blacklisting both ~"NSFW::Gore" and ~snuff, even thi these are very two different things, the list is just to small, to separate it |
| tld.list | TLD means Top Level Domain like .org is a top level domain, we can with DNS RPZ benefit from the wildcard capability be able to blacklist a few TLD's as they are reserved the adult entertainment industry such as .sex and .adult |
| white.list | 🤔 💭 ☕ Do you need more time to figure this one out? |
| wildcard.list | The wildcard Blacklist, is the list used to blacklist any (second level from the TLD) domains for which the contents is pornographic (NSFW) concept. This means explicit nudity or sexual acts for pornographic entertainment purpose only |
| wildcard.rpz-nsdname | This list contains DNS names of DNS Servers which only is used for hosting Porno domains. |
submit_here/strict.adult.mypdns.cloud/: |
|
| strict.domains.list | See sibling above |
| strict.hosts.list | See sibling above |
| strict.rpz-ip | See sibling above |
| strict.white.list | See sibling above |
| strict.wildcard.list | See sibling above |
| strict.wildcard.rpz-nsdname | See sibling above |
You should contribute to this list because it does matter for those who have to block this kind of content.
Let's compare our work against Cloudflare's https://cloudflare-dns.com/family/
so-called adult filter running on 1.1.1.3
From the test file https://mypdns.org/clefspeare13/pornhosts/-/blob/master/0.0.0.0/hosts which we are going to use for our test we see the following result and why it matters you are contributing.
| Status | Percentage | Numbers |
|---|---|---|
| ACTIVE | 96% | 8615 |
| INACTIVE | 3% | 356 |
| INVALID | 0% | 0 |
We can hereby conclude this project have knowledge to 8615 domains, which CloudFlare-dns do not know about
We have stated to extract the most common used tags within the domainnames and published the list hereL https://www.matrix.rocks/
NoteL the url is target for changing later
Don't forget to clear your browser history when you have bypassed these filter!!!
Adult Only, DNS Filter, DNS Firewall, Family Filter, Family Shield, FamilyShield, hosts file, hosts-file, Kids Safe, NSFW, parental control, Pi-Hole, PiHole, Porn Block, Porn Blocker, Porn Detection, Porn Filter, Porn Records, Pornhost, Pornographic, Pornography, PyFunceble, Safe Kids
Please see contact information