返回博客

How to protect a website from DDoS attacks and verify the connection

Prepare your origin and DNS records, route web traffic through HotWall and verify that real visitors can still use the site.

If your website stops responding, record when the problem started and try a familiar page. Check the errors and resource graphs at your hosting provider. A traffic spike after a newsletter, a stalled database and a DDoS attack can all look like a timeout to a customer. If the service is already down, contact your host while you investigate. DNS changes take time to reach visitors.

Prepare your domain and origin

You need access to the authoritative DNS zone and the address, protocol and port of the web server that serves your site. Save the current root and www records with their TTLs. Identify the names used by mail, APIs and other services before changing the web records. Keep the previous values available in case you need to restore them.

Route web traffic through HotWall

  1. Check plans and site limits. In the dashboard, add your root domain, such as example.com, and enter the origin server. Use the protocol and port on which the origin already accepts requests.
  2. Open the DNS instructions for that site. Copy the name, type and value of each record. If the dashboard asks for a TXT record to prove ownership, add it. Use the routing target displayed for your own domain.
  3. Edit the zone at your current DNS provider. You can keep your existing nameservers if the provider supports the records shown. If the dashboard gives you a CNAME target for the root, check for ALIAS or CNAME flattening support. Preserve MX and mail verification records. Add www as a separate hostname in the dashboard if your visitors use it.
  4. Run the dashboard DNS check. If the site stays pending, compare each record with the dashboard, look for a doubled zone suffix and allow for the TTL of the old records.

Verify the result from a visitor’s browser

Wait for the site to become active. Open a familiar HTTPS page from another connection, check the certificate and try a real visitor workflow such as signing in or opening the checkout. Find the visit in your request log by time and path. An active site that returns an error may have the wrong origin address, protocol or port. Check each public hostname separately.

Keep a baseline

Record the cutover time, normal request volume and error rate so you can recognise changes during future incidents. If the origin still accepts direct web traffic, discuss proxy access rules with your hosting provider and verify monitoring and integrations before restricting access.

Read about HotWall website DDoS protection or connect your site when you have your DNS records and origin details ready.

分享: