Short answer: If the site is not opening, the first thing to do is read the error text shown by the browser: “This site can’t be reached” points to the domain name or DNS, a privacy and certificate warning points to SSL, 500–503 codes point to the server, and an “account suspended” page points to hosting. If the site does not open on another device and mobile data either, the problem is not with the visitor but with the site.
When a website will not open, the cause usually falls into one of six categories: an expired domain name, an incorrect or recently changed DNS record, an expired SSL certificate, a suspended hosting account or one that has reached its resource limits, server or software related 5xx errors, and a cache serving old content. The error text displayed by the browser is the quickest clue for identifying which layer has failed.
A report that a website will not open does not always originate from the website itself; the problem may be the visitor’s connection, a browser extension, or the device clock. This guide first explains how to distinguish where the problem lies, then covers browser error codes, domain names and DNS, SSL, hosting, HTTP status codes, WordPress specific errors, and caching. At the end, you will find a step by step checking sequence and maintenance habits that prevent recurrence.
Video transcript
Why will a website not open? The cause usually falls into one of six categories: the domain name, DNS, SSL certificate, hosting, server errors, or caching. The first task is to distinguish whether the problem is with the website or the device. Other websites, mobile data, an incognito window, another person, and the device clock are checked in sequence. The browser error indicates the layer. If the name cannot be resolved, inspect the domain name and DNS; for a privacy warning, the certificate; for a redirect loop, HTTPS settings; and for errors in the five hundreds, the server. Checks proceed from the outside inward: first the device and network, then the domain name and DNS, followed by the certificate and hosting control panel. After the correction, all cache layers are cleared. A substantial portion of outages follow a schedule. Automatic renewal, certificate tracking, availability monitoring, updates with backups, and a list of control panel access details prevent recurrence. All error codes and the checking sequence are on the page. If your website will not open, you can write via WhatsApp with a screenshot of the error screen. Onur Freelance dot com.
The first distinction: Is the problem with the website or the device?
The first task is to establish whether the website will not open for everyone or only on one device; intervening on the server without making this distinction wastes time. Google Chrome’s connection errors help page also begins troubleshooting by checking the spelling of the address and determining whether the problem affects one website or several.
- Do other websites open? If no websites open, the problem is with the internet connection, modem, or router.
- Does it open using mobile data? A website that will not open on the office network but opens over a phone’s mobile data points to a local network, firewall, or DNS cache problem.
- Does it open in an incognito window? For a website that opens without problems in incognito mode, browser extensions, cookies, and the cache are examined.
- Does it open for another person? Asking someone in another city or on a different carrier to check shows whether the failure is widespread.
- Is the device clock correct? If the date and time are incorrect, even a valid certificate will appear faulty.
If the website will not open on any device or connection, the problem is most likely with the domain name, DNS, certificate, or server. The sections below address these layers individually.
Which layer does the browser error message indicate?
The browser’s error code indicates whether the failure involves address resolution, the connection, the certificate, or the server response. Google’s Chrome error messages page lists the meanings of the most common codes; their interpretation from the website owner’s perspective is as follows:
| Error | Chrome’s explanation | The first place to check on the website side |
|---|---|---|
| ERR_NAME_NOT_RESOLVED | The hostname does not exist or has a different IP address | Domain name expiration and DNS records |
| ERR_CONNECTION_TIMED_OUT | The connection took too long; the page may be too busy | Whether the server is running and its resource usage |
| ERR_CONNECTION_REFUSED | The page did not allow the connection or blocked it | The web server service and firewall rules |
| Privacy warnings and certificate errors | The certificate is invalid, the name does not match, or the date is incorrect | The SSL certificate’s expiration date and the domain names it covers |
| ERR_TOO_MANY_REDIRECTS | The page is trying to redirect too many times | Conflicting HTTPS, www, and CDN redirect settings |
| ERR_EMPTY_RESPONSE | The page sent no data and may be down | Server error logs and a crashed application |
If the browser displays a plain error page or text such as “An error occurred” instead of an error code, the connection has been established and the server has responded, but it has reported a problem. In this case, check the HTTP status code.
The domain name may have expired
When a domain name is not renewed, the registrar stops DNS routing for the address, and the website will not open even though the content and server remain in place. ICANN’s expired registration recovery policyfor generic extensions requires DNS resolution to be interrupted for a certain period after expiration, and if visitors are redirected to a page during this time, that page must clearly show that the registration has expired and explain the renewal steps.
If the registrar’s “this domain has expired” page or a parking page appears instead of the website, the first places to check are the registrar’s control panel and billing emails. The policy provides for renewal reminders to be sent before and after expiration; these emails often go unnoticed because they are sent to a former administrator’s or agency’s address. When renewal is completed, the registrar restores the previous DNS settings, but if the registration has entered the deletion stage, the recovery process becomes more involved. For country extensions such as .com.tr, time frames and rules vary according to the relevant registration authority.
Page contents
DNS records may be incorrect or recently changed
DNS is the system that translates a domain name into the IP address of the server hosting the website; if the nameserver or A record points to the wrong server, the website will not open or will display an old version. This error frequently occurs after changing hosting, transferring a domain name to another company, or switching to a CDN service.
DNS changes do not take effect everywhere immediately; records are held in carriers’ and devices’ DNS caches for the specified caching period. After a change, this is why one person may reach the new server while another reaches the old server. Shutting down the old server during a migration before propagation is complete causes the website to stop opening for some visitors; this risk is managed in the WordPress website migration plan by timing the DNS switchover.
For businesses that keep their email service with a separate provider, forgetting MX records during a DNS change is also common; the website opens, but emails do not arrive. Before changing nameservers, a list of the existing records is taken, and the following entries in particular are compared:
- NS records: Determine which DNS provider manages the domain name.
- A and AAAA records: Show which server IP address the main domain name will point to.
- CNAME record: Defines which address subdomains such as www connect to.
- MX and TXT records: Carry email delivery settings as well as domain verification and sender identity settings.
The SSL certificate may have expired or been installed incorrectly
When an SSL certificate expires or does not cover the website’s exact address, the browser stops loading the page with a security warning stating that the connection is not private. Most visitors turn back at this warning, so a website that technically works becomes effectively unavailable.
Two possibilities are distinguished when identifying the reason for the warning. Chrome notes that NET::ERR_CERT_DATE_INVALID can also appear when the device’s date and time are incorrect; if the warning appears on only one computer, the clock is checked first. If the warning appears on every device, the certificate’s expiration date, the domain names it covers, and whether automatic renewal is working are examined in the hosting control panel. The certificate must cover both the www and non-www versions; a certificate issued for only one produces a name mismatch error at the other address.
The hosting account may be suspended or have reached a resource limit
If the website will not open and a warning page from the hosting company appears instead, the account status is the first suspect. The hosting company may suspend the account because of an unpaid invoice, a violation of its terms of use, detected malware, or excessive resource usage on a shared server. In this situation, the company’s “account suspended” page appears instead of the website, or no connection is established at all.
Resource limits produce a less obvious pattern: the website opens for part of the day but returns timeouts or 503 errors during busy hours. With shared hosting, processor, memory, and concurrent process limits are defined by the package; when plugin load or bot traffic strains these limits, the server rejects new requests. How to choose a hosting package according to the website’s requirements is explained in detail in the web hosting selection article.
Let us diagnose your unavailable website together
Share a screenshot of the error screen and your domain name so we can identify together which layer is causing the problem. The preliminary assessment is free; if intervention is needed, the scope and price are clarified the same day, before work begins.
HTTP status codes: What do 4xx and 5xx errors tell you?
If the page will not open even though the server responds, the type of problem can be determined from the HTTP status code: the 4xx range indicates errors related to the request itself, while the 5xx range indicates a server-side failure. MDN’s HTTP status code reference groups responses into five classes and defines the most common error codes as follows:
- 403 Forbidden: The server recognizes the request but does not grant access to the content; file permissions, a security plugin, or an IP block are possible causes.
- 404 Not Found: The requested resource cannot be found; if this affects one page, deleted content is investigated, and if it affects all internal pages, the permalink settings are examined.
- 429 Too Many Requests: Too many requests have been sent within a certain period; rate limiting is active.
- 500 Internal Server Error: The server does not know how to process the request; this is the generic error used when no more specific 5xx code can be found.
- 502 Bad Gateway: The server acting as a gateway received an invalid response from the upstream server; this occurs on websites using a CDN or reverse proxy.
- 503 Service Unavailable: The server is not ready to handle the request; maintenance mode and excessive load are the most common causes.
- 504 Gateway Timeout: The gateway did not receive a timely response from the upstream server.
The Network tab in the browser’s developer tools shows which code the page returns. For permanently removed content, code 410 can also be used instead of 404; MDN defines this code as a situation where content has been permanently deleted from the server and no redirect address is available.
Critical errors, white screens, and database connections on WordPress websites
Most loading failures on WordPress websites result from incompatibilities involving plugins, themes, or the PHP version, and usually appear as an “a critical error has occurred” warning on the screen or a completely blank white screen. WordPress.org’s common errors documentlists the possible causes of a critical error as plugin conflicts, theme incompatibility, an incompatible PHP version, reaching the memory limit, and corrupted core files.
When a critical error occurs, WordPress sends information about the source of the error and a recovery mode link to the administrator email address; that inbox is therefore the first place to check. The message “Error establishing a database connection” usually results from the database name, username, password, or server information in wp-config.php being out of date, or from the database server not responding.
Enabling debugging mode on a live website, renaming plugin folders, or changing the PHP version without taking a backup can make the problem worse. Reading the error log and safely locating the source is the purpose of the WordPress troubleshooting service. If the error appeared suddenly and the website contains unfamiliar administrator accounts, strange redirects, or unknown files, the problem may be an attack; in this case, the steps for recovering a hacked WordPress website are followed.
How do caching and redirect loops lock up a website?
Caching can cause an old error page to be displayed even after the problem has been fixed; conflicting redirects can prevent the page from opening altogether. Both situations produce confusing symptoms, such as a website that “sometimes opens and sometimes does not.”
The browser cache, website caching plugin, server cache, and CDN cache are separate layers; when one is cleared and another is not, old content continues to be served. In a typical redirect loop, the website is forced to HTTP at the CDN and HTTPS at the server, and the two rules send requests back to each other indefinitely. Chrome displays this as ERR_TOO_MANY_REDIRECTS and recommends clearing cookies on the visitor’s side; on the website owner’s side, HTTPS and www redirects need to be defined in a single place.
A step by step checking sequence when a website will not open
When a website will not open, troubleshooting produces results fastest when it proceeds from the outermost layer inward. The sequence followed in practice is:
- Check whether the website opens on a different device, network, and in an incognito window.
- Note the error text or code displayed by the browser and take a screenshot.
- Verify the domain name’s expiration date in the registrar’s control panel.
- Examine whether the nameservers and A record point to the correct server.
- Check the SSL certificate’s expiration date and the addresses it covers.
- Read the account status, resource usage, and error logs in the hosting control panel.
- Identify the HTTP status code returned by the page.
- On a WordPress website, examine the administrator email and error log.
- After the correction, clear all cache layers and test the website again from different devices.
Recording a brief note of what was observed at each step prevents the same checks from being repeated when the information is passed to the support or technical team.
Preventive maintenance to keep the website from going down again
A substantial portion of loading failures can be prevented in advance because they follow a schedule: domain and certificate expiration dates are known, updates can be planned, and backups can be taken regularly. The following habits are established for a lasting routine:
- Automatic renewal: Enable automatic renewal for the domain name and hosting, and direct billing emails to the business’s current address.
- Certificate tracking: Before its expiration date, check that the automatically renewed certificate has actually been renewed.
- Availability monitoring: Set up a monitoring service that checks the website at regular intervals and sends notifications when it goes down.
- Update discipline: Perform plugin, theme, and PHP updates after taking a backup and, where possible, testing them in a staging environment.
- Access list: Keep a record in one place of who holds access to the domain name, hosting, and DNS control panels.
These tasks, which eliminate schedule-related causes of a website failing to open, can be placed on a regular schedule through the annual WordPress maintenance and updates service. Monthly maintenance is optional and ranges from 500 – 2,000 TL, depending on the scope.
Let us plan together to keep your website continuously available
Let us prevent similar outages from recurring by bringing domain name, certificate, backup, and update tracking into a single routine. The preliminary assessment of the current situation is free; we send the proposed maintenance scope together with its price on the same day.
Related guides
- How do you fix a WordPress critical error?
- Error establishing a database connection
- If your WordPress website loads slowly
- How can you tell whether a website has been hacked?
- Hosting prices 2026
- Annual WordPress maintenance and updates
- SSL certificates and website security
- What is Cloudflare, and how does it benefit a website?
- If your WordPress website broke after an update
- If you cannot log in to the WordPress admin panel
- How do you fix 500 Internal Server Error?
- 403 Forbidden error: Resolving blocked access
- ERR_TOO_MANY_REDIRECTS redirect loop
- The “Your connection is not private” error and SSL
- How long does a DNS change take?
Frequently asked questions
The website will not open for me but opens for others. Why?
In this situation, the problem is most likely with the device or local network. Browser extensions, cookies, the DNS cache, security software, or the device clock are checked; the website is tested in an incognito window and using mobile data.
What does “Web page not available” mean?
It is a general warning that the browser could not reach the address or that the server did not return a page at that address. It appears if the domain name has expired, the DNS record is wrong, or the page has been removed; if the same address does not open on another device and mobile data either, the problem is with the site.
Does a website go down immediately when the domain name expires?
The registrar usually stops DNS routing after expiration, and the website will not open. The previous settings are restored when renewal is completed; however, if the registration has entered the deletion stage, recovery may be more difficult and expensive.
Why will the website not open for some people after a DNS change?
DNS records are kept in carriers’ and devices’ caches for the specified period. Until this period expires, some visitors continue to reach the old server; if the old server has been shut down, the website will not open for them.
Are browser privacy and certificate warnings the website owner's problem?
If the warning appears on every device, the certificate has most likely expired or does not cover the address. If it appears on only one device, that device’s date and time are checked first.
What is the difference between a 500 error and a 503 error?
500 is a generic error indicating that the server encountered an unexpected condition while processing the request. 503 indicates that the server cannot provide service at that moment, usually because it is undergoing maintenance or is overloaded.
What should you do first when a critical error message appears in WordPress?
The first task is to check the error notification and recovery mode link that WordPress sent to the administrator email address. A backup is taken before making changes; the source of the error is identified from the error log.
Is there a way to find out immediately when the website goes down?
Yes, availability monitoring services that check the website at regular intervals send an email or message notification when an outage occurs. This makes it possible to intervene in the problem before visitors notice it.
Call us
Call us for detailed information.
Let us call you!
Share your phone number and let us give you a call!
Our other services
- › Corporate web design
- › Ecommerce website development
- › SEO optimization
- › WordPress website development
- › Google advertising management
- › WordPress speed optimization
Service areas
- › Web design in Sakarya
- › Web design in Tekirdağ
- › Web design in Bursa
- › Web design in Beşiktaş
- › Web design in Şişli
- › Web design in Tuzla
- › Web design in Ümraniye
- › Web design in Kadıköy
- › Web design in İstanbul
- › Web design in Ankara
- › Web design in Ataşehir
- › Web design in Üsküdar
- › Web design in Kartal
- › Web design in Maltepe
- › Web design in Pendik
- › Web design in Kocaeli
- › Web design in İzmir
- › Web design in Antalya
