allunblocked.com

Unblock all websites using the AllUnblocked service. Access any site such as Facebook or YouTube while at school. ...

Display Widget for this domain on your website. Click Here
Processing update domain...

Overview Info

  • Domain Name
    allunblocked.com
  • Favicon
  • Alexa Rank
    #57775
  • Google Page Rank
    PR 2
  • Ip Address
    208.53.158.137
  • Page Size
    7.7 KB
  • Images
    1 GIF, 0 JPG, 0 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 0 0 0 0 0

Website Meta Analysis



  • Title
    All Unblocked | Unblock all Websites | Unblock Facebook YouTube & MySpace
  • Meta Keyword
    unblock, all, youtube, myspace, facebook, unblocked
  • Meta Description
    Unblock all websites using the AllUnblocked service. Access any site such as Facebook or YouTube while at school.

Technical Analysis



  • Webserver
    Apache/2.2.15 (CentOS)
  • Ip Address
    208.53.158.137
  • Domain Age
    3 Years, 6 Months, 9 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Thu, 19 Sep 2013 14:32:51 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
Domain name: allunblocked.com

Registrant Contact:
Nicholas Webster
NA NA ()

Fax:
12 Barlea Avenue
Manchester, P M40 3WL
GB

Administrative Contact:
NA
Webster ( email )
+7.894992029
Fax:
12 Barlea Avenue
Manchester, P M40 3WL
GB

Technical Contact:
NA
Nicholas Webster ( email )
+7.894992029
Fax:
12 Barlea Avenue
Manchester, P M40 3WL
GB

Status: Locked

Name Servers:
ns1.dneasy.net
ns2.dneasy.net
ns3.dneasy.net
ns4.dneasy.net

Creation date: 28 Feb 2010 13:30:00
Expiration date: 28 Feb 2014 13:30:01

DNS Analysis


DNS servers
ns4.dneasy.net
ns1.dneasy.net
ns3.dneasy.net
ns2.dneasy.net


DNS Records

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

Authority records

Additional records
ns2.dneasy.net 28 [16 bytes] 172800s
ns2.dneasy.net A 95.211.165.80 172800s
ns1.dneasy.net A 50.31.1.17 172800s
ns4.dneasy.net 28 [16 bytes] 172800s
ns3.dneasy.net 28 [16 bytes] 172800s
ns4.dneasy.net A 69.85.93.117 172800s
ns3.dneasy.net A 106.187.48.223 172800s
ns1.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:Zenex 5ive Limited
    network:OrgID;I:FDC-1013
    network:Address:5 Jupiter House, Calleva Park
    network:City:Aldermaston, Reading
    network:PostalCode:RG7 8NN
    network:Country:GB
    network:NetRange:208.53.158.137 - 208.53.158.137
    network:CIDR:208.53.158.137/32
    network:NetName:FDC-1013-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

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 5 Errors
  • 22 Warnings
Ratio Text/Html
  • 0.5954169318905156
Message Error
  • Error Line 35, 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 36, 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 37, 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 38, 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 39, 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 156, Column 207: cannot generate system identifier for general entity "sa"
    …ZcwKTiknUIG3AH6%2FP1rbSLteRg4UMFqA%3D&sa=3b86a54&opt=3">MySpace</a> | <a href=…

    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 156, Column 207: general entity "sa" not defined and no default entity
    …ZcwKTiknUIG3AH6%2FP1rbSLteRg4UMFqA%3D&sa=3b86a54&opt=3">MySpace</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.

  • Warning Line 156, Column 209: reference not terminated by REFC delimiter
    …wKTiknUIG3AH6%2FP1rbSLteRg4UMFqA%3D&sa=3b86a54&opt=3">MySpace</a> | <a href="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 156, Column 209: reference to external entity in attribute value
    …wKTiknUIG3AH6%2FP1rbSLteRg4UMFqA%3D&sa=3b86a54&opt=3">MySpace</a> | <a href="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 156, Column 209: reference to entity "sa" for which no system identifier could be generated
    …wKTiknUIG3AH6%2FP1rbSLteRg4UMFqA%3D&sa=3b86a54&opt=3">MySpace</a> | <a href="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 156, Column 206: entity was defined here
    …3ZcwKTiknUIG3AH6%2FP1rbSLteRg4UMFqA%3D&sa=3b86a54&opt=3">MySpace</a> | <a href…
  • Warning Line 156, Column 218: cannot generate system identifier for general entity "opt"
    …3AH6%2FP1rbSLteRg4UMFqA%3D&sa=3b86a54&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 156, Column 218: general entity "opt" not defined and no default entity
    …3AH6%2FP1rbSLteRg4UMFqA%3D&sa=3b86a54&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 156, Column 221: reference not terminated by REFC delimiter
    …6%2FP1rbSLteRg4UMFqA%3D&sa=3b86a54&opt=3">MySpace</a> | <a href="http://www.al…

    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 156, Column 221: reference to external entity in attribute value
    …6%2FP1rbSLteRg4UMFqA%3D&sa=3b86a54&opt=3">MySpace</a> | <a href="http://www.al…

    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 156, Column 221: reference to entity "opt" for which no system identifier could be generated
    …6%2FP1rbSLteRg4UMFqA%3D&sa=3b86a54&opt=3">MySpace</a> | <a href="http://www.al…

    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 156, Column 217: entity was defined here
    …G3AH6%2FP1rbSLteRg4UMFqA%3D&sa=3b86a54&opt=3">MySpace</a> | <a href="http://ww…
  • Warning Line 156, Column 342: reference not terminated by REFC delimiter
    …dlHU1uTySww8e6yelCKGUj6nStOpxDLs%3D&sa=3b86a54&opt=3">FaceBook</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 156, Column 342: reference to external entity in attribute value
    …dlHU1uTySww8e6yelCKGUj6nStOpxDLs%3D&sa=3b86a54&opt=3">FaceBook</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 156, Column 342: reference to entity "sa" for which no system identifier could be generated
    …dlHU1uTySww8e6yelCKGUj6nStOpxDLs%3D&sa=3b86a54&opt=3">FaceBook</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 156, Column 206: entity was defined here
    …3ZcwKTiknUIG3AH6%2FP1rbSLteRg4UMFqA%3D&sa=3b86a54&opt=3">MySpace</a> | <a href…
  • Warning Line 156, Column 354: reference not terminated by REFC delimiter
    …e6yelCKGUj6nStOpxDLs%3D&sa=3b86a54&opt=3">FaceBook</a> | <a href="http://www.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 156, Column 354: reference to external entity in attribute value
    …e6yelCKGUj6nStOpxDLs%3D&sa=3b86a54&opt=3">FaceBook</a> | <a href="http://www.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 156, Column 354: reference to entity "opt" for which no system identifier could be generated
    …e6yelCKGUj6nStOpxDLs%3D&sa=3b86a54&opt=3">FaceBook</a> | <a href="http://www.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 156, Column 217: entity was defined here
    …G3AH6%2FP1rbSLteRg4UMFqA%3D&sa=3b86a54&opt=3">MySpace</a> | <a href="http://ww…
  • Warning Line 156, Column 476: reference not terminated by REFC delimiter
    …3sUAn%2F55q8TsWbtjbJx7nB9mNmuSfUu5uZjWc0hDsc%3D&sa=3b86a54&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 156, Column 476: reference to external entity in attribute value
    …3sUAn%2F55q8TsWbtjbJx7nB9mNmuSfUu5uZjWc0hDsc%3D&sa=3b86a54&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 156, Column 476: reference to entity "sa" for which no system identifier could be generated
    …3sUAn%2F55q8TsWbtjbJx7nB9mNmuSfUu5uZjWc0hDsc%3D&sa=3b86a54&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 156, Column 206: entity was defined here
    …3ZcwKTiknUIG3AH6%2FP1rbSLteRg4UMFqA%3D&sa=3b86a54&opt=3">MySpace</a> | <a href…
  • Warning Line 156, Column 488: reference not terminated by REFC delimiter
    …3sUAn%2F55q8TsWbtjbJx7nB9mNmuSfUu5uZjWc0hDsc%3D&sa=3b86a54&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 156, Column 488: reference to external entity in attribute value
    …3sUAn%2F55q8TsWbtjbJx7nB9mNmuSfUu5uZjWc0hDsc%3D&sa=3b86a54&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 156, Column 488: reference to entity "opt" for which no system identifier could be generated
    …3sUAn%2F55q8TsWbtjbJx7nB9mNmuSfUu5uZjWc0hDsc%3D&sa=3b86a54&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 156, Column 217: entity was defined here
    …G3AH6%2FP1rbSLteRg4UMFqA%3D&sa=3b86a54&opt=3">MySpace</a> | <a href="http://ww…
  • Warning Line 157, Column 102: reference not terminated by REFC delimiter
    …BHcXMsM4enbSQRBetW44DMAo05rTZnzk%3D&sa=3b86a54&opt=3">Bebo</a>| <a href="http:…

    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 157, Column 102: reference to external entity in attribute value
    …BHcXMsM4enbSQRBetW44DMAo05rTZnzk%3D&sa=3b86a54&opt=3">Bebo</a>| <a href="http:…

    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 157, Column 102: reference to entity "sa" for which no system identifier could be generated
    …BHcXMsM4enbSQRBetW44DMAo05rTZnzk%3D&sa=3b86a54&opt=3">Bebo</a>| <a href="http:…

    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 156, Column 206: entity was defined here
    …3ZcwKTiknUIG3AH6%2FP1rbSLteRg4UMFqA%3D&sa=3b86a54&opt=3">MySpace</a> | <a href…
  • Warning Line 157, Column 114: reference not terminated by REFC delimiter
    …QRBetW44DMAo05rTZnzk%3D&sa=3b86a54&opt=3">Bebo</a>| <a href="http://www.allunb…

    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 157, Column 114: reference to external entity in attribute value
    …QRBetW44DMAo05rTZnzk%3D&sa=3b86a54&opt=3">Bebo</a>| <a href="http://www.allunb…

    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 157, Column 114: reference to entity "opt" for which no system identifier could be generated
    …QRBetW44DMAo05rTZnzk%3D&sa=3b86a54&opt=3">Bebo</a>| <a href="http://www.allunb…

    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 156, Column 217: entity was defined here
    …G3AH6%2FP1rbSLteRg4UMFqA%3D&sa=3b86a54&opt=3">MySpace</a> | <a href="http://ww…
  • Warning Line 157, Column 231: reference not terminated by REFC delimiter
    …qBU8wmOnvObVHE51HOhSiI9HcO%2BO80jyix9wn0M%3D&sa=3b86a54&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 157, Column 231: reference to external entity in attribute value
    …qBU8wmOnvObVHE51HOhSiI9HcO%2BO80jyix9wn0M%3D&sa=3b86a54&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 157, Column 231: reference to entity "sa" for which no system identifier could be generated
    …qBU8wmOnvObVHE51HOhSiI9HcO%2BO80jyix9wn0M%3D&sa=3b86a54&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 156, Column 206: entity was defined here
    …3ZcwKTiknUIG3AH6%2FP1rbSLteRg4UMFqA%3D&sa=3b86a54&opt=3">MySpace</a> | <a href…
  • Warning Line 157, Column 243: reference not terminated by REFC delimiter
    …qBU8wmOnvObVHE51HOhSiI9HcO%2BO80jyix9wn0M%3D&sa=3b86a54&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 157, Column 243: reference to external entity in attribute value
    …qBU8wmOnvObVHE51HOhSiI9HcO%2BO80jyix9wn0M%3D&sa=3b86a54&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 157, Column 243: reference to entity "opt" for which no system identifier could be generated
    …qBU8wmOnvObVHE51HOhSiI9HcO%2BO80jyix9wn0M%3D&sa=3b86a54&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 156, Column 217: entity was defined here
    …G3AH6%2FP1rbSLteRg4UMFqA%3D&sa=3b86a54&opt=3">MySpace</a> | <a href="http://ww…

Visitor Analysis

Daily Visitor
  • 5.017 visits