-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Add service magnet to PSL #1232
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- DNS Validation ok
- Tests ok
- Rationale ok (incl Added magnet.page to the public suffix list #1230 )
- No conflict with base
Approved
Thanks for clearing the debris in the linter stuff by hopping through this extra hoop dave. Appreciate that this is being done also to isolate cookies per user, which will also be a result of the change. May want to monitor and ensure this was an expected outcome. |
Hello @DaveSanders , it seems that the project or organization associated with your domain, which was merged into the Public Suffix List (PSL), may no longer be active based on the observable usage of subdomains. magnet.page
If the service has been decommissioned and the domain is no longer linked to an active project, as outlined in your original request, please confirm whether it can be safely removed from the PSL. This will help prevent leaving unnecessary entries for PSL volunteers and future registrants, as requesters often "set and forget" and neglect to request the removal of their domains from the PSL when their project reaches its end of life (EOL). The PSL is a globally used resource, and it's important to understand that tens of millions, if not hundreds of millions, of devices and users incorporate the list. We aim to keep it as minimal as possible for those who truly need PSL inclusion. Projects that are smaller in scale, such as those without thousands of users or subdomains belonging to thousands of individual entities, will likely be ineligible for inclusion. If you no longer need your entry to remain on the PSL, please create a new pull request to remove it or reply here to confirm. If your project or organization is still active and requires continued inclusion in the PSL, please reply at your earliest convenience. If we do not hear back from you for an extended period, your entry may be subject to removal. Additionally, ensure that the required Thank you. |
Confirmed. This service is no longer in use and the entries can be removed. Thank you! |
@DaveSanders thanks for confirming, opened #2142 |
This replaces #1230 and cleans up the merge change to only be the public_suffix_list.dat file, as requested by @dnsguru
Adding our root domain for our subdomained users for Magnet pages.
Description of Organization
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.
Description of Organization
Service Magnet is a lead generation toolset for the small business service industry. Our customers provide information to us that allows us to generate and maintain landing pages for specific online advertisements so that non-technical users can benefit from online advertising for their businesses.
Each of our customers is assigned a specific subdomain, very much like Squarespace, Heroku, or Carrd does for their customers. We need these subdomains recognized as their own websites.
Organization Website: https://myservicemagnet.com
Note: our website is our marketing information. Our customers pages are hosted at X.magnet.page, which is what this request is for.
Reason for PSL Inclusion
We require PSL inclusion primarily so that Facebook and other advertising platforms recognize the customers websites as different stand-alone sites. Currently because of the TLD+1 rules that Facebook uses, they lump all of our magnet pages under the same domain. We reached out to the Carrd folks and they reported that the way they got around this limitation was by submitting their domain here.
This makes sense because our customer websites should be seen as completely separate and unique, even with the same base domain.
DNS Verification via dig
make test
Yes, I ran make test locally on my fork and from what I could tell everything passed.