welivesecurity.com caiu - problemas, instabilidade e status

O que aconteceu com welivesecurity.com, por que o site caiu e não funcionou? Aqui você pode ver quem mais está tendo o mesmo problema com welivesecurity.com, bem como possíveis soluções. De acordo com nossas estatísticas, o seguinte geralmente não funciona: .

Status atual: Sem falhas

No momento, de acordo com nossos dados, welivesecurity.com está funcionando bem, mas falhas únicas são possíveis. Se welivesecurity.com não funcionar para você, relate seu problema e escreva um comentário.
Adicionar comentário

O que fazer se o site welivesecurity.com não estiver disponível? Experimente nosso guia.

welivesecurity.com - relatórios de interrupção nas últimas 24 horas

welivesecurity.com - relatórios de erros e falhas, métodos de solução de problemas

Deixe seu comentário descrevendo a falha e compartilhe com outros usuários como resolver o problema.
  • Não é necessário registro.
  • Mensagens com linguagem obscena e insultos, bem como infringindo a lei, não podem ser publicadas.
  • Links ativos em o texto da mensagem não é publicado, mas exibido em texto simples.
  • É proibido postar dados pessoais próprios e de outras pessoas: endereços, números de telefone, e-mails, contas em mensageiros instantâneos, etc.

Informações técnicas

Título da página principal:
Award-winning news, views, and insight from the ESET security community
Descrição da página principal:
WeLiveSecurity comes from the brains at ESET - experienced researchers with in-depth knowledge of the latest threats and security trends.
Protocolo:
https
Código de status:
200
Tamanho da página:
82.6 KB
Tempo de resposta:
0.225seg.
IP:
91.228.167.128
Cabeçalhos de resposta:
content-type: text/html; charset=UTF-8
referrer-policy: no-referrer-when-downgrade
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
access-control-allow-origin: *
content-security-policy: default-src 'none'; child-src https://disqus.com https://vars.hotjar.com; connect-src 'self' http://ad.doubleclick.net https://*.akamaihd.net https://*.akstat.io https://*.eset.com https://*.hotjar.com https://*.hotjar.io https://adservice.google.com https://captcha.welivesecurity.com https://cc.welivesecurity.com https://cdn.esetstatic.com https://cdn.linkedin.oribi.io https://in.hotjar.com https://px.ads.linkedin.com https://region1.google-analytics.com https://stats.g.doubleclick.net https://trial-eum-clientnsv4-s.akamaihd.net https://trial-eum-clienttons-s.akamaihd.net https://vc.hotjar.io https://ws22.hotjar.com https://ws32.hotjar.com https://www.facebook.com https://www.google-analytics.com https://www.google.com https://www.googletagmanager.com https://www.opinionstage.com wss://*.hotjar.com wss://ws1.hotjar.com; font-src 'self' data: https://script.hotjar.com; form-action 'self'; frame-ancestors 'self'; frame-src 'self' https://*.slideshare.net https://bid.g.doubleclick.net https://c.disquscdn.com https://disqus.com https://m.facebook.com https://open.spotify.com/ https://platform.twitter.com https://player.vimeo.com https://share.transistor.fm https://tpc.googlesyndication.com https://vars.hotjar.com https://www.buzzsprout.com https://www.facebook.com https://www.googletagmanager.com https://www.instagram.com https://www.opinionstage.com https://www.podbean.com https://www.screencast.com https://www.slideshare.net https://www.youtube-nocookie.com https://www.youtube.com; img-src 'self' data: https://*.ads.linkedin.com https://*.esetstatic.com https://adservice.google.com https://analytics.twitter.com https://c.disquscdn.com https://captcha.welivesecurity.com https://connect.facebook.net https://googleads.g.doubleclick.net https://px.ads.linkedin.com https://referrer.disqus.com https://region1.google-analytics.com https://script.hotjar.com https://secure.eset.com https://syndication.twitter.com https://t.co https://twitter.com https://www.facebook.com https://www.google-analytics.com https://www.googletagmanager.com https://www.hotjar.com https://www.linkedin.com https://www.youtube.com; manifest-src 'self'; media-src 'self' https://web-assets.esetstatic.com; object-src 'self' https://content.screencast.com; script-src 'self' 'unsafe-eval' 'unsafe-inline' https://a.disquscdn.com https://assets.esetstatic.com https://cdn.esetstatic.com https://connect.facebook.net https://embed.playbuzz.com https://googleads.g.doubleclick.net https://platform.twitter.com https://script.hotjar.com https://snap.licdn.com https://static.ads-twitter.com https://static.hotjar.com https://tpc.googlesyndication.com https://welivesecurity.disqus.com https://www.buzzsprout.com https://www.google-analytics.com https://www.googleadservices.com https://www.googletagmanager.com https://www.instagram.com https://www.opinionstage.com https://www.youtube.com; style-src 'self' 'unsafe-inline' https://assets.esetstatic.com https://c.disquscdn.com https://cdn.esetstatic.com; worker-src 'self'; report-uri https://www-welivesecurity-com.api.cspconsole.com/v1/csp/report; report-to csp-endpoint;
reporting-endpoints: csp-endpoint="https://www-welivesecurity-com.api.cspconsole.com/v1/csp/report"
x-edps-request-status: normal
strict-transport-security: max-age=15724800
x-akamai-transformed: 9 20289 0 pmb=mRUM,2
cache-control: public, max-age=41671
date: Tue, 01 Oct 2024 21:46:22 GMT
transfer-encoding: chunked
connection: close, Transfer-Encoding
set-cookie: AKA_A2=A; expires=Tue, 01-Oct-2024 22:46:22 GMT; path=/; domain=welivesecurity.com; secure; HttpOnly
server-timing: cdn-cache; desc=HIT, edge; dur=17, origin; dur=0, ak_p; desc="1727819182902_390659236_224204637_1684_1429_3_4_-";dur=1
link: <https://www.googletagmanager.com>;rel="preconnect",<https://cdn.esetstatic.com>;rel="preconnect"

Cabeçalhos de SEO

h3 Latest Articles
h2 Let us keep you up to date
h3 Follow us

Como resolver problemas com welivesecurity.com

Erros no site welivesecurity.com podem ser do lado do servidor ou do seu lado (lado do cliente). Se não houver praticamente nada a ser feito sobre erros no lado do servidor (resta apenas esperar para que o site volte a funcionar), então com erros do lado do cliente é possível resolver o problema com a disponibilidade de welivesecurity.com por conta própria.