When Your Website Is Under Attack | DScholar Web
Cybersecurity • Real-world incident report

Your Website Can Be Under Attack Even When Everything Looks Normal

How DScholar Web identified and contained a resource-exhaustion bot traffic incident—and what it reveals about the value of fully managed websites.

DScholar Web cybersecurity illustration showing website protection, servers and a secure laptop
Layered protection matters: website-facing defenses and origin-server safeguards must work together.
The hidden threat

A Website Doesn’t Have to Be Hacked to Be in Trouble

When business owners think about cyberattacks, they often imagine stolen passwords, defaced websites, or hackers gaining access to confidential information.

But not every cyberattack involves breaking into a website. Sometimes, attackers simply overwhelm a website with requests until its hosting infrastructure struggles to keep up.

The website may still be accessible. There may be no obvious warning message. No files may have been stolen or modified. Yet behind the scenes, server resources can be pushed to their limits, potentially affecting website performance, customer experience, and business operations.

Recently, the DScholar Web team encountered exactly this type of threat while investigating a website within our managed infrastructure. Here is what happened, how we responded, and what every business owner should learn from the incident.

Case study

The Real-World Incident: A Website Under Heavy Bot Traffic

During a server performance investigation, our team identified an unusual resource-consumption pattern affecting dscholarweb.com.

The server’s CPU utilization had climbed to approximately 97–99%. This was not normal visitor activity.

Our investigation revealed numerous automated requests targeting specific website URLs, often with unusual, malformed query parameters. These requests were particularly problematic because they could bypass normal page-caching behavior and force the server to perform additional processing.

In simpler terms, instead of receiving a ready-made page, the server was repeatedly being asked to generate responses using its processing resources. Multiply that activity across many simultaneous requests, and even a normally healthy website can experience serious performance pressure.

What We Discovered

  • The suspicious traffic originated from cloud-hosted IP addresses within the 47.79.0.0/16 network range.
  • Automated requests repeatedly targeted website pages with abnormal query strings.
  • These requests were creating unnecessary processing workloads.
  • Multiple application processes were consuming significant CPU resources.
  • The attack traffic was reaching the server directly, bypassing the website’s existing Cloudflare protection.

Protecting a website’s public domain is not always the same as protecting its underlying server.

A critical security gap

Why a Security Layer Alone Wasn’t Enough

Many website owners assume that enabling a content delivery network or cloud-based security service automatically protects their website against every possible threat. Unfortunately, cybersecurity is rarely that simple.

In this incident, we had already configured a targeted Cloudflare security rule to identify and block the suspicious request pattern. The rule was working: Cloudflare’s analytics confirmed that hundreds of matching requests were being blocked.

But the server continued receiving malicious-looking requests. Why? Because the attackers were connecting directly to the server’s public IP address, bypassing the protection applied at the website’s cloud security layer.

Effective security requires visibility into both the website and the underlying server.

Our response

How DScholar Web Responded

Our response followed a systematic approach focused on identifying the cause, containing the traffic, and restoring normal performance without unnecessarily disrupting legitimate website activity.

01 / INVESTIGATE

We Investigated the Server, Not Just the Website

We examined resource usage, active processes, web requests, and network connections to distinguish ordinary workload from abnormal automated traffic.

02 / IDENTIFY

We Identified the Suspicious Request Pattern

Unusual query parameters were triggering additional processing. Identifying them enabled a targeted response rather than blocking legitimate visitors indiscriminately.

03 / CONTAIN

We Applied Protection at Multiple Levels

A cloud security rule addressed the malformed requests, while a server firewall rule dropped direct connections from the identified attacking network.

04 / VERIFY

We Verified the Results

We checked firewall counters, reviewed resource utilization, and tested website responsiveness to confirm that the mitigation was effective.

Measured recovery

From Nearly 99% CPU Usage to Normal Operation

Performance indicatorDuring the incidentAfter mitigation
Server CPU utilizationApproximately 97–99%Approximately 15%
Suspicious direct connectionsReaching the serverBlocked from the identified network
Website responsivenessAt risk from excessive processing loadHomepage test completed in approximately 0.074 seconds
Security responseCloud protection alone was insufficientCloud and server-level protection working together

CPU utilization dropped dramatically after the server-level block was applied. The website returned a successful HTTP 200 response, and a subsequent homepage test completed in approximately 74 milliseconds.

We also verified that the website’s page-caching system was generating cached HTML, helping support efficient content delivery.

These measurements were taken during post-mitigation checks. They represent the observed recovery, not a guarantee that future attacks cannot occur. The investigation identified abusive traffic and resource exhaustion; it did not establish that attackers compromised the website or accessed private data.

The business impact

What Could Happen Without Active Website Management?

Imagine a business owner discovering that their website has suddenly become slow or intermittently unavailable. Their first reaction might be to blame their hosting provider, website design, or recent content updates.

They might even purchase a more expensive hosting plan, hoping additional server resources will solve the problem. But if the underlying cause is abusive automated traffic, increasing capacity alone may not address it.

Without technical investigation, the real issue can remain unresolved. The business could face slower page loads, interrupted customer journeys, lost inquiries, or reduced customer confidence.

This is why website management must go beyond publishing content, installing updates, or keeping a domain active. A business website needs ongoing technical oversight.

The managed advantage

What Fully Managed Website Security Means at DScholar Web

At DScholar Web, we believe a website should be a business asset—not another technical burden for its owner. Our fully managed website approach brings together several essential responsibilities.

Performance Monitoring

Investigating abnormal resource consumption and unexpected slowdowns.

Traffic Analysis

Distinguishing genuine visitor activity from suspicious automated requests.

Layered Security

Combining website-facing protections with appropriate server-level safeguards.

Performance Optimization

Reducing unnecessary processing while preserving important dynamic functionality.

Incident Response

Investigating threats, applying proportionate mitigations, and verifying results.

Ongoing Maintenance

Keeping website infrastructure and essential components properly managed.

No responsible provider can promise that cyberattacks will never happen. What matters is the ability to recognize threats and respond effectively.

What business owners should know

Five Lessons Every Website Owner Should Take From This Incident

1

A functioning website can still be under attack.

High resource usage and abnormal traffic may be early warning signs even when the homepage loads.

2

Cloud-based protection must be configured correctly.

Attackers may attempt to bypass domain-level security by targeting the origin server directly.

3

Not all traffic is good traffic.

Large volumes of automated requests can consume resources without delivering business value.

4

Security must account for legitimate customers.

Broad restrictions can disrupt real visitors or essential website features. Targeted mitigation is often preferable.

5

Website security is an ongoing responsibility.

A rule that stops today’s attack may not stop tomorrow’s. Monitoring and adaptation remain essential.

Looking ahead

Your Business Deserves More Than a Website That Simply Looks Good

A professional website should be fast, reliable, secure, and ready to support your business. Achieving that requires more than attractive design; it requires technical expertise behind the scenes, particularly when unexpected problems arise.

The incident involving dscholarweb.com demonstrates how coordinated investigation and layered response can bring a heavily stressed server back to normal operation.

For businesses choosing a fully managed website service, that is the value of professional oversight: someone is responsible for maintaining, optimizing, and helping protect the digital infrastructure that supports your work.

You focus on running your business. DScholar Web takes responsibility for managing, maintaining, optimizing, and helping protect your website.

Cyber threats will continue to evolve. Your website management strategy should evolve with them.

Ready for a Website That’s Professionally Managed and Protected?

Whether you’re launching a new business website or looking for expert management of an existing one, explore DScholar Web’s fully managed website services—built around performance, reliability, and security.

Explore DScholar Web →
#WebsiteSecurity #CyberSecurity #ManagedWebsites #WebsitePerformance #BotAttacks #DScholarWeb
Scroll to Top