Domain: | examplesite.com |
Account Plan: |
professional plan
upgrade
|
Hosting IP Address: |
127.0.0.1
Manage
|
Firewall IP Address: |
c868843601.102.sucurifirewall.com
|
Internal Domains: |
c868843601.102.sucurifirewall.com
2a02:fe80::/29
192.88.134.0/23
185.93.228.0/22
199.223.236.179
146.148.117.213
23.251.134.134
178.33.238.180
142.4.217.0/24
167.114.0.0/24
192.99.17.0/24
5.196.79.0/24
130.211.0.0/16
104.155.0.0/16
Created at: |
12/Nov/2018 05:51:05
Date corresponds to the time when the configuration file was created. This information might be inaccurate due to the way Unix file systems work, but will give you an approximation of how old the account is.
|
Enterprise Address: |
(No enterprise address set)
Normally, several hosting accounts reside on a single server and share that server's IP address. Dedicated IP addresses are usually used for large SSL-encrypted secure websites and particularly large and/or traffic-heavy sites.
|
Wildcard Domain: |
Yes, it is wildcard
A wildcard DNS record is a record in a DNS zone that will match requests for non-existent domain names and it is specified by using an asterisk as the leftmost label of a domain name, e.g. "*.example.com"
|
DNS Cache Creation Time: |
Some of the DNS records used in this dashboard are cached temporarily, these records are used to determine if the website is active or not and to reverse the IP addresses associated to the domain. The cache is re-generated per-site every time the settings are updated or when the cache is flushed.
Wed, 31 Dec 1969 19:00:00 -0500
|
Eth0 Compatibility: | (not available) |
Setting | Value | ||||||||
---|---|---|---|---|---|---|---|---|---|
proxy_active_text | Not Activated | ||||||||
account_plan | professional | ||||||||
domain | example.com | ||||||||
domain_ip | 127.0.0.1 | ||||||||
enterprise_addr | <Empty> | ||||||||
domain_reverse | 127.0.0.1 | ||||||||
internal_ip_visible | 127.0.0.1 127.0.0.1 | ||||||||
internal_domain | 4378a6a452.10006.sucurifirewall.com | ||||||||
internal_domain_ip | 127.0.0.1 | ||||||||
internal_domain_nodes |
|
||||||||
internal_ip_explained |
|
||||||||
colliding_ip | False | ||||||||
security_level | high | ||||||||
admin_access | open | ||||||||
comment_access | restricted | ||||||||
cache_mode | docache | ||||||||
force_sec_headers | enabled | ||||||||
unfiltered_html | block_unfilter | ||||||||
block_php_upload | block_uploads | ||||||||
behind_cdn | <Empty> | ||||||||
http_flood_protection | <Empty> | ||||||||
compression_mode | disabled | ||||||||
spdy_mode | enabled | ||||||||
max_upload_size | 5m | ||||||||
detect_adv_evasion | enabled | ||||||||
ids_monitoring | enabled | ||||||||
minimize_static_files | <Empty> | ||||||||
aggressive_bot_filter | disabled | ||||||||
uri_based_caching | disabled | ||||||||
failover_time | 30 | ||||||||
ssl_keys | enabled | ||||||||
force_https | https | ||||||||
ssl_sni_tls | disabled | ||||||||
origin_protocol_port | 80 | ||||||||
api_info |
|
||||||||
whitelist_list |
|
||||||||
blacklist_list |
|
||||||||
whitelist_dirs_list |
|
||||||||
blacklist_dirs_list |
|
||||||||
noncache_dirs_list |
|
||||||||
path_pass_2f_combo |
|
||||||||
block_useragent_list |
|
||||||||
block_referer_list |
|
||||||||
block_cookie_list |
|
||||||||
ahttp_method_list |
|
||||||||
domain_alias_list |
|
||||||||
block_from_viewing | <Empty> | ||||||||
block_from_posting | <Empty> | ||||||||
brotli | disabled | ||||||||
dns_zone_owner | user@example.com | ||||||||
dns_is_owner | True | ||||||||
dns_records |
|
If your site runs on multiple hosting servers, you can add multiple hosting IP addresses for them to be load balanced. You can also provide a failover backup IP address that will be used in case your main hosting IP addresses are not responding.
Note: If there is one single IP address in the list and you want to change it because the system is flagging it as collision prone, add a new address first and then delete the old one. This is necessary because the system requires at least one entry in the list in order to work.
This option defines the timeframe the system takes to consider the server unhealthy between consecutive errors. Once this threshold has been reached consecutive requests will be directed to the next server.
Note: Changing this value will have no effect if you don't have any backup IP address configured.
The option allows you to restrict the maximum upload size to be allowed through our firewall. Some hosting companies do not allow large uploads and this option will not bypass the limit imposed in these cases, but allows you to restrict a maximum size to reduce the chance of large uploads hitting your server.
Domain aliasing allow you to add additional domains that will be redirected (via 301) to this site. For example, if your site is "example.com", you can add "example.net" as an alias.
Domain Alias | |
---|---|
another-example.com | |
demo-domain.net |
Our Firewall already runs on top of a CDN (Content Delivery Network) that speeds your website by bringing your pages closer to the visitors. However, if you still want to use an external CDN, it is supported by our system. All you have to do is configure in your CDN settings so that the origin (hosting) IP is pointed to this address:
This will cause all traffic to be routed first through your CDN before hiting our Firewall and your server. Only enable this option if all your traffic is being routed through the CDN first. Note that you won't need to change the DNS A records to our IP address if you do such setup.
If you wish to cancel your billing (recurring payment), you need to do it here: Website Firewall Billing. If what you want is to delete the domain from your account you can use the button below.
Remember to change the DNS records for your site to point to the real server. Once the domain is deleted from the account all its settings will be reset, and we will keep the logs and statistics collected so far in case that we need to investigate something.