Is history.ca down or not working?

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

What to do if the site history.ca is not available? Try our guide.

history.ca outage reports in the last 24 hours

history.ca - 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:
Home - History CANADA
Protocol:
https
Status code:
200
Page size:
53.0 KB
Response time:
1.628sec.
IP:
18.239.69.50
Response headers:
content-type: text/html; charset=UTF-8
transfer-encoding: chunked
connection: close
date: Sat, 05 Oct 2024 11:23:43 GMT
server: Apache
link: <https://www.history.ca/wp-json/>; rel="https://api.w.org/", <https://www.history.ca/wp-json/wp/v2/pages/7>; rel="alternate"; type="application/json", <https://www.history.ca/>; rel=shortlink
cache-control: max-age=300
expires: Sat, 05 Oct 2024 11:28:43 GMT
x-frame-options: SAMEORIGIN
x-content-type-options: nosniff
strict-transport-security: max-age=86400
vary: Accept-Encoding
set-cookie: kpid=32ceafe1edc740e4978df95fd8973f0f; Path=/; expires=Sat, 05 Apr 2025 11:23:43 GMT; Max-Age=15724800; domain=.history.ca
x-cache: Miss from cloudfront
via: 1.1 d5da174e34f35b7d1482b8432bf7e084.cloudfront.net (CloudFront)
x-amz-cf-pop: PRG50-C1
x-amz-cf-id: Ngei5IDTJeZnLgoHkcmuH00MblDQRKSEm3t1Sacrfylo5lBL19NkXw==
DNS records:
A address18.239.69.18
ttl60
A address18.239.69.49
ttl60
A address18.239.69.72
ttl60
A address18.239.69.50
ttl60
MX exchangealt2.us.email.fireeyecloud.com
priority30
MX exchangealt1.us.email.fireeyecloud.com
priority20
MX exchangeprimary.us.email.fireeyecloud.com
priority10
MX exchangealt3.us.email.fireeyecloud.com
priority40
NS valuens-550.awsdns-04.net
NS valuens-1637.awsdns-12.co.uk
NS valuens-343.awsdns-42.com
NS valuens-1331.awsdns-38.org
TXT entriesMS=ms17483832
TXT entriesfacebook-domain-verification=ry2m6ijz51ixeu8cip2nvol4eudcr0
TXT entriesCnw4u+TKd1L4ZXOm365IQS549a3wsQPtQO+jNVVy4EMDoioZwKFeoQYLag+n193tQhiyoBChZzUIXVaoLKcThw==
TXT entriesv=spf1 include:spf.protection.outlook.com -all
TXT entriesgoogle-site-verification=0naG0KX_XgJL64snSF53315j8KkX5Fz52K0zCMKBLrw
SOA nsnamens-1637.awsdns-12.co.uk
hostmasterawsdns-hostmaster.amazon.com
serial1
refresh7200
retry900
expire1209600
minttl86400

SEO headers

h3 Featured
h3 Get the History Newsletter
h2

How to solve problems with history.ca

Errors on the history.ca 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 history.ca on your own.