schooltunnel.net

School Tunnel is a free service that enables you to unblock access to any website such as Facebook and YouTube. Use our service at school or wherever there is a fliter/firewall in your ...

Display Widget for this domain on your website. Click Here
This data was last updated from 10-05-2013 03:40:30  (update).

Overview Info

  • Domain Name
    schooltunnel.net
  • Favicon
  • Alexa Rank
    #447703
  • Google Page Rank
    PR 2
  • Ip Address
    208.53.158.137
  • Page Size
    7.8 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
    School Tunnnel | Unblock Facebook at School | Access YouTube
  • Meta Keyword
    unblock, tunnel, youtube, facebook, school
  • Meta Description
    School Tunnel is a free service that enables you to unblock access to any website such as Facebook and YouTube. Use our service at school or wherever there is a fliter/firewall in your way.

Technical Analysis



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

Hyper Text Transfer Protocol (HTTP) header show data header response from schooltunnel.net.

HTML Analysis

  • date: Fri, 10 May 2013 15:40:26 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 schooltunnel.net

DNS 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
schooltunnel.net NS  ns3.dneasy.net 172800s
schooltunnel.net SOA
server: ns1.dneasy.net
email: unbannernetwork@gmail.com
serial: 2013013000
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 38400
172800s
schooltunnel.net NS  ns1.dneasy.net 172800s
schooltunnel.net NS  ns2.dneasy.net 172800s
schooltunnel.net NS  ns4.dneasy.net 172800s
schooltunnel.net A 208.53.158.137 3600s

Authority records

Additional records
ns3.dneasy.net A 106.187.48.223 172800s
ns1.dneasy.net A 50.31.1.17 172800s
ns4.dneasy.net A 69.85.93.117 172800s
ns2.dneasy.net 28 [16 bytes] 172800s
ns2.dneasy.net A 95.211.165.80 172800s
ns1.dneasy.net 28 [16 bytes] 172800s
ns4.dneasy.net 28 [16 bytes] 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: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
  • 17 Errors
  • 22 Warnings
Ratio Text/Html
  • 0.6051154086088584
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 205: cannot generate system identifier for general entity "sa"
    …dLqbTOJwjOfAn40T1ygjloLWSydNjdvZiU%3D&sa=56c369088b1&opt=3">MySpace</a> | <a h…

    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 205: general entity "sa" not defined and no default entity
    …dLqbTOJwjOfAn40T1ygjloLWSydNjdvZiU%3D&sa=56c369088b1&opt=3">MySpace</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.

  • Warning Line 156, Column 207: reference not terminated by REFC delimiter
    …qbTOJwjOfAn40T1ygjloLWSydNjdvZiU%3D&sa=56c369088b1&opt=3">MySpace</a> | <a hre…

    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 207: reference to external entity in attribute value
    …qbTOJwjOfAn40T1ygjloLWSydNjdvZiU%3D&sa=56c369088b1&opt=3">MySpace</a> | <a hre…

    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 207: reference to entity "sa" for which no system identifier could be generated
    …qbTOJwjOfAn40T1ygjloLWSydNjdvZiU%3D&sa=56c369088b1&opt=3">MySpace</a> | <a hre…

    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 204: entity was defined here
    …XdLqbTOJwjOfAn40T1ygjloLWSydNjdvZiU%3D&sa=56c369088b1&opt=3">MySpace</a> | <a …
  • Warning Line 156, Column 220: cannot generate system identifier for general entity "opt"
    …T1ygjloLWSydNjdvZiU%3D&sa=56c369088b1&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 220: general entity "opt" not defined and no default entity
    …T1ygjloLWSydNjdvZiU%3D&sa=56c369088b1&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 223: reference not terminated by REFC delimiter
    …gjloLWSydNjdvZiU%3D&sa=56c369088b1&opt=3">MySpace</a> | <a href="http://www.sc…

    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 223: reference to external entity in attribute value
    …gjloLWSydNjdvZiU%3D&sa=56c369088b1&opt=3">MySpace</a> | <a href="http://www.sc…

    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 223: reference to entity "opt" for which no system identifier could be generated
    …gjloLWSydNjdvZiU%3D&sa=56c369088b1&opt=3">MySpace</a> | <a href="http://www.sc…

    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 219: entity was defined here
    …0T1ygjloLWSydNjdvZiU%3D&sa=56c369088b1&opt=3">MySpace</a> | <a href="http://ww…
  • Warning Line 156, Column 346: reference not terminated by REFC delimiter
    …KJ4AyvIHvg7G7PaPiTa3j%2F7uz5yQPI%3D&sa=56c369088b1&opt=3">FaceBook</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 156, Column 346: reference to external entity in attribute value
    …KJ4AyvIHvg7G7PaPiTa3j%2F7uz5yQPI%3D&sa=56c369088b1&opt=3">FaceBook</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 156, Column 346: reference to entity "sa" for which no system identifier could be generated
    …KJ4AyvIHvg7G7PaPiTa3j%2F7uz5yQPI%3D&sa=56c369088b1&opt=3">FaceBook</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 156, Column 204: entity was defined here
    …XdLqbTOJwjOfAn40T1ygjloLWSydNjdvZiU%3D&sa=56c369088b1&opt=3">MySpace</a> | <a …
  • Warning Line 156, Column 362: reference not terminated by REFC delimiter
    …iTa3j%2F7uz5yQPI%3D&sa=56c369088b1&opt=3">FaceBook</a> | <a href="http://www.s…

    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 362: reference to external entity in attribute value
    …iTa3j%2F7uz5yQPI%3D&sa=56c369088b1&opt=3">FaceBook</a> | <a href="http://www.s…

    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 362: reference to entity "opt" for which no system identifier could be generated
    …iTa3j%2F7uz5yQPI%3D&sa=56c369088b1&opt=3">FaceBook</a> | <a href="http://www.s…

    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 219: entity was defined here
    …0T1ygjloLWSydNjdvZiU%3D&sa=56c369088b1&opt=3">MySpace</a> | <a href="http://ww…
  • Warning Line 156, Column 482: reference not terminated by REFC delimiter
    …9yPLNLgdlMa0DaMilRmUOh479ha8Iaxrd1hrw1U0%3D&sa=56c369088b1&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 482: reference to external entity in attribute value
    …9yPLNLgdlMa0DaMilRmUOh479ha8Iaxrd1hrw1U0%3D&sa=56c369088b1&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 482: reference to entity "sa" for which no system identifier could be generated
    …9yPLNLgdlMa0DaMilRmUOh479ha8Iaxrd1hrw1U0%3D&sa=56c369088b1&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 204: entity was defined here
    …XdLqbTOJwjOfAn40T1ygjloLWSydNjdvZiU%3D&sa=56c369088b1&opt=3">MySpace</a> | <a …
  • Warning Line 156, Column 498: reference not terminated by REFC delimiter
    …9yPLNLgdlMa0DaMilRmUOh479ha8Iaxrd1hrw1U0%3D&sa=56c369088b1&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 498: reference to external entity in attribute value
    …9yPLNLgdlMa0DaMilRmUOh479ha8Iaxrd1hrw1U0%3D&sa=56c369088b1&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 498: reference to entity "opt" for which no system identifier could be generated
    …9yPLNLgdlMa0DaMilRmUOh479ha8Iaxrd1hrw1U0%3D&sa=56c369088b1&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 219: entity was defined here
    …0T1ygjloLWSydNjdvZiU%3D&sa=56c369088b1&opt=3">MySpace</a> | <a href="http://ww…
  • Warning Line 157, Column 104: reference not terminated by REFC delimiter
    …cq2yK9dTWX2TnuDDyn7RKm%2FngEJnEA%3D&sa=56c369088b1&opt=3">Bebo</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 157, Column 104: reference to external entity in attribute value
    …cq2yK9dTWX2TnuDDyn7RKm%2FngEJnEA%3D&sa=56c369088b1&opt=3">Bebo</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 157, Column 104: reference to entity "sa" for which no system identifier could be generated
    …cq2yK9dTWX2TnuDDyn7RKm%2FngEJnEA%3D&sa=56c369088b1&opt=3">Bebo</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 204: entity was defined here
    …XdLqbTOJwjOfAn40T1ygjloLWSydNjdvZiU%3D&sa=56c369088b1&opt=3">MySpace</a> | <a …
  • Warning Line 157, Column 120: reference not terminated by REFC delimiter
    …yn7RKm%2FngEJnEA%3D&sa=56c369088b1&opt=3">Bebo</a>| <a href="http://www.school…

    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 120: reference to external entity in attribute value
    …yn7RKm%2FngEJnEA%3D&sa=56c369088b1&opt=3">Bebo</a>| <a href="http://www.school…

    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 120: reference to entity "opt" for which no system identifier could be generated
    …yn7RKm%2FngEJnEA%3D&sa=56c369088b1&opt=3">Bebo</a>| <a href="http://www.school…

    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 219: entity was defined here
    …0T1ygjloLWSydNjdvZiU%3D&sa=56c369088b1&opt=3">MySpace</a> | <a href="http://ww…
  • Warning Line 157, Column 239: reference not terminated by REFC delimiter
    …IXJ9XQTbKqdnFfX6URu%2B1sk4rwwUc0o7A6A%3D&sa=56c369088b1&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 239: reference to external entity in attribute value
    …IXJ9XQTbKqdnFfX6URu%2B1sk4rwwUc0o7A6A%3D&sa=56c369088b1&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 239: reference to entity "sa" for which no system identifier could be generated
    …IXJ9XQTbKqdnFfX6URu%2B1sk4rwwUc0o7A6A%3D&sa=56c369088b1&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 204: entity was defined here
    …XdLqbTOJwjOfAn40T1ygjloLWSydNjdvZiU%3D&sa=56c369088b1&opt=3">MySpace</a> | <a …
  • Warning Line 157, Column 255: reference not terminated by REFC delimiter
    …IXJ9XQTbKqdnFfX6URu%2B1sk4rwwUc0o7A6A%3D&sa=56c369088b1&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 255: reference to external entity in attribute value
    …IXJ9XQTbKqdnFfX6URu%2B1sk4rwwUc0o7A6A%3D&sa=56c369088b1&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 255: reference to entity "opt" for which no system identifier could be generated
    …IXJ9XQTbKqdnFfX6URu%2B1sk4rwwUc0o7A6A%3D&sa=56c369088b1&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 219: entity was defined here
    …0T1ygjloLWSydNjdvZiU%3D&sa=56c369088b1&opt=3">MySpace</a> | <a href="http://ww…

Visitor Analysis

Daily Visitor
  • 210 visits
Daily Visitor