sceper.ws

Your source for all Scene and P2P Movies, TV Shows, Games, Magazines, Music and more! ...

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

Overview Info

  • Domain Name
    sceper.ws
  • Favicon
  • Alexa Rank
    #12184
  • Google Page Rank
    PR 3
  • Ip Address
    109.163.231.41
  • Page Size
    72.6 KB
  • Images
    0 GIF, 21 JPG, 6 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 10 4 7 0 0

Website Meta Analysis



  • Title
    Sceper | For your daily Scene and P2P releases
  • Meta Keyword
    scene,p2p,movies,release,games,tv,warez,shows,rlslog,rlslog alternative,rlslog down,oneddl,rlslog.net,alternative,oneddl alternative,hotfile,fileserve,filesonic,wupload,rapidshare,files,torrent
  • Meta Description
    Your source for all Scene and P2P Movies, TV Shows, Games, Magazines, Music and more!

Technical Analysis



  • Webserver
    hi
  • Ip Address
    109.163.231.41
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from sceper.ws.

HTML Analysis

  • x-pingback: http://sceper.ws/xmlrpc.php
  • content-type: text/html; charset=UTF-8
  • server: hi
  • content-length: 70667
  • accept-ranges: bytes
  • date: Tue, 09 Jul 2013 19:32:55 GMT
  • x-varnish: 443853869 443852998
  • age: 5
  • via: 1.1 varnish
  • connection: keep-alive
  • x-google-cache-control: remote-fetch


Welcome to the .WS Whois Server

Use of this service for any purpose other
than determining the availability of a domain
in the .WS TLD to be registered is strictly
prohibited.

Domain Name: SCEPER.WS

Registrant Name: Use registrar whois listed below
Registrant Email: Use registrar whois listed below

Administrative Contact Email: Use registrar whois listed below
Administrative Contact Telephone: Use registrar whois listed below

Registrar Name: eNom
Registrar Email: email
Registrar Telephone: 425-974-4500
Registrar Whois: whois.enom.com

Domain Created: 2012-01-26
Domain Last Updated: 2012-12-27
Domain Currently Expires: 2014-01-26

Current Nameservers:

dns1.registrar-servers.com
dns2.registrar-servers.com
dns3.registrar-servers.com
dns4.registrar-servers.com
dns5.registrar-servers.com


IP 109.163.231.41 Analysis

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

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 25 Errors
  • 21 Warnings
Ratio Text/Html
  • 0.7422848225576453
Message Error
  • Error Line 4, Column 11: there is no attribute "REL"
    <LINK REL="SHORTCUT ICON" HREF="http://sceper.ws/favicon.ico" />

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 4, Column 32: there is no attribute "HREF"
    <LINK REL="SHORTCUT ICON" HREF="http://sceper.ws/favicon.ico" />

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 4, Column 64: element "LINK" undefined
    <LINK REL="SHORTCUT ICON" HREF="http://sceper.ws/favicon.ico" />

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 66, Column 92: end tag for element "a" which is not open
    …"http://static.sceper.ws/images/SceneRLSv4/logo.png" alt="Logo" id="logo"/></a>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 233, Column 97: required attribute "alt" not specified
    …="_blank"><img src="http://static.sceper.ws/images/SceneRLSv4/rssicon.png"></a>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 233, Column 101: end tag for "img" omitted, but OMITTAG NO was specified
    …="_blank"><img src="http://static.sceper.ws/images/SceneRLSv4/rssicon.png"></a>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 233, Column 33: start tag was here
    <a href="/feed" target="_blank"><img src="http://static.sceper.ws/images/SceneR…
  • Error Line 237, Column 195: there is no attribute "allowTransparency"
    …rameborder="0" width="91" height="16" allowTransparency="true"></iframe></span>

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 311, Column 17: there is no attribute "TYPE"
    			<SCRIPT TYPE="text/javascript" SRC="http://ad.adorika.com/st?ad_type=ad&ad_s…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 311, Column 39: there is no attribute "SRC"
    			<SCRIPT TYPE="text/javascript" SRC="http://ad.adorika.com/st?ad_type=ad&ad_s…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Warning Line 311, Column 76: cannot generate system identifier for general entity "ad_size"
    …="http://ad.adorika.com/st?ad_type=ad&ad_size=728x90&section=3646943&pub_url=s…

    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 311, Column 76: general entity "ad_size" not defined and no default entity
    …="http://ad.adorika.com/st?ad_type=ad&ad_size=728x90&section=3646943&pub_url=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.

  • Warning Line 311, Column 83: reference not terminated by REFC delimiter
    …//ad.adorika.com/st?ad_type=ad&ad_size=728x90&section=3646943&pub_url=sceper.m…

    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 311, Column 83: reference to external entity in attribute value
    …//ad.adorika.com/st?ad_type=ad&ad_size=728x90&section=3646943&pub_url=sceper.m…

    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 311, Column 83: reference to entity "ad_size" for which no system identifier could be generated
    …//ad.adorika.com/st?ad_type=ad&ad_size=728x90&section=3646943&pub_url=sceper.m…

    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 311, Column 75: entity was defined here
    …C="http://ad.adorika.com/st?ad_type=ad&ad_size=728x90&section=3646943&pub_url=…
  • Warning Line 311, Column 91: cannot generate system identifier for general entity "section"
    …rika.com/st?ad_type=ad&ad_size=728x90&section=3646943&pub_url=sceper.me"></SCR…

    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 311, Column 91: general entity "section" not defined and no default entity
    …rika.com/st?ad_type=ad&ad_size=728x90&section=3646943&pub_url=sceper.me"></SCR…

    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 311, Column 98: reference not terminated by REFC delimiter
    …a.com/st?ad_type=ad&ad_size=728x90&section=3646943&pub_url=sceper.me"></SCRIPT>

    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 311, Column 98: reference to external entity in attribute value
    …a.com/st?ad_type=ad&ad_size=728x90&section=3646943&pub_url=sceper.me"></SCRIPT>

    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 311, Column 98: reference to entity "section" for which no system identifier could be generated
    …a.com/st?ad_type=ad&ad_size=728x90&section=3646943&pub_url=sceper.me"></SCRIPT>

    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 311, Column 90: entity was defined here
    …orika.com/st?ad_type=ad&ad_size=728x90&section=3646943&pub_url=sceper.me"></SC…
  • Warning Line 311, Column 107: cannot generate system identifier for general entity "pub_url"
    …a.com/st?ad_type=ad&ad_size=728x90&section=3646943&pub_url=sceper.me"></SCRIPT>

    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 311, Column 107: general entity "pub_url" not defined and no default entity
    …a.com/st?ad_type=ad&ad_size=728x90&section=3646943&pub_url=sceper.me"></SCRIPT>

    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 311, Column 114: reference not terminated by REFC delimiter
    …a.com/st?ad_type=ad&ad_size=728x90&section=3646943&pub_url=sceper.me"></SCRIPT>

    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 311, Column 114: reference to external entity in attribute value
    …a.com/st?ad_type=ad&ad_size=728x90&section=3646943&pub_url=sceper.me"></SCRIPT>

    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 311, Column 114: reference to entity "pub_url" for which no system identifier could be generated
    …a.com/st?ad_type=ad&ad_size=728x90&section=3646943&pub_url=sceper.me"></SCRIPT>

    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 311, Column 106: entity was defined here
    …a.com/st?ad_type=ad&ad_size=728x90&section=3646943&pub_url=sceper.me"></SCRIPT>
  • Error Line 311, Column 125: element "SCRIPT" undefined
    …a.com/st?ad_type=ad&ad_size=728x90&section=3646943&pub_url=sceper.me"></SCRIPT>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 638, Column 80: reference not terminated by REFC delimiter
    …//ad.adorika.com/st?ad_type=ad&ad_size=300x250&section=3646943&pub_url=sceper.…

    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 638, Column 80: reference to external entity in attribute value
    …//ad.adorika.com/st?ad_type=ad&ad_size=300x250&section=3646943&pub_url=sceper.…

    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 638, Column 80: reference to entity "ad_size" for which no system identifier could be generated
    …//ad.adorika.com/st?ad_type=ad&ad_size=300x250&section=3646943&pub_url=sceper.…

    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 311, Column 75: entity was defined here
    …C="http://ad.adorika.com/st?ad_type=ad&ad_size=728x90&section=3646943&pub_url=…
  • Warning Line 638, Column 96: reference not terminated by REFC delimiter
    ….com/st?ad_type=ad&ad_size=300x250&section=3646943&pub_url=sceper.me"></SCRIPT>

    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 638, Column 96: reference to external entity in attribute value
    ….com/st?ad_type=ad&ad_size=300x250&section=3646943&pub_url=sceper.me"></SCRIPT>

    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 638, Column 96: reference to entity "section" for which no system identifier could be generated
    ….com/st?ad_type=ad&ad_size=300x250&section=3646943&pub_url=sceper.me"></SCRIPT>

    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 311, Column 90: entity was defined here
    …orika.com/st?ad_type=ad&ad_size=728x90&section=3646943&pub_url=sceper.me"></SC…
  • Warning Line 638, Column 112: reference not terminated by REFC delimiter
    ….com/st?ad_type=ad&ad_size=300x250&section=3646943&pub_url=sceper.me"></SCRIPT>

    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 638, Column 112: reference to external entity in attribute value
    ….com/st?ad_type=ad&ad_size=300x250&section=3646943&pub_url=sceper.me"></SCRIPT>

    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 638, Column 112: reference to entity "pub_url" for which no system identifier could be generated
    ….com/st?ad_type=ad&ad_size=300x250&section=3646943&pub_url=sceper.me"></SCRIPT>

    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 311, Column 106: entity was defined here
    …a.com/st?ad_type=ad&ad_size=728x90&section=3646943&pub_url=sceper.me"></SCRIPT>
  • Error Line 638, Column 123: element "SCRIPT" undefined
    ….com/st?ad_type=ad&ad_size=300x250&section=3646943&pub_url=sceper.me"></SCRIPT>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 737, Column 80: reference not terminated by REFC delimiter
    …//ad.adorika.com/st?ad_type=ad&ad_size=160x600&section=3646943&pub_url=sceper.…

    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 737, Column 80: reference to external entity in attribute value
    …//ad.adorika.com/st?ad_type=ad&ad_size=160x600&section=3646943&pub_url=sceper.…

    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 737, Column 80: reference to entity "ad_size" for which no system identifier could be generated
    …//ad.adorika.com/st?ad_type=ad&ad_size=160x600&section=3646943&pub_url=sceper.…

    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 311, Column 75: entity was defined here
    …C="http://ad.adorika.com/st?ad_type=ad&ad_size=728x90&section=3646943&pub_url=…
  • Warning Line 737, Column 96: reference not terminated by REFC delimiter
    ….com/st?ad_type=ad&ad_size=160x600&section=3646943&pub_url=sceper.me"></SCRIPT>

    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 737, Column 96: reference to external entity in attribute value
    ….com/st?ad_type=ad&ad_size=160x600&section=3646943&pub_url=sceper.me"></SCRIPT>

    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 737, Column 96: reference to entity "section" for which no system identifier could be generated
    ….com/st?ad_type=ad&ad_size=160x600&section=3646943&pub_url=sceper.me"></SCRIPT>

    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 311, Column 90: entity was defined here
    …orika.com/st?ad_type=ad&ad_size=728x90&section=3646943&pub_url=sceper.me"></SC…
  • Warning Line 737, Column 112: reference not terminated by REFC delimiter
    ….com/st?ad_type=ad&ad_size=160x600&section=3646943&pub_url=sceper.me"></SCRIPT>

    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 737, Column 112: reference to external entity in attribute value
    ….com/st?ad_type=ad&ad_size=160x600&section=3646943&pub_url=sceper.me"></SCRIPT>

    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 737, Column 112: reference to entity "pub_url" for which no system identifier could be generated
    ….com/st?ad_type=ad&ad_size=160x600&section=3646943&pub_url=sceper.me"></SCRIPT>

    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 311, Column 106: entity was defined here
    …a.com/st?ad_type=ad&ad_size=728x90&section=3646943&pub_url=sceper.me"></SCRIPT>
  • Error Line 737, Column 123: element "SCRIPT" undefined
    ….com/st?ad_type=ad&ad_size=160x600&section=3646943&pub_url=sceper.me"></SCRIPT>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 795, Column 58: end tag for element "a" which is not open
    …>© 2006-2013 <a href="" />Sceper.ws</a><br>This server doesn't host any files.…

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 795, Column 63: end tag for "br" omitted, but OMITTAG NO was specified
    …06-2013 <a href="" />Sceper.ws</a><br>This server doesn't host any files. This…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 795, Column 59: start tag was here
    …© 2006-2013 <a href="" />Sceper.ws</a><br>This server doesn't host any files. …

Visitor Analysis

Daily Visitor
  • 11.783 visits

In Page Analysis