Free Scat Tube Video Sharing Community. Upload scat shitting pooping for free. Best Porn Tube. Scat shitting poo kaviar free extreme fetish tube scat tube kaviar tube kacke kacken coprophilia ...

scatrina.com
  • Domain Name
    scatrina.com
  • Favicon
  • Google Page Rank
    0
  • Alexa Rank
    #45958
  • Page Size
    27.5 KB
  • Ip Address
    95.211.228.30
  • Heading
    H1: 0, H2: 1, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    1 GIF, 10 JPG, 1 PNG

Website Meta Analysis

  • Title
    Scatrina.Com - Scat tube shitting poo kaviar free extreme fetish tube - scat tube full of shit and pooping
  • Meta Keyword
    scat tube shitting shit poo pooping kaviar extreme bizarre piss pee vomit brazil german puke gag free tube video sharing community amateur coprophilia tube kacke kacken
  • Meta Description
    Free Scat Tube Video Sharing Community. Upload scat shitting pooping for free. Best Porn Tube. Scat shitting poo kaviar free extreme fetish tube scat tube kaviar tube kacke kacken coprophilia

Technical Analysis

  • Webserver
    nginx/1.0.15
  • Ip Address
    95.211.228.30
  • Domain Age
    2 Years, 2 Months, 20 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: nginx/1.0.15
  • date: Wed, 26 Jun 2013 22:54:17 GMT
  • content-type: text/html; charset=UTF-8
  • connection: keep-alive
  • x-powered-by: PHP/5.3.3
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for scatrina.com

DNS Analysis


DNS servers
ns1.scatrina.com [62.141.42.206]
ns2.scatrina.com [5.104.108.46]


DNS Records

Answer records
scatrina.com A 62.141.42.206 14400s
scatrina.com MX
preference: 0
exchange: scatrina.com
14400s
scatrina.com SOA
server: b206.blue.fastwebserver.de
email: support@scatrina.com
serial: 2012071101
refresh: 86400
retry: 7200
expire: 3600000
minimum ttl: 86400
0s
scatrina.com NS  ns1.scatrina.com 86400s
scatrina.com NS  ns2.scatrina.com 86400s

Authority records

Additional records
ns1.scatrina.com A 62.141.42.206 14400s
ns2.scatrina.com A 5.104.108.46 14400s

IP 95.211.228.30 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 78 Errors
  • 19 Warnings
Ratio Text/Html
  • 0.552907700515739
Message Error
  • Error Line 8, Column 66: end tag for "link" omitted, but OMITTAG NO was specified
    <link rel="shortcut icon" href="http://scatrina.com/favicon.ico">

    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 8, Column 1: start tag was here
    <link rel="shortcut icon" href="http://scatrina.com/favicon.ico">
  • Error Line 40, Column 8: required attribute "type" not specified
    <script>

    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 111, Column 8: required attribute "type" not specified
    <script>

    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>.

  • Warning Line 236, Column 25: character "&" is the first character of a delimiter but occurred as data
    	} else if(window.opera && window.print) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 236, Column 26: character "&" is the first character of a delimiter but occurred as data
    	} else if(window.opera && window.print) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 264, Column 159: end tag for "img" omitted, but OMITTAG NO was specified
    …ee extreme fetish tube - scat tube full of shit and pooping"  class="logo"></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 263, Column 35: start tag was here
        <a href="http://scatrina.com"><img src="http://scatrina.com/styles/cbv2new/…
  • Error Line 269, Column 74: end tag for "img" omitted, but OMITTAG NO was specified
     src="http://www.scatrina.com/banners/bee52/banner_psg_468_60_01.jpg"></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 266, Column 65: start tag was here
    <a href="https://www.inet-cash.com/click/21445" target="_blank"><img
  • Error Line 353, Column 14: ID "container" already defined
        <div id="container" class="container clearfix" >

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 257, Column 10: ID "container" first defined here
    <div id="container" class="container clearfix">
  • Error Line 394, Column 13: end tag for "br" omitted, but OMITTAG NO was specified
            <br>

    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 394, Column 9: start tag was here
            <br>
  • Error Line 396, Column 16: there is no attribute "border"
    <iframe border=0 frameborder=0 marginheight=0 marginwidth=0 width=476 height=68…

    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 396, Column 16: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe border=0 frameborder=0 marginheight=0 marginwidth=0 width=476 height=68…
  • Error Line 396, Column 30: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe border=0 frameborder=0 marginheight=0 marginwidth=0 width=476 height=68…
  • Error Line 396, Column 45: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …e border=0 frameborder=0 marginheight=0 marginwidth=0 width=476 height=68 scro…
  • Error Line 396, Column 59: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …meborder=0 marginheight=0 marginwidth=0 width=476 height=68 scrolling=no allow…
  • Error Line 396, Column 67: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=0 marginheight=0 marginwidth=0 width=476 height=68 scrolling=no allowtranspar…
  • Error Line 396, Column 78: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ight=0 marginwidth=0 width=476 height=68 scrolling=no allowtransparency=true s…
  • Error Line 396, Column 91: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …width=0 width=476 height=68 scrolling=no allowtransparency=true src=http://ads…
  • Error Line 396, Column 112: there is no attribute "allowtransparency"
    …ght=68 scrolling=no allowtransparency=true src=http://adserver.juicyads.com/ad…

    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 396, Column 112: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ght=68 scrolling=no allowtransparency=true src=http://adserver.juicyads.com/ad…
  • Error Line 396, Column 121: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rolling=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?…
  • Error Line 396, Column 127: NET-enabling start-tag not immediately followed by null end-tag
    …g=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?adzone…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 396, Column 183: end tag for element "iframe" which is not open
    …arency=true src=http://adserver.juicyads.com/adshow.php?adzone=113900></iframe>

    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 400, Column 67: ID "watched" already defined
    …ted"><a href="javascript:void(0)" id="watched" onclick="getAjaxPhoto('last_vie…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 376, Column 67: ID "watched" first defined here
    …ted"><a href="javascript:void(0)" id="watched" onclick="get_video('recent_view…
  • Error Line 401, Column 50: ID "most_watched" already defined
    … <li><a href="javascript:void(0)" id="most_watched" onclick="getAjaxPhoto('mos…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 377, Column 50: ID "most_watched" first defined here
    … <li><a href="javascript:void(0)" id="most_watched" onclick="get_video('most_v…
  • Error Line 402, Column 50: ID "recently_watched" already defined
    … <li><a href="javascript:void(0)" id="recently_watched" onclick="getAjaxPhoto(…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 378, Column 50: ID "recently_watched" first defined here
    … <li><a href="javascript:void(0)" id="recently_watched" onclick="get_video('re…
  • Error Line 403, Column 50: ID "recently_watched" already defined
    … <li><a href="javascript:void(0)" id="recently_watched" onclick="getAjaxPhoto(…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 378, Column 50: ID "recently_watched" first defined here
    … <li><a href="javascript:void(0)" id="recently_watched" onclick="get_video('re…
  • Error Line 423, Column 6: end tag for "br" omitted, but OMITTAG NO was specified
    	<br>

    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 423, Column 2: start tag was here
    	<br>
  • Error Line 425, Column 16: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe border=0 frameborder=0 marginheight=0 marginwidth=0 width=308 height=25…
  • Error Line 425, Column 30: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe border=0 frameborder=0 marginheight=0 marginwidth=0 width=308 height=25…
  • Error Line 425, Column 45: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …e border=0 frameborder=0 marginheight=0 marginwidth=0 width=308 height=258 scr…
  • Error Line 425, Column 59: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …meborder=0 marginheight=0 marginwidth=0 width=308 height=258 scrolling=no allo…
  • Error Line 425, Column 67: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=0 marginheight=0 marginwidth=0 width=308 height=258 scrolling=no allowtranspa…
  • Error Line 425, Column 78: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ight=0 marginwidth=0 width=308 height=258 scrolling=no allowtransparency=true …
  • Error Line 425, Column 92: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …idth=0 width=308 height=258 scrolling=no allowtransparency=true src=http://ads…
  • Error Line 425, Column 113: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ht=258 scrolling=no allowtransparency=true src=http://adserver.juicyads.com/ad…
  • Error Line 425, Column 122: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rolling=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?…
  • Error Line 425, Column 128: NET-enabling start-tag not immediately followed by null end-tag
    …g=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?adzone…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 425, Column 184: end tag for element "iframe" which is not open
    …arency=true src=http://adserver.juicyads.com/adshow.php?adzone=113838></iframe>

    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 427, Column 9: end tag for "br" omitted, but OMITTAG NO was specified
        <br>

    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 427, Column 5: start tag was here
        <br>
  • Error Line 429, Column 16: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe border=0 frameborder=0 marginheight=0 marginwidth=0 width=308 height=25…
  • Error Line 429, Column 30: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe border=0 frameborder=0 marginheight=0 marginwidth=0 width=308 height=25…
  • Error Line 429, Column 45: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …e border=0 frameborder=0 marginheight=0 marginwidth=0 width=308 height=258 scr…
  • Error Line 429, Column 59: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …meborder=0 marginheight=0 marginwidth=0 width=308 height=258 scrolling=no allo…
  • Error Line 429, Column 67: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=0 marginheight=0 marginwidth=0 width=308 height=258 scrolling=no allowtranspa…
  • Error Line 429, Column 78: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ight=0 marginwidth=0 width=308 height=258 scrolling=no allowtransparency=true …
  • Error Line 429, Column 92: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …idth=0 width=308 height=258 scrolling=no allowtransparency=true src=http://ads…
  • Error Line 429, Column 113: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ht=258 scrolling=no allowtransparency=true src=http://adserver.juicyads.com/ad…
  • Error Line 429, Column 122: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rolling=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?…
  • Error Line 429, Column 128: NET-enabling start-tag not immediately followed by null end-tag
    …g=no allowtransparency=true src=http://adserver.juicyads.com/adshow.php?adzone…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 429, Column 184: end tag for element "iframe" which is not open
    …arency=true src=http://adserver.juicyads.com/adshow.php?adzone=122128></iframe>

    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 431, Column 9: end tag for "br" omitted, but OMITTAG NO was specified
        <br>

    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 431, Column 5: start tag was here
        <br>
  • Warning Line 432, Column 104: cannot generate system identifier for general entity "type"
    …/bongacash.com/tools/promo.php?c=2381&type=banner&size=300x250&name=bongacams_…

    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 432, Column 104: general entity "type" not defined and no default entity
    …/bongacash.com/tools/promo.php?c=2381&type=banner&size=300x250&name=bongacams_…

    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 432, Column 108: reference not terminated by REFC delimiter
    …gacash.com/tools/promo.php?c=2381&type=banner&size=300x250&name=bongacams_bang…

    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 432, Column 108: reference to external entity in attribute value
    …gacash.com/tools/promo.php?c=2381&type=banner&size=300x250&name=bongacams_bang…

    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 432, Column 108: reference to entity "type" for which no system identifier could be generated
    …gacash.com/tools/promo.php?c=2381&type=banner&size=300x250&name=bongacams_bang…

    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 432, Column 103: entity was defined here
    …//bongacash.com/tools/promo.php?c=2381&type=banner&size=300x250&name=bongacams…
  • Warning Line 432, Column 116: cannot generate system identifier for general entity "size"
    …om/tools/promo.php?c=2381&type=banner&size=300x250&name=bongacams_bangascreen"…

    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 432, Column 116: general entity "size" not defined and no default entity
    …om/tools/promo.php?c=2381&type=banner&size=300x250&name=bongacams_bangascreen"…

    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 432, Column 120: reference not terminated by REFC delimiter
    …ools/promo.php?c=2381&type=banner&size=300x250&name=bongacams_bangascreen" mar…

    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 432, Column 120: reference to external entity in attribute value
    …ools/promo.php?c=2381&type=banner&size=300x250&name=bongacams_bangascreen" mar…

    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 432, Column 120: reference to entity "size" for which no system identifier could be generated
    …ools/promo.php?c=2381&type=banner&size=300x250&name=bongacams_bangascreen" mar…

    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 432, Column 115: entity was defined here
    …com/tools/promo.php?c=2381&type=banner&size=300x250&name=bongacams_bangascreen…
  • Warning Line 432, Column 129: cannot generate system identifier for general entity "name"
    …o.php?c=2381&type=banner&size=300x250&name=bongacams_bangascreen" marginwidth=…

    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 432, Column 129: general entity "name" not defined and no default entity
    …o.php?c=2381&type=banner&size=300x250&name=bongacams_bangascreen" marginwidth=…

    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 432, Column 133: reference not terminated by REFC delimiter
    …p?c=2381&type=banner&size=300x250&name=bongacams_bangascreen" marginwidth="0" …

    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 432, Column 133: reference to external entity in attribute value
    …p?c=2381&type=banner&size=300x250&name=bongacams_bangascreen" marginwidth="0" …

    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 432, Column 133: reference to entity "name" for which no system identifier could be generated
    …p?c=2381&type=banner&size=300x250&name=bongacams_bangascreen" marginwidth="0" …

    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 432, Column 128: entity was defined here
    …mo.php?c=2381&type=banner&size=300x250&name=bongacams_bangascreen" marginwidth…
  • Error Line 448, Column 200: required attribute "alt" not specified
    …-small.png" width="30" height="30" border="0" class="vsmall_thumb" /></a></div>

    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 455, Column 197: required attribute "alt" not specified
    …-small.jpg" width="30" height="30" border="0" class="vsmall_thumb" /></a></div>

    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 462, Column 198: required attribute "alt" not specified
    …-small.JPG" width="30" height="30" border="0" class="vsmall_thumb" /></a></div>

    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 469, Column 196: required attribute "alt" not specified
    …-small.jpg" width="30" height="30" border="0" class="vsmall_thumb" /></a></div>

    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 476, Column 198: required attribute "alt" not specified
    …-small.jpg" width="30" height="30" border="0" class="vsmall_thumb" /></a></div>

    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 483, Column 201: required attribute "alt" not specified
    …-small.JPG" width="30" height="30" border="0" class="vsmall_thumb" /></a></div>

    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 490, Column 196: required attribute "alt" not specified
    …-small.jpg" width="30" height="30" border="0" class="vsmall_thumb" /></a></div>

    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 497, Column 203: required attribute "alt" not specified
    …-small.jpg" width="30" height="30" border="0" class="vsmall_thumb" /></a></div>

    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 504, Column 199: required attribute "alt" not specified
    …-small.jpg" width="30" height="30" border="0" class="vsmall_thumb" /></a></div>

    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 511, Column 202: required attribute "alt" not specified
    …-small.png" width="30" height="30" border="0" class="vsmall_thumb" /></a></div>

    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>.

  • Warning Line 551, Column 9: S separator in comment declaration
        <!-- div align="center"></div>

    This may happen if you have consecutive comments but did not close one of them properly. The proper syntax for comments is <!-- my comment -->.

  • Error Line 551, Column 10: invalid comment declaration: found name start character outside comment but inside comment declaration
        <!-- div align="center"></div>
  • Info Line 549, Column 5: comment declaration started here
        <!-- div class="footer_sp"></div>
  • Error Line 570, Column 30: end tag for "img" omitted, but OMITTAG NO was specified
    alt="tumblr site counter"></a></div></noscript>

    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 568, Column 17: start tag was here
    target="_blank"><img class="statcounter"
  • Error Line 586, Column 6: end tag for element "div" which is not open
    </div>

    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.

Visitor Analysis

Daily Visitor
  • 2.567 visits
Daily Visitor