Is coj.net down or not working?

What happened to coj.net, why did the website go down and not work? Here you can see who else is having the same problem with coj.net, as well as possible solutions. According to our statistics, the following most often do not work: Website, Login, Account, Mobile App.

Current status: No failures

At the moment, according to our data, coj.net is working fine, but single failures are possible. If coj.net does not work for you, then report your problem and write a comment.
Add comment

What to do if the site coj.net is not available? Try our guide.

coj.net outage reports in the last 24 hours

coj.net - error and failure reports, troubleshooting methods

Leave your comment describing the failure and share with other users how to solve the problem.
  • No registration required.
  • Messages with obscene language and insults, as well as breaking the law, are not allowed to be published.
  • Active links in the text of the message are not published, but displayed in plain text.
  • It is forbidden to post your own and other people's personal data: addresses, phone numbers, emails, accounts in instant messengers, etc.

Technical information

Main page title:
Access Denied
Protocol:
https
Status code:
403
Page size:
0.4 KB
Response time:
0.796sec.
IP:
205.173.38.124
Response headers:
mime-version: 1.0
content-type: text/html
content-length: 372
expires: Tue, 01 Oct 2024 04:47:50 GMT
cache-control: max-age=0, no-cache, no-store
pragma: no-cache
date: Tue, 01 Oct 2024 04:47:50 GMT
connection: close
server-timing: cdn-cache; desc=HIT, edge; dur=1, ak_p; desc="1727758070247_1490884711_156195705_28_8599_4_35_-";dur=1
akamai-grn: 0.6718dd58.1727758070.94f5b79
DNS records:
A address205.173.38.124
ttl300
MX exchangecoj-net.mail.protection.outlook.com
priority10
NS valuedns2.coj.net
NS valuedns1.coj.net
TXT entriesv=spf1 mx mx:pd4.coj.net mx:amazonses.com ip4:192.254.121.248 ip4:205.173.38.59 include:spf.protection.outlook.com include:_phishspf.knowbe4.com include:mailgun.org include:mail.zendesk.com exists:%{i}._spf.sparkpostmail.com ~all
TXT entriesgoogle-site-verification=vmFPsCfbdBXKJ4CCVkvu79oUA1iDT2D_TVvmpmGCQX0
TXT entriesogle-site-verification=1o792P0-B6_79nZew7SKeNjJ4gtIQua5-06pTqPcJVE
TXT entries8kctq466hbrnppycfrbhny3mrq4drlr6
TXT entriesdocusign=6c08c46e-c358-4796-a216-29ce9187826a
TXT entrieskLmCVz0dXzlV4nLE6Wqzdn6kZCBX3fmBHD8xh+H7c3eqpvpz8YPgpDulLtmxIoOYdrI+pvkz4kmZIdlTPabh+A==
TXT entries0dlk8412kgrfnrd1nsmmk33jggw5p4mq
TXT entriesdocusign=82f8bf8d-9a53-4a31-98dc-cf8a9dd2abb3
TXT entriesdropbox-domain-verification=4g5uhxa59ixk
TXT entriesJOoY75KUc4sOs13YQjHv8i5d9p5bqT6o1TTlDydMd49kgmoCyoacQKCEg9flqIy+RNxcLaI3WQBM2PTJCGsWRg==
SOA nsnamedns1.coj.net
hostmasterpostmaster.coj.net
serial2535746183
refresh900
retry600
expire1209600
minttl86400

SEO headers

h1 Access Denied

How to solve problems with coj.net

Errors on the coj.net website can be either on the server side or on your side (client side). If there is practically nothing to be done about errors on the server side (it remains only to wait for the site to work again), then with errors on the client side it is possible to solve the problem with the availability of coj.net on your own.