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

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

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.110.81.90
  • Domain Age
    3 Years, 5 Months, 27 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Fri, 09 Aug 2013 05:09:07 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.110.81.90 Analysis

  • Country Code
  • Country Code3
  • Country Name
  • City
  • Continent Code
  • Latitude
  • Longitude
  • No whois ip data for 208.110.81.90

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 5 Errors
  • 22 Warnings
Ratio Text/Html
  • 0.595622852780252
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 155, Column 209: cannot generate system identifier for general entity "sa"
    …bMFLEyAJsMYZ2V%2FSblRVOjNVpx845sow%3D&sa=32f85e31&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 155, Column 209: general entity "sa" not defined and no default entity
    …bMFLEyAJsMYZ2V%2FSblRVOjNVpx845sow%3D&sa=32f85e31&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 155, Column 211: reference not terminated by REFC delimiter
    …FLEyAJsMYZ2V%2FSblRVOjNVpx845sow%3D&sa=32f85e31&opt=3">MySpace</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 155, Column 211: reference to external entity in attribute value
    …FLEyAJsMYZ2V%2FSblRVOjNVpx845sow%3D&sa=32f85e31&opt=3">MySpace</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 155, Column 211: reference to entity "sa" for which no system identifier could be generated
    …FLEyAJsMYZ2V%2FSblRVOjNVpx845sow%3D&sa=32f85e31&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.

  • Info Line 155, Column 208: entity was defined here
    …FbMFLEyAJsMYZ2V%2FSblRVOjNVpx845sow%3D&sa=32f85e31&opt=3">MySpace</a> | <a hre…
  • Warning Line 155, Column 221: cannot generate system identifier for general entity "opt"
    …2V%2FSblRVOjNVpx845sow%3D&sa=32f85e31&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 155, Column 221: general entity "opt" not defined and no default entity
    …2V%2FSblRVOjNVpx845sow%3D&sa=32f85e31&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 155, Column 224: reference not terminated by REFC delimiter
    …2FSblRVOjNVpx845sow%3D&sa=32f85e31&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 155, Column 224: reference to external entity in attribute value
    …2FSblRVOjNVpx845sow%3D&sa=32f85e31&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 155, Column 224: reference to entity "opt" for which no system identifier could be generated
    …2FSblRVOjNVpx845sow%3D&sa=32f85e31&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 155, Column 220: entity was defined here
    …Z2V%2FSblRVOjNVpx845sow%3D&sa=32f85e31&opt=3">MySpace</a> | <a href="http://ww…
  • Warning Line 155, Column 349: reference not terminated by REFC delimiter
    …Y318j551idwxQTejDe%2BBaRz45A%2FE%3D&sa=32f85e31&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 155, Column 349: reference to external entity in attribute value
    …Y318j551idwxQTejDe%2BBaRz45A%2FE%3D&sa=32f85e31&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 155, Column 349: reference to entity "sa" for which no system identifier could be generated
    …Y318j551idwxQTejDe%2BBaRz45A%2FE%3D&sa=32f85e31&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 155, Column 208: entity was defined here
    …FbMFLEyAJsMYZ2V%2FSblRVOjNVpx845sow%3D&sa=32f85e31&opt=3">MySpace</a> | <a hre…
  • Warning Line 155, Column 362: reference not terminated by REFC delimiter
    …TejDe%2BBaRz45A%2FE%3D&sa=32f85e31&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 155, Column 362: reference to external entity in attribute value
    …TejDe%2BBaRz45A%2FE%3D&sa=32f85e31&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 155, Column 362: reference to entity "opt" for which no system identifier could be generated
    …TejDe%2BBaRz45A%2FE%3D&sa=32f85e31&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 155, Column 220: entity was defined here
    …Z2V%2FSblRVOjNVpx845sow%3D&sa=32f85e31&opt=3">MySpace</a> | <a href="http://ww…
  • Warning Line 155, Column 482: reference not terminated by REFC delimiter
    …ld7MzDWazfdVmoD8UCGNvF2Z2YiEuVL8ALMOUHAyHIQ%3D&sa=32f85e31&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 155, Column 482: reference to external entity in attribute value
    …ld7MzDWazfdVmoD8UCGNvF2Z2YiEuVL8ALMOUHAyHIQ%3D&sa=32f85e31&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 155, Column 482: reference to entity "sa" for which no system identifier could be generated
    …ld7MzDWazfdVmoD8UCGNvF2Z2YiEuVL8ALMOUHAyHIQ%3D&sa=32f85e31&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 155, Column 208: entity was defined here
    …FbMFLEyAJsMYZ2V%2FSblRVOjNVpx845sow%3D&sa=32f85e31&opt=3">MySpace</a> | <a hre…
  • Warning Line 155, Column 495: reference not terminated by REFC delimiter
    …ld7MzDWazfdVmoD8UCGNvF2Z2YiEuVL8ALMOUHAyHIQ%3D&sa=32f85e31&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 155, Column 495: reference to external entity in attribute value
    …ld7MzDWazfdVmoD8UCGNvF2Z2YiEuVL8ALMOUHAyHIQ%3D&sa=32f85e31&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 155, Column 495: reference to entity "opt" for which no system identifier could be generated
    …ld7MzDWazfdVmoD8UCGNvF2Z2YiEuVL8ALMOUHAyHIQ%3D&sa=32f85e31&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 155, Column 220: entity was defined here
    …Z2V%2FSblRVOjNVpx845sow%3D&sa=32f85e31&opt=3">MySpace</a> | <a href="http://ww…
  • Warning Line 156, Column 102: reference not terminated by REFC delimiter
    …hgYmnVAACzwCawbmatoy1b4juLikcE68%3D&sa=32f85e31&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 156, Column 102: reference to external entity in attribute value
    …hgYmnVAACzwCawbmatoy1b4juLikcE68%3D&sa=32f85e31&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 156, Column 102: reference to entity "sa" for which no system identifier could be generated
    …hgYmnVAACzwCawbmatoy1b4juLikcE68%3D&sa=32f85e31&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 155, Column 208: entity was defined here
    …FbMFLEyAJsMYZ2V%2FSblRVOjNVpx845sow%3D&sa=32f85e31&opt=3">MySpace</a> | <a hre…
  • Warning Line 156, Column 115: reference not terminated by REFC delimiter
    …wbmatoy1b4juLikcE68%3D&sa=32f85e31&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 156, Column 115: reference to external entity in attribute value
    …wbmatoy1b4juLikcE68%3D&sa=32f85e31&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 156, Column 115: reference to entity "opt" for which no system identifier could be generated
    …wbmatoy1b4juLikcE68%3D&sa=32f85e31&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 155, Column 220: entity was defined here
    …Z2V%2FSblRVOjNVpx845sow%3D&sa=32f85e31&opt=3">MySpace</a> | <a href="http://ww…
  • Warning Line 156, Column 234: reference not terminated by REFC delimiter
    …%2Bln1IS%2FAq4efvV6wN4qUORB5wrZT5UDV0sVM%3D&sa=32f85e31&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 156, Column 234: reference to external entity in attribute value
    …%2Bln1IS%2FAq4efvV6wN4qUORB5wrZT5UDV0sVM%3D&sa=32f85e31&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 156, Column 234: reference to entity "sa" for which no system identifier could be generated
    …%2Bln1IS%2FAq4efvV6wN4qUORB5wrZT5UDV0sVM%3D&sa=32f85e31&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 155, Column 208: entity was defined here
    …FbMFLEyAJsMYZ2V%2FSblRVOjNVpx845sow%3D&sa=32f85e31&opt=3">MySpace</a> | <a hre…
  • Warning Line 156, Column 247: reference not terminated by REFC delimiter
    …%2Bln1IS%2FAq4efvV6wN4qUORB5wrZT5UDV0sVM%3D&sa=32f85e31&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 156, Column 247: reference to external entity in attribute value
    …%2Bln1IS%2FAq4efvV6wN4qUORB5wrZT5UDV0sVM%3D&sa=32f85e31&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 156, Column 247: reference to entity "opt" for which no system identifier could be generated
    …%2Bln1IS%2FAq4efvV6wN4qUORB5wrZT5UDV0sVM%3D&sa=32f85e31&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 155, Column 220: entity was defined here
    …Z2V%2FSblRVOjNVpx845sow%3D&sa=32f85e31&opt=3">MySpace</a> | <a href="http://ww…

Visitor Analysis

Daily Visitor
  • 3.033 visits