Frequently Asked Questions
Do you offer a method that replaces profane words with other characters (i.e. “@#$!”)?
Yes, documentation on this method can be found here: webpurify.live.replace
How many submissions can I send to WebPurify?
There is no limit to the number of queries you can send to WebPurify. No matter how many requests you make, 10 queries or 1,000,000, you just pay the same price. However we do limit the number of simultaneous connections from a single IP address. Please look at our pricing page to see our simultaneous request limits.
What are simultaneous requests?
Simultaneous requests are the number of requests WebPurify can process at one time per license. For an Enterprise license, if you were to submit 4 requests at one time, you would need to wait for one request to finish before you could send another. To learn about plans that offer more simultaneous requests than our Enterprise Plan, please contact firstname.lastname@example.org.
Does WebPurify work with languages other than English?
Yes, please look at our languages section to see a current list of the languages we support.
Can I have custom black and white lists?
Yes! Through our admin interface or API you can create custom white and black lists for each license key. This allows you to manage your own profanity list.
Why make this a web service as opposed to just a profanity filter library?
WebPurify eliminates the nuisance of having to maintain your own profanity database, which is a time-consuming task. We’re always working to increase the accuracy of WebPurify and to make sure it is compatible with all coding languages. As time goes on, we’ll be releasing even more new features that you will be able to implement without installing new software.
How many characters can I post to WebPurify per submission?
Currently WebPurify has a limit of 30,000 characters. The larger the text submitted, the longer it will take to return results. If you require larger submission limits please contact our sales department about a custom solution.
My application will make MANY requests to your service, can WebPurify handle it?
Yes! WebPurify is hosted in a cloud environment, which scales automatically to meet capacity. This ensures that the response time of our service and yours never slows during periods of high traffic. Please note, we do limit the number of simultaneous connections from a single IP address.
Can I host WebPurify on my own servers?
What is a Web Service or API?
We better let Wikipedia answer this one: Web Service
What are the response times for WebPurify?
Response times for our profanity filter average around 89 milliseconds or .089 seconds. This does not include travel time between your servers and ours and can also vary depending on the length of text you are submitting.
Why should I use WebPurify instead of writing my own filter?
We have a dedicated team of developers whose number one goal is to maintain the most accurate and efficient profanity filter in the universe. Using our filter lets you devote more time to building your app, instead of your own filter.
Can I have/see your list of profanity?
Nope. WebPurify is not just a list, it’s a system of detecting profanity. Our service is designed to capture many variations of every kind of profanity you can imagine (and even some that you don’t want to).
What forms of payment do you accept?
On our website we accept Visa, MasterCard, American Express and Discover. For other forms of payment please contact email@example.com
Do I need to give you my credit card info for a free trial?
How many licenses do I need?
Our Plugin and Custom Licenses work with 1 domain name or IP (ie www.yourdomain.com). If you would like to use our service with a development and live environment you will need to purchase two licenses. Our Enterprise licenses allow you to use our service with up to 6 domain names or IPs.
How do you handle words that may or may not be profane, depending on the usage? (i.e Vice President Dick Cheney)
While no profanity filter is 100% accurate, our system is designed to minimize “false positives”. To date we have received a handful of false positive reports and our support team has reacted quickly. That’s not bad considering we have had over 75,000,000 requests made to our service!
Can I see how many queries I have submitted and how many have contained profanity?
Yes, you can see your stats by logging into your account.
Why am I asked to enter in a domain name or IP when purchasing a license?
We require you enter the domain name or IP address that your requests to WebPurify will be coming from in order to ensure that our license keys are being used by paying customers.
What if I don’t have a domain name or IP address to enter at this time?
If you don’t currently have a domain name or static IP address for your application, you may enter “localhost” into the domain/IP field. This will put you license on our “watch list”.
How do I change the domain name or IP associated with my license?
You can change the domain or IP associated with your license by logging into your WebPurify account, selecting the domain you wish to change, and then clicking on “change domain for this license”. Once you submit your change it will take effect immediately.
Do you provide image moderation services?
Yes! Learn more about our Image Moderation Web Service
Do you have regional API Endpoints?
Currently our profanity filter has endpoints in the US, Europe and Asia-Pacific regions. For more information please read our documentation
Can I use WebPurify in a mobile app?
Absolutely. The best practice is to proxy the requests through code that resides on a server. Using a proxy allows you to make changes to the requests to WebPurify whenever you want without having to submit a new version of your mobile app.
Do you provide custom solutions and/or per request pricing?
Yes, please email firstname.lastname@example.org
When using cURL there is no response from WebPurify when submitting over 1024 characters.
When using cURL to make requests to our service with more than 1024 characters, set the expect header.
For example: curl_setopt($ch,CURLOPT_HTTPHEADER,array(“Expect:”));