Is dailymercury.com.au down or not working?

What happened to dailymercury.com.au, why did the website go down and not work? Here you can see who else is having the same problem with dailymercury.com.au, 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, dailymercury.com.au is working fine, but single failures are possible. If dailymercury.com.au does not work for you, then report your problem and write a comment.
Add comment

What to do if the site dailymercury.com.au is not available? Try our guide.

dailymercury.com.au outage reports in the last 24 hours

dailymercury.com.au - 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

Protocol:
https
Status code:
403
Page size:
1.3 KB
Response time:
0.679sec.
IP:
165.69.249.4
Response headers:
server: AkamaiGHost
mime-version: 1.0
content-length: 1300
cache-control: no-cache, no-store, must-revalidate, max-age=0
pragma: no-cache
expires: 0
content-type: text/html
date: Sat, 05 Oct 2024 07:10:12 GMT
connection: close
set-cookie: n_regis=123456789; path=/; domain=.couriermail.com.au
strict-transport-security: max-age=31536000 ; includeSubDomains
content-security-policy-report-only: frame-ancestors 'self'; report-uri https://www.couriermail.com.au/csp-reports
content-security-policy: block-all-mixed-content; style-src https: 'unsafe-inline'; script-src https: blob: 'unsafe-inline' 'unsafe-eval'; img-src https: data:; frame-src https:;
x-arrrg5: /blaize/decision-engine?path=https%3a%2f%2fwww.couriermail.com.au%2fnews%2fqueensland%2fmackay%2f&blaizehost=v4-news-au-couriermail.cdn.zephr.com&content_id=
x-arrrg4: http://dailymercury.com.au/
x-pathqs: TRUE
vary: User-Agent
akamai-grn: 0.3d19dd58.1728112212.145e2d8c
DNS records:
A address165.69.249.4
ttl60
MX exchangemxb-00596a01.gslb.pphosted.com
priority10
MX exchangemxa-00596a01.gslb.pphosted.com
priority10
NS valuens-1487.awsdns-57.org
NS valuens-240.awsdns-30.com
NS valuens-1539.awsdns-00.co.uk
NS valuens-811.awsdns-37.net
TXT entriesgoogle-site-verification=Xv5Gp0uQpnH53PecMSuHSXTyFzB8yxcbKYeoyj8hbQk
TXT entriesfacebook-domain-verification=tn1fpitxts7m91s5e27kw0ajjdj3ud
TXT entries0ed1fe018ab5529242933d42228eea89
TXT entries0ed1fe018a2adaedac66a44cd89f31378ef8a13ff4
TXT entriesgoogle-site-verification=EFwDF0eLfaLNmzSaF1Vzlu0kB_XutfyQxWcn9YLI7rQ
TXT entriesgoogle-site-verification=mUpNGf1fun1vGYoiYPtTT7UN7T0Gd-dsCko6dA9eO5Y
TXT entriesgoogle-site-verification=4PpHcl3O0BZcMMXLgmw-wFS-M98btyjooJA3UsLUokk
TXT entriesv=spf1 include:_spf.google.com include:spf.mandrillapp.com include:servers.mcsv.net include:spf-00596a01.pphosted.com ~all
SOA nsnamens-1539.awsdns-00.co.uk
hostmasterawsdns-hostmaster.amazon.com
serial1
refresh7200
retry900
expire1209600
minttl86400

SEO headers

h2 You might have been detected and blocked as a crawler bot!
h2
h3 News Corp Australia uses software that manages crawler bot traffic on our websites. If you receive this message and are not a crawler bot (and are just a reader or subscriber), please try these steps first:

How to solve problems with dailymercury.com.au

Errors on the dailymercury.com.au 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 dailymercury.com.au on your own.