topunblock.com

TopUnblock grants you access to blocked sites and maintains anonymity. Unblock sites such as Facebook MySpace & YouTube at school with TopUnblock! ...

topunblock.com
Domain Name topunblock.com
Favicon topunblock.com
Google Page Rank 1
Alexa Rank #339545
Page Size 7.7 KB
Ip Address 208.53.158.137
Heading H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
Images 1 GIF, 0 JPG, 0 PNG

Website Meta Analysis

Title Top Unblock | Unblock Facebook YouTube & MySpace | Anonymous
Meta Keyword top, topunblock, unblocker, facebook, unblock, myspace, anonymous, youtube
Meta Description TopUnblock grants you access to blocked sites and maintains anonymity. Unblock sites such as Facebook MySpace & YouTube at school with TopUnblock!

Technical Analysis

Webserver Apache/2.2.15 (CentOS)
Ip Address 208.53.158.137
Domain Age
Javascript Library
Language used HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from ninodezign.com.

HTML Analysis

  • date: Fri, 09 Aug 2013 05:08:57 GMT
  • server: Apache/2.2.15 (CentOS)
  • x-powered-by: PHP/5.3.3
  • cache-control: no-store, no-cache, must-revalidate
  • last-modified: Fri, 25 Jan 2013 01:50:53 GMT
  • pragma: no-cache
  • content-type: text/html; charset=utf-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA

No data whois for topunblock.com

Technical Analysis


DNS servers
ns1.dneasy.net [50.31.1.17]
ns2.dneasy.net [95.211.165.80]
ns3.dneasy.net [106.187.48.223]
ns4.dneasy.net [69.85.93.117]


DNS Records

Answer records
topunblock.com NS  ns1.dneasy.net 172800s
topunblock.com A 208.53.158.137 3600s
topunblock.com NS  ns3.dneasy.net 172800s
topunblock.com NS  ns4.dneasy.net 172800s
topunblock.com SOA
server: ns1.dneasy.net
email: unbannernetwork@gmail.com
serial: 2013013000
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 38400
172800s
topunblock.com NS  ns2.dneasy.net 172800s

Authority records

Additional records
ns1.dneasy.net 28 [16 bytes] 172800s
ns4.dneasy.net 28 [16 bytes] 172800s
ns4.dneasy.net A 69.85.93.117 172800s
ns2.dneasy.net A 95.211.165.80 172800s
ns2.dneasy.net 28 [16 bytes] 172800s
ns1.dneasy.net A 50.31.1.17 172800s
ns3.dneasy.net A 106.187.48.223 172800s
ns3.dneasy.net 28 [16 bytes] 172800s

IP 208.53.158.137 Analysis

Country Code : US
Country Code3 : USA
Country Name : United States
City : Bronx
Continent Code : 718
Latitude : 501
Longitude : 501

%rwhois V-1.5:003eff:00 rwhois.fdcservers.net (by Network Solutions, Inc. V-1.5.10-pre6)
network:Auth-Area:208.53.128.0/18
network:Class-Name:network
network:OrgName:Nicholas Webster
network:OrgID;I:FDC-10463
network:Address:12 Barlea Avenue
network:City:Manchester
network:PostalCode:M40 3WL
network:Country:GB
network:NetRange:208.53.158.137 - 208.53.158.137
network:CIDR:208.53.158.137/32
network:NetName:FDC-10463-208.53.158.137
network:OrgAbuseHandle:ABUSE438-ARIN
network:OrgAbuseName:Abuse Department
network:OrgAbusePhone:+1-312-423-6675
network:OrgAbuseEmail:abuse@fdcservers.net
network:OrgNOCHandle:TECHS72-ARIN
network:OrgNOCName:Tech Support
network:OrgNOCPhone:+1-312-423-6675
network:OrgNOCEmail:support@fdcservers.net
network:OrgTechHandle:TECHS72-ARIN
network:OrgTechName:Tech Support
network:OrgTechPhone:+1-312-423-6675
network:OrgTechEmail:support@fdcservers.net

%ok

In Page Analysis

Traffic Analysis

Magestic Backlinks

Daily Ranks

Rank Trend

Visitor Trend

Bounce Trend

HTML Analysis

HTML validation
  • 17 Errors
  • 24 Warnings
Ratio Text/Html

0.6065970453387672

Message Error
  • Warning Line 8, Column 149: character "&" is the first character of a delimiter but occurred as data
    …Unblock sites such as Facebook MySpace & YouTube  at school with TopUnblock!"/>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 32, Column 40: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    						<a href="/"><div class="nav_home"></div></a>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 33, Column 80: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …ef="https://www.unbanner.com/" target="_blank"><div class="nav_more"></div></a>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 34, Column 78: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …               <a href="/disclaimer.php"><div class="nav_disclaimer"></div></a>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 35, Column 50: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    						<a href="/terms.php"><div class="nav_terms"></div></a>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 36, Column 54: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    						<a href="/privacy.php"><div class="nav_privacy"></div></a>

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Warning Line 68, Column 190: character "&" is the first character of a delimiter but occurred as data
    …nblock sites such as Facebook MySpace & YouTube at school with TopUnblock! Jus…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 153, Column 207: cannot generate system identifier for general entity "sa"
    …zcp4iLpM%2Bt2Uj4xRQn70y%2FbVhbWAmw%3D&sa=01ccc6b4a230&opt=3">MySpace</a> | <a …

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 153, Column 207: general entity "sa" not defined and no default entity
    …zcp4iLpM%2Bt2Uj4xRQn70y%2FbVhbWAmw%3D&sa=01ccc6b4a230&opt=3">MySpace</a> | <a …

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 153, Column 209: reference not terminated by REFC delimiter
    …p4iLpM%2Bt2Uj4xRQn70y%2FbVhbWAmw%3D&sa=01ccc6b4a230&opt=3">MySpace</a> | <a hr…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 153, Column 209: reference to external entity in attribute value
    …p4iLpM%2Bt2Uj4xRQn70y%2FbVhbWAmw%3D&sa=01ccc6b4a230&opt=3">MySpace</a> | <a hr…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 153, Column 209: reference to entity "sa" for which no system identifier could be generated
    …p4iLpM%2Bt2Uj4xRQn70y%2FbVhbWAmw%3D&sa=01ccc6b4a230&opt=3">MySpace</a> | <a hr…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 153, Column 206: entity was defined here
    …czcp4iLpM%2Bt2Uj4xRQn70y%2FbVhbWAmw%3D&sa=01ccc6b4a230&opt=3">MySpace</a> | <a…
  • Warning Line 153, Column 223: cannot generate system identifier for general entity "opt"
    …xRQn70y%2FbVhbWAmw%3D&sa=01ccc6b4a230&opt=3">MySpace</a> | <a href="http://www…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 153, Column 223: general entity "opt" not defined and no default entity
    …xRQn70y%2FbVhbWAmw%3D&sa=01ccc6b4a230&opt=3">MySpace</a> | <a href="http://www…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 153, Column 226: reference not terminated by REFC delimiter
    …n70y%2FbVhbWAmw%3D&sa=01ccc6b4a230&opt=3">MySpace</a> | <a href="http://www.to…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 153, Column 226: reference to external entity in attribute value
    …n70y%2FbVhbWAmw%3D&sa=01ccc6b4a230&opt=3">MySpace</a> | <a href="http://www.to…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 153, Column 226: reference to entity "opt" for which no system identifier could be generated
    …n70y%2FbVhbWAmw%3D&sa=01ccc6b4a230&opt=3">MySpace</a> | <a href="http://www.to…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 153, Column 222: entity was defined here
    …4xRQn70y%2FbVhbWAmw%3D&sa=01ccc6b4a230&opt=3">MySpace</a> | <a href="http://ww…
  • Warning Line 153, Column 343: reference not terminated by REFC delimiter
    …KTMII2CwoglcpsmDTF8AiqzDXjtPxCjU%3D&sa=01ccc6b4a230&opt=3">FaceBook</a> | <a h…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 153, Column 343: reference to external entity in attribute value
    …KTMII2CwoglcpsmDTF8AiqzDXjtPxCjU%3D&sa=01ccc6b4a230&opt=3">FaceBook</a> | <a h…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 153, Column 343: reference to entity "sa" for which no system identifier could be generated
    …KTMII2CwoglcpsmDTF8AiqzDXjtPxCjU%3D&sa=01ccc6b4a230&opt=3">FaceBook</a> | <a h…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 153, Column 206: entity was defined here
    …czcp4iLpM%2Bt2Uj4xRQn70y%2FbVhbWAmw%3D&sa=01ccc6b4a230&opt=3">MySpace</a> | <a…
  • Warning Line 153, Column 360: reference not terminated by REFC delimiter
    …F8AiqzDXjtPxCjU%3D&sa=01ccc6b4a230&opt=3">FaceBook</a> | <a href="http://www.t…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 153, Column 360: reference to external entity in attribute value
    …F8AiqzDXjtPxCjU%3D&sa=01ccc6b4a230&opt=3">FaceBook</a> | <a href="http://www.t…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 153, Column 360: reference to entity "opt" for which no system identifier could be generated
    …F8AiqzDXjtPxCjU%3D&sa=01ccc6b4a230&opt=3">FaceBook</a> | <a href="http://www.t…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 153, Column 222: entity was defined here
    …4xRQn70y%2FbVhbWAmw%3D&sa=01ccc6b4a230&opt=3">MySpace</a> | <a href="http://ww…
  • Warning Line 153, Column 478: reference not terminated by REFC delimiter
    …95R0pLtWQGO18JO2BRt1T3Jx2CBPQPZqvt4Hb4U%3D&sa=01ccc6b4a230&opt=3">YouTube</a> |

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 153, Column 478: reference to external entity in attribute value
    …95R0pLtWQGO18JO2BRt1T3Jx2CBPQPZqvt4Hb4U%3D&sa=01ccc6b4a230&opt=3">YouTube</a> |

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 153, Column 478: reference to entity "sa" for which no system identifier could be generated
    …95R0pLtWQGO18JO2BRt1T3Jx2CBPQPZqvt4Hb4U%3D&sa=01ccc6b4a230&opt=3">YouTube</a> |

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 153, Column 206: entity was defined here
    …czcp4iLpM%2Bt2Uj4xRQn70y%2FbVhbWAmw%3D&sa=01ccc6b4a230&opt=3">MySpace</a> | <a…
  • Warning Line 153, Column 495: reference not terminated by REFC delimiter
    …95R0pLtWQGO18JO2BRt1T3Jx2CBPQPZqvt4Hb4U%3D&sa=01ccc6b4a230&opt=3">YouTube</a> |

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 153, Column 495: reference to external entity in attribute value
    …95R0pLtWQGO18JO2BRt1T3Jx2CBPQPZqvt4Hb4U%3D&sa=01ccc6b4a230&opt=3">YouTube</a> |

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 153, Column 495: reference to entity "opt" for which no system identifier could be generated
    …95R0pLtWQGO18JO2BRt1T3Jx2CBPQPZqvt4Hb4U%3D&sa=01ccc6b4a230&opt=3">YouTube</a> |

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 153, Column 222: entity was defined here
    …4xRQn70y%2FbVhbWAmw%3D&sa=01ccc6b4a230&opt=3">MySpace</a> | <a href="http://ww…
  • Warning Line 154, Column 100: reference not terminated by REFC delimiter
    …Ivm3flX3bpSMIwljqgwswGqhQxldyxrA%3D&sa=01ccc6b4a230&opt=3">Bebo</a>| <a href="…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 154, Column 100: reference to external entity in attribute value
    …Ivm3flX3bpSMIwljqgwswGqhQxldyxrA%3D&sa=01ccc6b4a230&opt=3">Bebo</a>| <a href="…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 154, Column 100: reference to entity "sa" for which no system identifier could be generated
    …Ivm3flX3bpSMIwljqgwswGqhQxldyxrA%3D&sa=01ccc6b4a230&opt=3">Bebo</a>| <a href="…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 153, Column 206: entity was defined here
    …czcp4iLpM%2Bt2Uj4xRQn70y%2FbVhbWAmw%3D&sa=01ccc6b4a230&opt=3">MySpace</a> | <a…
  • Warning Line 154, Column 117: reference not terminated by REFC delimiter
    …gwswGqhQxldyxrA%3D&sa=01ccc6b4a230&opt=3">Bebo</a>| <a href="http://www.topunb…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 154, Column 117: reference to external entity in attribute value
    …gwswGqhQxldyxrA%3D&sa=01ccc6b4a230&opt=3">Bebo</a>| <a href="http://www.topunb…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 154, Column 117: reference to entity "opt" for which no system identifier could be generated
    …gwswGqhQxldyxrA%3D&sa=01ccc6b4a230&opt=3">Bebo</a>| <a href="http://www.topunb…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 153, Column 222: entity was defined here
    …4xRQn70y%2FbVhbWAmw%3D&sa=01ccc6b4a230&opt=3">MySpace</a> | <a href="http://ww…
  • Warning Line 154, Column 234: reference not terminated by REFC delimiter
    …xeg%2B4diobKsdKdJwJ1TQV%2BKgVeq9lifw%3D&sa=01ccc6b4a230&opt=3">eBuddy</a></div>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 154, Column 234: reference to external entity in attribute value
    …xeg%2B4diobKsdKdJwJ1TQV%2BKgVeq9lifw%3D&sa=01ccc6b4a230&opt=3">eBuddy</a></div>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 154, Column 234: reference to entity "sa" for which no system identifier could be generated
    …xeg%2B4diobKsdKdJwJ1TQV%2BKgVeq9lifw%3D&sa=01ccc6b4a230&opt=3">eBuddy</a></div>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 153, Column 206: entity was defined here
    …czcp4iLpM%2Bt2Uj4xRQn70y%2FbVhbWAmw%3D&sa=01ccc6b4a230&opt=3">MySpace</a> | <a…
  • Warning Line 154, Column 251: reference not terminated by REFC delimiter
    …xeg%2B4diobKsdKdJwJ1TQV%2BKgVeq9lifw%3D&sa=01ccc6b4a230&opt=3">eBuddy</a></div>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 154, Column 251: reference to external entity in attribute value
    …xeg%2B4diobKsdKdJwJ1TQV%2BKgVeq9lifw%3D&sa=01ccc6b4a230&opt=3">eBuddy</a></div>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 154, Column 251: reference to entity "opt" for which no system identifier could be generated
    …xeg%2B4diobKsdKdJwJ1TQV%2BKgVeq9lifw%3D&sa=01ccc6b4a230&opt=3">eBuddy</a></div>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 153, Column 222: entity was defined here
    …4xRQn70y%2FbVhbWAmw%3D&sa=01ccc6b4a230&opt=3">MySpace</a> | <a href="http://ww…

Visitor Analysis

Daily Visitor

327 visits