Website not working but email still works
Summary
This guide helps you troubleshoot and resolve: Website not working but email still works. Follow the steps below to fix the issue.
Common Causes
Website Inaccessible but Email Still Working
It can be frustrating when your website is offline but your email continues to arrive without issue. This happens because website traffic and email traffic are routed separately using different DNS records. While your Mail Exchange (MX) records are correctly directing email to your mail server, the records pointing visitors to your website may be incorrect, or the web server itself may be experiencing an outage.
Quick Fix Steps
- Confirm the outage by visiting your website from a different device or mobile network.
- Clear your browser cache or open the site in an incognito window to rule out local caching.
- Test both the www and non-www versions of your domain (e.g., www.yourdomain.com.au and yourdomain.com.au) to see if the issue affects only one.
- Check your domain's DNS records to ensure the A record points to the correct web server IP address.
- Verify that your SSL certificate has not expired.
- Verify that your hosting subscription is active and has not expired.
- If you host with 220 Internet Services, Open a Ticket and our Brisbane team will investigate.
Detailed Instructions
Understanding DNS Separation
DNS records act like a directory for your domain. Different record types handle different services:
- A Record: Maps your domain name to the IPv4 address of your web server.
- AAAA Record: Maps your domain name to the IPv6 address of your web server.
- MX Record: Directs email to your mail server.
- CNAME Record: Aliases one domain name to another, often used for www subdomains.
Because email uses MX records and your website uses A, AAAA, or CNAME records, an issue with your web server or A record will not affect email delivery.
DNS Management Menu Paths
Use the following paths to locate your DNS records depending on your hosting control panel or domain registrar:
- cPanel: Log in to cPanel, navigate to the Domains section, and select Zone Editor. Click Manage next to your domain to view and edit records.
- Plesk: Log in to Plesk, go to Websites & Domains, select your domain, and click DNS Settings.
- GoDaddy: Log in to your GoDaddy account, select My Products, click Domains, select your domain, and choose Manage DNS.
- Namecheap: Log in to your Namecheap account, go to Domain List, click Manage next to your domain, and select the Advanced DNS tab.
Checking Your A Record
- Access your domain's DNS management interface using the paths above.
- Locate the A Record for your root domain.
- Compare the IP address listed against the IP address provided by your web host.
- If the addresses do not match, update the record with the correct IP address and save the changes.
- Allow time for DNS propagation, which can take anywhere from a few minutes to 48 hours.
Checking Your AAAA Record
If your server supports IPv6, an incorrect or missing AAAA record can prevent some visitors from accessing your site while others remain unaffected.
- In your DNS management interface, locate the AAAA Record for your domain.
- Compare the IPv6 address listed against the IPv6 address provided by your web host.
- If your host does not provide IPv6, ensure no AAAA record exists for your root domain.
- If an incorrect AAAA record is present, update it with the correct IPv6 address or remove it.
- Allow time for DNS propagation after making changes.
Checking SSL Certificate Expiry
An expired SSL certificate can cause browsers to block access to your website with a security warning, making it appear offline while email continues to work normally.
- Open your website in a web browser.
- Look for the padlock icon in the address bar.
- Click the padlock and select Connection is secure or Certificate to view certificate details.
- Check the expiry date. If the certificate has expired, contact your hosting provider or certificate authority to renew it.
- If you host with us, Open a Ticket and our Brisbane team can assist with SSL renewal.
Testing Web Server Connectivity
Ping may be blocked by firewalls and does not confirm that your web server is responding to HTTP or HTTPS requests. Use a browser-based or command-line connectivity test instead.
- Open your website in a web browser using both
http://yourdomain.com.auandhttps://yourdomain.com.au. - Note any error messages, such as Connection timed out, Server not found, or SSL security warnings.
- Open Command Prompt on Windows or Terminal on macOS.
- Run the command
curl -I https://yourdomain.com.au(replace with your actual domain). - A response beginning with
HTTP/1.1 200 OKorHTTP/2 200indicates the web server is responding. A connection timeout or refusal suggests the server is down or unreachable. - Try accessing the website using a mobile device on 4G or 5G to bypass your local Wi-Fi network.
Verifying Web Server Service Status
If you have server access, confirm that the web server software is running.
- Apache: Check that the Apache service (httpd or apache2) is active and running.
- Nginx: Check that the Nginx service is active and running.
- IIS: Check that the World Wide Web Publishing Service is started.
If the service is stopped, restart it. If it fails to start, check the web server error logs for details.
Checking Web Server Error Logs
Error logs can reveal why the web server is not serving your website.
- Access your hosting control panel or connect to your server via SSH or Remote Desktop.
- Locate the error log files. Common locations include:
- Apache:
/var/log/apache2/error.logor/var/log/httpd/error_log - Nginx:
/var/log/nginx/error.log - IIS: Check Event Viewer under Windows Logs > Application, or the site-specific log files.
- Look for recent entries around the time the outage began.
- Common errors include permission issues, missing configuration files, or resource limits being reached.
- If you are unsure how to interpret the logs, Open a Ticket and our Brisbane team will analyse them for you.
Hosting Type Considerations
Troubleshooting steps vary depending on your hosting environment:
- Shared Hosting: You typically do not have access to server-level logs or service status. Use your control panel (cPanel or Plesk) to check DNS, SSL, and hosting status. If the server itself is down, you must contact your provider.
- VPS: You have root or administrator access and can check service status, error logs, and firewall rules directly. Ensure your web server service is running and that ports 80 and 443 are open.
- Dedicated Server: You have full control over the server. Verify service status, inspect error logs, check firewall configuration, and confirm that DNS records point to the correct server IP address.
Checking www vs Non-WWW Domain Issues
Sometimes only one version of your domain loads correctly.
- Visit
http://www.yourdomain.com.auandhttp://yourdomain.com.auseparately. - If only one version works, check your DNS for a CNAME or A record for the www subdomain.
- Ensure your web server is configured to respond to both the root domain and the www subdomain.
- Check for redirect rules in your .htaccess file or web server configuration that may be sending traffic to the wrong version.
Avoid changing MX records while troubleshooting website issues. Modifying email routing records can interrupt business email delivery.
Remember — If you host with us, you don't need to do this yourself — just Open a Ticket and our Brisbane team will get it sorted.
Still Having Issues?
💻 Open a Ticket