domstat.net

Website loading time

during the test: 1.47 s

cable connection (average): 1.55 s

DSL connection (average): 1.64 s

modem (average): 6.07 s

HTTP headers

HTTP/1.0 200 OK

Content-Type: text/html; charset=UTF-8

Expires: Sat, 15 Oct 2011 07:54:26 GMT

Date: Sat, 15 Oct 2011 07:54:26 GMT

Cache-Control: private, max-age=0

Last-Modified: Tue, 30 Aug 2011 13:22:08 GMT

ETag: "ff768939-3134-4980-b711-d495fdba28fe"

X-Content-Type-Options: nosniff

X-XSS-Protection: 1; mode=block

Server: GSE

Information about DNS servers

Received from the first DNS server

Request to the server "feedburnerstatus.blogspot.com"
Received 47 bytes from address 212.227.123.29#53 in 95 ms
Request to the server "feedburnerstatus.blogspot.com"
You used the following DNS server:
DNS Name: slv2.1and1.es
DNS Server Address: 212.227.123.29#53
DNS server aliases:

Host feedburnerstatus.blogspot.com not found: 2(SERVFAIL)
Received 47 bytes from address 212.227.123.29#53 in 95 ms

Received from the second DNS server

Request to the server "feedburnerstatus.blogspot.com"
Received 47 bytes from address 87.106.231.188#53 in 102 ms
Request to the server "feedburnerstatus.blogspot.com"
You used the following DNS server:
DNS Name: vps9.audinex.com
DNS Server Address: 87.106.231.188#53
DNS server aliases:

Host feedburnerstatus.blogspot.com not found: 5(REFUSED)
Received 47 bytes from address 87.106.231.188#53 in 99 ms

Subdomains (the first 50)

Typos (misspells)

Location

IP: 209.85.175.132

continent: NA, country: United States (USA), city: Mountain View

Website value

rank in the traffic statistics:

There is not enough data to estimate website value.

Basic information

website build using CSS

code weight: 32.23 KB

text per all code ratio: 11 %

title: The FeedBurner Status Blog

description:

keywords:

encoding: UTF-8

language: en

Website code analysis

one word phrases repeated minimum three times

two word phrases repeated minimum three times

three word phrases repeated minimum three times

B tags

Update (2011-06-08):

Update (8:00am PST 19-Mar):

Update (9:04am PST 28-Feb): 

Unfortunately, one of the reported side-effects has been that some email clients are categorizing mail from this new standardized "from" address into their bulk/spam folders.We are in the process of rolling back this change. Once complete the "from" address will again use the address field found in the Communication Preferences section of the Email Subscriptions service page. Update (7:25am PST 14-Feb): Email delivery has been restored to its previous functionality.

U tags

I tags

Issue:

Update (8:00am PST 19-Mar): Stats production issues have been resolved and both of the missing days restored.

Update (9:04am PST 28-Feb): The issue has been resolved. Posts should now be delivered normally to Twitter. If your posts are still not being delivered, please re-connect your Twitter account to your FeedBurner account by clicking "Add a Twitter account" in the Publicize tab, re-entering your Twitter username and password in the window that is opened, and clicking Save on the Publicize form after the window closes.

images

headers

H1

H2

Followers

Search the Status Blog

Archive

More Info about FeedBurner

H3

Followers

Search the Status Blog

Archive

More Info about FeedBurner

H4

H5

H6

internal links

external links