JS.ORG CLEANUP

[js-org-cleanup]

JS.ORG CLEANUP

The following js.org subdomains have been detected to no longer be working.

If you are the 'owner' of any of these subdomains and wish to still use them, please leave a comment below in the following format:

I am responsible for `xxx.js.org`.
It now has [reasonable content](https://github.com/js-org/js.org/wiki/No-Content) and is now working.

Subdomains that aren't accounted for after a month and are still down will be removed.

---

Note to maintainers:

• Once contact has been made with the 'owner' of a subdomain, please move it to the contact made list.
• Only once a domain has been validated by comment here from the 'owner' (see above) may the checkbox be ticked.
• This file will be automatically parsed by a script at the end of the period, so please follow these instructions.

---

Domains with the checkbox ticked are now working and will not be removed at the end of the cleanup period.

Pending Contact

All domains in this list have not been contacted by the maintainers of js.org yet regarding the domain status.

• -
• bad-automatic-fail.js.org > js-org-cleanup.github.io/simulated-automatic-fail
  HTTP: Failed during request with error 'FetchError: request to http://bad-automatic-fail.js.org/ failed, reason: getaddrinfo ENOTFOUND bad-automatic-fail.js.org bad-automatic-fail.js.org:80'
  HTTPS: Failed during request with error 'FetchError: request to https://bad-automatic-fail.js.org/ failed, reason: getaddrinfo ENOTFOUND bad-automatic-fail.js.org bad-automatic-fail.js.org:443'
• bad-external-target.js.org > custom-target.test.com
  HTTP: Failed during request with error 'FetchError: request to http://bad-external-target.js.org/ failed, reason: getaddrinfo ENOTFOUND bad-external-target.js.org bad-external-target.js.org:80'
  HTTPS: Failed during request with error 'FetchError: request to https://bad-external-target.js.org/ failed, reason: getaddrinfo ENOTFOUND bad-external-target.js.org bad-external-target.js.org:443'
• bad-non-existent-repo.js.org > js-org-cleanup.github.io
  HTTP: Failed during request with error 'FetchError: request to http://bad-non-existent-repo.js.org/ failed, reason: getaddrinfo ENOTFOUND bad-non-existent-repo.js.org bad-non-existent-repo.js.org:80'
  HTTPS: Failed during request with error 'FetchError: request to https://bad-non-existent-repo.js.org/ failed, reason: getaddrinfo ENOTFOUND bad-non-existent-repo.js.org bad-non-existent-repo.js.org:443'

Contact Made

All domains in this list have had contact made (issue raised on relevant repository etc.) by the js.org maintainers or the cleanup robot.

• -
• bad-automatic-contact.js.org > js-org-cleanup.github.io/simulated-automatic-contact
  Issue: JS.ORG CLEANUP simulated-automatic-contact#12
  HTTP: Failed during request with error 'FetchError: request to http://bad-automatic-contact.js.org/ failed, reason: getaddrinfo ENOTFOUND bad-automatic-contact.js.org bad-automatic-contact.js.org:80'
  HTTPS: Failed during request with error 'FetchError: request to https://bad-automatic-contact.js.org/ failed, reason: getaddrinfo ENOTFOUND bad-automatic-contact.js.org bad-automatic-contact.js.org:443'

---

'Owners' of subdomains that are identifiable through the GitHub pages site that the subdomain points to will be contacted via their repository where possible (repository public & issues enabled)
They will receive the following message asking them to reply to this issue to keep their domain:

# JS.ORG CLEANUP

Hello, it seems a `js.org` subdomain that was requested to target this repository no longer works.
The subdomain requested was `xxx.js.org` and had the target of `xxx`.
It produced the following failures when tested as part of the cleanup:
 - [HTTP](http://xxx.js.org): `xxx`
 - [HTTPS](https://xxx.js.org): `xxx`

To keep the `js.org` subdomain you should add a page with [reasonable content](https://github.com/js-org/js.org/wiki/No-Content) within a month so the subdomain passes the validation.
Failure to rectify the issues will result in the requested subdomain being removed from JS.ORGs DNS and the list of active subdomains.

**If you are wanting to keep the `js.org` subdomain and have added [reasonable content](https://github.com/js-org/js.org/wiki/No-Content), YOU MUST reply to the [main cleanup issue](https://github.com/js-org-cleanup/simulated-js.org/issues/46) with the response format detailed at the top to keep the requested subdomain.**

[MattIPv4]

I am responsible for bad-automatic-contact.js.org.
It now has reasonable content and is now working.