The Gcore Customer Portal is being updated. Screenshots may not show the current version.
Gcore Web Application Security product, along with Basic WAF and Bot protection, are soon to be deprecated. Instead, we'll be introducing a new and improved Web Application & API Protection.
Web Application Security
BillingCreate protected resourceUse Web Application Security and CDNConfigure protection settingsAdd an SSL certificateRate LimiterSet the Access PolicyDeny accessSet the X-Forward-For headerCheck reports
How do I change an A record?What criteria do you analyze?I see lots of requests from several IPs. Could this be an attack?I changed my A record long time ago, but you are not filtering it. What to do?Attackers have found out my origin IP and are attacking it directly. What should I do? directly. What should I do?Who is attacking us?Will a blacklisted user get unblocked after a particular time?During a DDoS attack, we changed your IP address, but we still have problems with the performance. Why?Do you protect against attacks targeted at DNS?Can you disable the protection for some time for the entire site or certain parts of the site?How long does the service enabling take?Which web crawlers doesn't your service block?Force an IP banGet all banned IP addresses for all resourcesRenew SSL certificates
I changed my A record long time ago, but you are not filtering it. What to do?
We can not assist you in this situation. TTL reduction isn't effective because the previous record has been cached on DNS servers with the previous TTL value.
Was this article helpful?
Not a Gcore user yet?
Discover the all-in-one Web security solution by Gcore