Is cdc.gov down or not working?

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

What to do if the site cdc.gov is not available? Try our guide.

cdc.gov outage reports in the last 24 hours

cdc.gov - 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:
Centers for Disease Control and Prevention | CDC
Protocol:
https
Status code:
200
Page size:
67.8 KB
Response time:
0.877sec.
IP:
198.246.102.49
Response headers:
content-type: text/html
srv: 6
access-control-allow-origin: *
x-ua-compatible: IE=edge
access-control-allow-headers: Access-Control-Allow-Headers, Origin, Accept, X-Requested-With, Content-Type, Access-Control-Request-Method, Access-Control-Request-Headers
date: Mon, 30 Sep 2024 20:02:25 GMT
transfer-encoding: chunked
connection: close, Transfer-Encoding
set-cookie: akamai_visit_id=4d8e1002265451d5785Z; expires=Wed, 30-Sep-2026 20:02:25 GMT; path=/; domain=.cdc.gov; secure,Akamai-Request-ID=4d8e1002265451d5785Z; path=/; domain=cdc.gov
strict-transport-security: max-age=31536000 ; includeSubDomains ; preload
DNS records:
A address198.246.106.49
ttl21600
A address198.246.102.49
ttl21600
MX exchangeprimary.us.etp.fireeyegov.com
priority10
MX exchangealt2.us.etp.fireeyegov.com
priority30
MX exchangealt1.us.etp.fireeyegov.com
priority20
MX exchangealt3.us.etp.fireeyegov.com
priority40
NS valuens1.cdc.gov
NS valuens2.cdc.gov
NS valuens3.cdc.gov
TXT entriesatlassian-domain-verification=qjHCJ33pyZHmggxdcFDtGiegrc/iLSyVUIG0LAu1g7XW1JnMdaY8G8pbMUY1Z4hm
TXT entriesgoogle-gws-recovery-domain-verification=42225222
TXT entries268BC041572123F15C5566E5F3D88675FABCC028427B501AE228CA9BB31630D5
TXT entriesamazonses:OhxI8Nxovqf1xBmhK5S9kNk7vo9XV4GmGe6LVc+ji80=
TXT entries4FF7-1931-E8C2-912B-94CF-BCB0-806A-7442
TXT entriesMS=ms84056562
TXT entriesgoogle-site-verification=GkbnFA_aF3RXaZOC3deEsrGqs0fmTXyys2hbIn1nVcM
TXT entriesadobe-idp-site-verification=4089552e88740d878b0400d184ab01c0b7391e6dc85796732000450e3476fc93
TXT entriesv=spf1 ip4:51.5.72.0/24 ip4:172.81.81.38 ip4:51.4.72.0/24 ip4:51.5.80.0/27 ip4:51.4.80.0/27 ip4:172.81.81.50 ip4:172.81.82.50 ip4:63.123.152.4 ip4:40.92.0.0/15 ip4:172.81.82.79 ip4:172.81.80.64 ip4:172.81.81.39 ip4:172.81.82.87 ip4:172.81.82.88 ip4:155.95,.96.50 ip4:155.95.86.50 ip4:23.90.98.102 ip4:124.17.27.36 ip4:149.72.0.0/16 ip4:198.21.0.0/21 ip4:50.31.32.0/19 ip4:167.89.0.0/17 ip4:68.232.140.57 ip4:68.232.140.79 include:_s0.cdc.gov -all
TXT entriesgoogle-site-verification=nZIK8Rc0sw4MxlgnsYseSBTdcyDXeLFR6P5FIAbgSEM
TXT entriesv4ixju/hXVFXszYswwinkbStpHoDb361lQekI6rkjQ2DV4HHKdN/FJPvMAO88x1rTaRwf29UYwPAq6LqldNWZQ==
TXT entriesgoogle-site-verification=qZbBdujV5kZQv_pCqV2wpfSU25odH35HQukm5ACyLNs
TXT entriesZOOM_verify_yEK5MgTwT72nP5URz-eoaA
TXT entriesapple-domain-verification=VOKePKhT9MhX9zmq
TXT entriesidentrust_validate=B/Pm/IvNx8tLDDFRsJXBs+oweQGmx08QZ6xK0IvBQn3R
SOA nsnamens2.cdc.gov
hostmasterhostmaster.cdc.gov
serial746123750
refresh10800
retry3600
expire604800
minttl3600

SEO headers

h2 Featured Topics
h2 A to Z
h2 News All News
h2 Scientific Journals
h2 Science at CDC

How to solve problems with cdc.gov

Errors on the cdc.gov 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 cdc.gov on your own.