Introducing Webpage In-Browser Monitoring

February 1st, 2016
Posted in WebSitePulse News

We are delighted to announce the launching of our newest service - webpage in-browser monitoring.

Check out the features and see if it's right for you:


  • Performs within a real browser (WebKit engine)
  • Provides a real browser experience from a user perspective
  • Verifies keywords
  • Verifies DOM components against CSS selectors
  • Supports JavaScript and CSS
  • Uses multiple simultaneous connections
  • Provides screenshots on the last check and on every error
  • Provides detailed report with graphs



 Click to Enlarge


Click to Enlarge 

Webpage In-Browser vs. In-Browser Transaction Monitoring

Similarly to the in-browser transaction monitoring, the webpage in-browser provides a real browser experience from a user perspective. Clients can actually ‘experience’ the availability and performance of their webpage’s web applications the same way their website’ visitors do, i.e. via a real browser engine.

While the in-browser transaction is based on the Firefox engine (GECKO) and our clients need to fill in a set of actions that we perform afterwards, the webpage in-browser is based on the WebKit engine identical to the Google Chrome’s one, and clients provide only an URL which we then have to load.

Webpage In-Browser vs. Full-Page Website Monitoring

Both services load the webpage along with all the components on it (images, CSS, JavaScript). However, webpage In-browser is more useful when the client needs to see how his website visitors view a specific webpage as that monitoring service occurs in a real browser. In addition, it will show a realistic view on the page load time. It performs the network requests simultaneously.

In contrast, full-page website monitoring will perform every network request separately. However, it is suitable when you need to check whether all components on the page load properly. 

For more detailed comparison between the two services, see the table below.

Full Page
Performs in Browser -
Browser Page Load -
Screenshot on Every Check -
Execute JS -
Execute CSS -
Multiple Simultaneous Connections -
Monitoring Interval
Maximum References to Check
Soft Timeout
Keep Detailed Logs
Traceroute on Error
Forced Monitoring
IPv6 -
XML Requests
Request Timeout
Page Load Timeout
Exclude URLs
Include Additional URLs -
Alert If Keywords Not Found
Alert If Keywords Found
Custom Headers
Force TLS/SSL Version
Bandwidth Limit -

Clients who have been using full-page monitoring, may continue to do so unless they decide to upgrade to webpage in-browser.

Curious how webpage in-browser  may further fulfill your monitoring needs?

We are now offering up to 2 targets for a period of one month free of charge.

Try Webpage In-Browser Monitoring Now

How to Earn with WebSitePulse

August 19th, 2015
Posted in WebSitePulse News

Click to Enlarge

Looking for an extra income? We’ve got an idea: why don’t you enroll in our affiliate program to start cashing in?

With over 37 000 satisfied customers around the world, we are now giving you the opportunity to become our affiliate partner and earn one of the highest referral commissions in the industry. Even if online marketing is not your strong suit, you can take advantage of our ready-to-use marketing tools and start making money. It really is that easy.


To enroll in our program, you should simply submit an online application via our site:

We will review your application and send you an e-mail notification within 2 business days.


We may reject your application in case your website contains illegal, threatening or defamatory content. Also, if you plan to use extensive messaging, which we call “spamming” by the way, or decide to place multiple direct links on blogs,  message boards and such, unsolicited email, etc., please note that you risk compromising your affiliate account this way. Of course, it's best that you read our full Terms and Conditions  (you know, the part which everyone scrolls quickly and agrees to) to get a better idea of what you can and cannot do.

So, without further ado, let's get to the serious part:

How Our Affiliate Program Works:

Once approved, we will:

  • Configure an affiliate account for you located at our resellers’ interface.
  • Email you the credentials. After login in, make sure you locate the Billing info section, so you can submit your personal details and receive our payments.

Next, you need to figure out what your affiliate commission is going to be as we give you the opportunity to select from three types of campaigns. You can create the following campaigns - one at a time:

  1. One-time commission: 20.00% of the 1st paid invoice of the referred client.
  2. Limited-time commission: Higher percentage for a short period - 10.00% of the payments for 3 months.
  3. Lifetime commission: Lower percentage for the lifetime of the referred account - 5.00% of every paid invoice.

Now remember, you can create up to ten campaigns, but you can refer a customer to a single campaign only.


If you are finished setting up your campaigns, go to the Link Generator area and generate your own, unique link. This link contains a unique ID which we will use to track all customers you refer to us for the respective campaign. After you get the link, you can use it on any of our logos and place it on your website(s).

What You Should Know:

You will earn a commission based on the paid invoices for WebSitePulse accounts, purchased by customers who followed the affiliate link on your site to WebSitePulse, or provided your unique affiliate ID upon subscription, unless agreed otherwise.

Commissions that have been due for over 30 days and are over $ 50.00 will be eligible for claim. We do that to ensure that a customer has not made use of our 30-day money-back guarantee to get a refund.

If a customer receives a refund or credit for a product that generated a commission under this paragraph and we have paid you the commission already, we will deduct that commission from your next payment.

If you close your affiliate account or this affiliate account is terminated by WebSitePulse, any commissions over $ 5.00, which are not claimed at the time of the account closure, will be eligible for claim and will be paid no later than 90 days from the termination.

That's pretty much it. Happy hunting!



















Security notification for CVE-2015-0235 (GHOST vulnerability)

January 28th, 2015
Posted in Industry News, WebSitePulse News, Tech

A significant Linux vulnerability that allows remote code execution to Linux server(s) was announced late yesterday, named GHOST: CVE-2015-023. Full details of the vulnerability are available at While the issue has been fixed as early as Mar 21, 2013 it was not marked as a security threat and as a result the patch was not backported to most of the stable and long-term-support distributions like RHEL, Centos, Ubuntu 12.04 etc which left them vulnerable.

Updates for CentOS are already available in the Updates repository so a simple "yum update" will install the required patches to mitigate this vulnerability.

Qualys have provided a simple C program to test if a machine is vulnerable

cat > GHOST.c << EOF
#include <netdb.h>
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <errno.h>

#define CANARY "in_the_coal_mine"

struct {
  char buffer[1024];
  char canary[sizeof(CANARY)];
} temp = { "buffer", CANARY };

int main(void) {
  struct hostent resbuf;
  struct hostent *result;
  int herrno;
  int retval;

  /*** strlen (name) = size_needed - sizeof (*host_addr) - sizeof (*h_addr_ptrs) - 1; ***/
  size_t len = sizeof(temp.buffer) - 16*sizeof(unsigned char) - 2*sizeof(char *) - 1;
  char name[sizeof(temp.buffer)];
  memset(name, '0', len);
  name[len] = '\0';

  retval = gethostbyname_r(name, &resbuf, temp.buffer, sizeof(temp.buffer), &result, &herrno);

  if (strcmp(temp.canary, CANARY) != 0) {
  if (retval == ERANGE) {
    puts("not vulnerable");
  puts("should not happen");

$ gcc GHOST.c -o GHOST

We have verified that all WebSitePulse servers have latest updates installed and are not vulnerable.





Security Notification for SSLv3 POODLE Vulnerability

October 16th, 2014
Posted in Industry News, WebSitePulse News

As you probably know, a number of news sources, corporations, and the OpenSSL team reported yesterday 14 October 2014 that version 3 of Secure Sockets Layer (SSLv3) is vulnerable at the protocol level. More information about the vulnerability can be found here -  CVE-2014-3566.

To prevent any potential leaks from this vulnerability we have immediately disabled SSLv3 on all our web servers including the API endpoints. Our monitoring agents are not affected by this change and will continue to support SSLv3 for the time being in order to be able to monitor properly servers that do support SSLv3 only. We are urging all customers to disable SSLv3 on hosts interacting with the our services as soon as possible and upgrade to use Transport Layer Service (TLS).

Here are a few samples how to configure your potentially vulnerable services and disable SSLv3.



Change all SSLProtocol directives in your httpd config to


and restart the server.


Add/edit the the following text to your server directive

ssl_protocols TLSv1 TLSv1.1 TLSv1.2;

If you can't  disable SSL 3.0 entirely,  there is TLS_FALLBACK_SCSV  patch that can help avoid the attack, if both the client and the server support it.


Internet users in China hit with a massive DNS issue

January 21st, 2014
Posted in WebSitePulse News, Tech, Tech

Today (Jan 21, 2014) between 07:00 and 09:00 UTC mainland China was hit by a wave of network issues. A large number of both Chinese and international domains were reporting connection timeouts and were completely unaccessible. The cause for this was that for some reason a large number of domains were resolving to a single IP address - The problem was reported as resolved in most places around 08:50. Due to the DNS caching infrastructure however a lot of users will still be affected until the cached bogus records expire. Users were suggested to use alternative DNS servers like Google's We strongly recommend if you are using a DNS caching server in China to flush it as soon as possible to avoid DNS issues

The news sources in China first blamed it on a DNS poisoning of the root and the gTLD DNS servers. This however is not the case since the networks outside mainland China were not affected at all. Our investigation showed DNS responses from authoritative name servers coming with bogus data when queried from our servers in Beijing, Shangai and Guangzhou.

For example our first notice of the issue was when we requested the A record of from (, which is one of the authoritative DNS serves for,

the response was      37621     IN      A

instead of  the correct record which is      900     IN      CNAME

This suggests that the response packet was modified in transit and the most likely culprit is the Golden Shield Project (also known as The Great Firewall of China). A possible reason for the misshap is that instead of blocking the IP address all DNS queries were redirected to this IP. Ironically they actually succeeded blocking the IP by creating a massive DDOS attack from all Chinese users who were making connections to this address while trying to access different sites.

The offending IP has an interesting story itself but I'll just put a few pointers
 - It is owned by Sophidea, Inc. registered on the address 2710 Thomes Ave Suite 884, Cheyenne, WY, 82001, US. Reuters ran a special story about this address a few years ago (
 - While there is scant information regarding Sophidea, Inc I can see that they are providing hosting services to a large number of companies and the IPs from this range were frequently reported for spam
 - Hosted on the same network range is which was created to provide means to bypass the China Firewall and provide anonymous Internet access. Ultrareach Corp - the company which owns UltraSurf is registered on the same postal address in Wyoming above. There was some discussion of the actual value of the services provided by UltraSurf  ( but still their service might have something to do with the Chinese goverment wanting to restrict access to this netblock

 Update Jan 22, 2014

The widespread news that a DNS poisoning attack has taken place are largely false. While there was secondary DNS cache poisoning due to this problem the initial error came from the Great Firewall of China and its regional sub-systems. First were affected the domains with low TTL which were frequently visited by Chinese internet users like Weibo and Baidu, but not all sites were affected - for example was getting correct IPs during the whole period.

An interesting fact is that after the IP for a DNS servers was set to the bogus address, which at the moment was already unreachable we were still getting bogus DNS responses from it. Here is an example from our DNS cache logs converted for better explanation

1. Query address
2. We have cached NS records and
3. Find address for

response from ( - this should not happen. The gtld servers should return NS records, not A 19613 IN  A

4.  Find address for
response from ( - this should not happen. The gtld servers should return NS records, not A 34332 IN  A

5. Find address for from the above DNS server addresses (both are
response from - this IP was not reachable at the time. It is obviously coming from a different location pretending to be it 36993 IN  A

 Another fact about the IP  - it was routed via Dynamic Internet Technology Inc.( which lists among its clients (banned in China) and is developing Freegate (an anti-censorship software). Their network took most of the traffic which at the time seemed like a massive DDOS attack. The estimates from some Chinese providers state that more than 200 million users were affected. This raises the question about the security of the Great Firewall. By setting similar DNS filtering rules a malicious attacker can direct the traffic of all China users to any single IP in the world effectively bringing it down in minutes. Currently China has more than 600 million internet users and for comparison the largest botnet in the world to date was estimated at around 30 million bots.

We will update this post with additional information as soon some official statement regrading the issue is made. Please let us know if you have any thoughts on this.



DNS - Domain Name System. The global DNS infrastructure serves as an Internet address book. It allows you to find the IP address needed to connect to a domain name. For example currently resolves to the IP address Additionally it serves information about the email servers behind an email address (MX records), the email servers that are allowed to send email from a domain (SPF records), IPv6 addresses (AAAA records) and more. See more on DNS

DNS spoofing - an attack serving bogus DNS responses to trick users to connect to a different IP address or service. Similar to DNS cache poisoning.

DNS hijacking - an attack that compromises a trusted DNS server or the packets coming from it to redirect the users to different addresses.Also called DNS redirection.

NS records - a typical DNS record containing the domain names and/or IP addresses of the DNS servers responsible for a domain

A records - a DNS record containg the IP address(es) corresponding to a domain name

Golden Shield (The Great Firewall of China) - a large censorship and surveilance project run by the goverment of China. In addition to the capability of blocking specific domains and addresess it is supposed to be able to do  DNS filtering and redirecton and Man-in-the-middle attacks.