js-org-cleanup / simulated-js.org Goto Github PK

View Code? Open in Web Editor NEW

0.0 0.0 0.0 29 KB

JavaScript 100.00%

simulated-js.org's People

Contributors

Watchers

simulated-js.org's Issues

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.

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.

-
test.js.org > js-org-cleanup.github.io/test-repo-2
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'
custom.js.org > custom-target.test.com
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'

Contact Made

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

'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: `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/test-repo-1/issues/20) with the response format detailed at the top to keep the requested subdomain.**

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.

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.

-
test-other.js.org > js-org-cleanup.github.io/test-repo-3
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'
test-gone.js.org > js-org-cleanup.github.io
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'
custom.js.org > custom-target.test.com
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'

Contact Made

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

-
test.js.org > js-org-cleanup.github.io/test-repo-2
Issue: js-org-cleanup/simulated-automatic-contact#2
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'

'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/test-repo-1/issues/27) with the response format detailed at the top to keep the requested subdomain.**

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.

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.**

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.

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.

-
test.js.org > js-org-cleanup.github.io/test-repo-2
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'
custom.js.org > custom-target.test.com
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'

Contact Made

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

# 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: `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/test-repo-1/issues/17) with the response format detailed at the top to keep the requested subdomain.**

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.

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.

-
76.js.org > hustcc.github.io/76
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'

Contact Made

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

# 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: `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/test-repo-1/issues/3) with the response format detailed at the top to keep the requested subdomain.**

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.

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'
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-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'
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-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'
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'

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#13
HTTP: Failed during request with error 'FetchError: request to http://bad-automatic-contact.js.org/ failed, reason: getaddrinfo ENOTFOUND bad-automatic-contact.js.org'
HTTPS: Failed during request with error 'FetchError: request to https://bad-automatic-contact.js.org/ failed, reason: getaddrinfo ENOTFOUND bad-automatic-contact.js.org'

'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/49) with the response format detailed at the top to keep the requested subdomain.**

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.

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.

-
76.js.org > hustcc.github.io/76
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'

Contact Made

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

# 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: `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/test-repo-1/issues/6) with the response format detailed at the top to keep the requested subdomain.**

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.

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.

-
76.js.org > hustcc.github.io/76
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'

Contact Made

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

# 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: `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/test-repo-1/issues/14) with the response format detailed at the top to keep the requested subdomain.**

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.

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#10
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/42) with the response format detailed at the top to keep the requested subdomain.**

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.

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.

-
test.js.org > js-org-cleanup.github.io/test-repo-2
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'
test-other.js.org > js-org-cleanup.github.io/test-repo-3
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'
test-gone.js.org > js-org-cleanup.github.io
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'
custom.js.org > custom-target.test.com
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'

Contact Made

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

# 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: `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/test-repo-1/issues/23) with the response format detailed at the top to keep the requested subdomain.**

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.

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.

-
test-other.js.org > js-org-cleanup.github.io/test-repo-3
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'
test-gone.js.org > js-org-cleanup.github.io
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'
custom.js.org > custom-target.test.com
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'

Contact Made

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

-
test.js.org > js-org-cleanup.github.io/test-repo-2
Issue: js-org-cleanup/simulated-automatic-contact#2
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'

'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/test-repo-1/issues/29) with the response format detailed at the top to keep the requested subdomain.**

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.

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.

-
test-other.js.org > js-org-cleanup.github.io/test-repo-3
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'
test-gone.js.org > js-org-cleanup.github.io
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'
custom.js.org > custom-target.test.com
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'

Contact Made

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

-
test.js.org > js-org-cleanup.github.io/test-repo-2
Issue: js-org-cleanup/simulated-automatic-contact#4
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'

'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/test-repo-1/issues/31) with the response format detailed at the top to keep the requested subdomain.**

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.

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.

-
test.js.org > js-org-cleanup.github.io/test-repo-2
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'
custom.js.org > custom-target.test.com
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'

Contact Made

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

# 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: `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/test-repo-1/issues/16) with the response format detailed at the top to keep the requested subdomain.**

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.

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.

-
test.js.org > js-org-cleanup.github.io/test-repo-2
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'
custom.js.org > custom-target.test.com
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'

Contact Made

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

# 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: `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/test-repo-1/issues/19) with the response format detailed at the top to keep the requested subdomain.**

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.

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.

-
test-other.js.org > js-org-cleanup.github.io/test-repo-3
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'
test-gone.js.org > js-org-cleanup.github.io
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'
custom.js.org > custom-target.test.com
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'

Contact Made

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

-
test.js.org > js-org-cleanup.github.io/test-repo-2
Issue: js-org-cleanup/simulated-automatic-contact#1
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'

'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/test-repo-1/issues/26) with the response format detailed at the top to keep the requested subdomain.**

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.

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#11
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/44) with the response format detailed at the top to keep the requested subdomain.**

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.

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.

-
76.js.org > hustcc.github.io/76
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'

Contact Made

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

# 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: `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/test-repo-1/issues/7) with the response format detailed at the top to keep the requested subdomain.**

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.

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.

-
test-other.js.org > js-org-cleanup.github.io/test-repo-3
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'
test-gone.js.org > js-org-cleanup.github.io
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'
custom.js.org > custom-target.test.com
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'

Contact Made

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

-
test.js.org > js-org-cleanup.github.io/test-repo-2
Issue: js-org-cleanup/simulated-automatic-contact#5
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'

'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/test-repo-1/issues/33) with the response format detailed at the top to keep the requested subdomain.**

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.

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.

-
test-other.js.org > js-org-cleanup.github.io/test-repo-3
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'
test-gone.js.org > js-org-cleanup.github.io
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'
custom.js.org > custom-target.test.com
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'

Contact Made

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

-
test.js.org > js-org-cleanup.github.io/test-repo-2
Issue: js-org-cleanup/simulated-automatic-contact#2
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'

'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/test-repo-1/issues/28) with the response format detailed at the top to keep the requested subdomain.**

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.

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.

-
76.js.org > hustcc.github.io/76
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'

Contact Made

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

# 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: `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/test-repo-1/issues/4) with the response format detailed at the top to keep the requested subdomain.**

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.

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/test-repo-3
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/test-repo-2
Issue: js-org-cleanup/simulated-automatic-contact#9
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/test-repo-1/issues/40) with the response format detailed at the top to keep the requested subdomain.**

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.

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.

-
76.js.org > hustcc.github.io/76
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'

Contact Made

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

# 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: `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/test-repo-1/issues/9) with the response format detailed at the top to keep the requested subdomain.**

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.

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.

-
test.js.org > js-org-cleanup.github.io/test-repo-2
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'
custom.js.org > custom-target.test.com
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'

Contact Made

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

# 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: `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/test-repo-1/issues/18) with the response format detailed at the top to keep the requested subdomain.**

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.

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.

-
76.js.org > hustcc.github.io/76
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'

Contact Made

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

# 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: `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/test-repo-1/issues/12) with the response format detailed at the top to keep the requested subdomain.**

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.

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/test-repo-3
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/test-repo-2
Issue: js-org-cleanup/simulated-automatic-contact#6
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/test-repo-1/issues/35) with the response format detailed at the top to keep the requested subdomain.**

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.

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.

-
76.js.org > hustcc.github.io/76
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'

Contact Made

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

# 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: `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/test-repo-1/issues/11) with the response format detailed at the top to keep the requested subdomain.**

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.

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/test-repo-3
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/test-repo-2
Issue: js-org-cleanup/simulated-automatic-contact#8
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/test-repo-1/issues/39) with the response format detailed at the top to keep the requested subdomain.**

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.

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.

-
test-other.js.org > js-org-cleanup.github.io/test-repo-3
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'
test-gone.js.org > js-org-cleanup.github.io
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'
custom.js.org > custom-target.test.com
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'

Contact Made

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

-
test.js.org > js-org-cleanup.github.io/test-repo-2
Issue: js-org-cleanup/simulated-automatic-contact#3
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'

'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/test-repo-1/issues/30) with the response format detailed at the top to keep the requested subdomain.**

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.

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/test-repo-3
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/test-repo-2
Issue: js-org-cleanup/simulated-automatic-contact#7
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/test-repo-1/issues/38) with the response format detailed at the top to keep the requested subdomain.**

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.

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.

-
test.js.org > js-org-cleanup.github.io/test-repo-2
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'

Contact Made

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

# 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: `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/test-repo-1/issues/15) with the response format detailed at the top to keep the requested subdomain.**

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.

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.

-
76.js.org > hustcc.github.io/76
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'

Contact Made

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

# 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: `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/test-repo-1/issues/8) with the response format detailed at the top to keep the requested subdomain.**

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.

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.

-
test.js.org > js-org-cleanup.github.io/test-repo-2
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'
test-other.js.org > js-org-cleanup.github.io/test-repo-3
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'
test-gone.js.org > js-org-cleanup.github.io
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'
custom.js.org > custom-target.test.com
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'

Contact Made

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

# 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/test-repo-1/issues/24) with the response format detailed at the top to keep the requested subdomain.**

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.

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.

-
test.js.org > js-org-cleanup.github.io/test-repo-2
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'
custom.js.org > custom-target.test.com
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'

Contact Made

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

# 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: `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/test-repo-1/issues/22) with the response format detailed at the top to keep the requested subdomain.**

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.

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.

-
76.js.org > hustcc.github.io/76
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'

Contact Made

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

# 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: `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/test-repo-1/issues/5) with the response format detailed at the top to keep the requested subdomain.**

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.

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.

-
test-other.js.org > js-org-cleanup.github.io/test-repo-3
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'
test-gone.js.org > js-org-cleanup.github.io
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'
custom.js.org > custom-target.test.com
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'

Contact Made

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

-
test.js.org > js-org-cleanup.github.io/test-repo-2
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'

# 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/test-repo-1/issues/25) with the response format detailed at the top to keep the requested subdomain.**

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.

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.

-
test.js.org > js-org-cleanup.github.io/test-repo-2
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'
custom.js.org > custom-target.test.com
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'

Contact Made

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

# 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: `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/test-repo-1/issues/21) with the response format detailed at the top to keep the requested subdomain.**

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.

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.

-
76.js.org > hustcc.github.io/76
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'

Contact Made

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

# 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: `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](xxx) with the response format detailed at the top to keep the requested subdomain.**

JS.ORG CLEANUP

Automatic initial cleanup contact in progress... this issue will be updated shortly.

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.

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.

-
76.js.org > hustcc.github.io/76
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'

Contact Made

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

# 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: `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/test-repo-1/issues/13) with the response format detailed at the top to keep the requested subdomain.**

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.

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.

-
76.js.org > hustcc.github.io/76
HTTP: Failed with status code '404 Not Found'
HTTPS: Failed with status code '404 Not Found'

Contact Made

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

# 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: `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/test-repo-1/issues/10) with the response format detailed at the top to keep the requested subdomain.**