Are you having issues? Provide feedback to Slashdot by selecting the option you are having issues with.
HTTP/2 200 server: nginx date: Wed, 09 Feb 2022 23:02:45 GMT content-type: text/html; charset=utf-8 slash_log_data: shtml cache-control: no-cache pragma: no-cache x-frame-options: SAMEORIGIN content-security-policy: frame-ancestors 'self'; upgrade-insecure-requests x-xrds-location: https://slashdot.org/slashdot.xrds strict-transport-security: max-age=31536000
The DNS is up. We have tried pinging Slashdot.org. There are no DNS Issues detected!
Type | Name | Value | Class | TTL |
A | slashdot.org | 204.68.111.106 | IN | 26 |
NS | slashdot.org | IN | 86400 | |
NS | slashdot.org | IN | 86400 | |
NS | slashdot.org | IN | 86400 | |
NS | slashdot.org | IN | 86400 | |
NS | slashdot.org | IN | 86400 |
We have tried pinging Slashdot.org using our servers and the Slashdot.org server responded on time, indicating that there are no current Slashdot.org problems today.
If Slashdot.org is down for you too, the server might be overloaded or unreachable because of network problems, outages or a website maintenance is in progress.
If Slashdot.org is UP for us but you cannot access it, try these solutions:
en