Türkiyenin en kapsamlı blog sitesi. Resimler, şarkı çevirileri, taban puanları, mesajlar ve ansiklopedik bilgiler ...

nkfu.com
  • Domain Name
    nkfu.com
  • Favicon
  • Google Page Rank
    1
  • Alexa Rank
    #66116
  • Page Size
    91.4 KB
  • Ip Address
    62.212.76.3
  • Heading
    H1: 1, H2: 17, H3: 7, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 4 JPG, 0 PNG

Website Meta Analysis

  • Title
    EN Kapsamlı Blog Sitesi
  • Meta Keyword
    şarkı çevirileri, taban puanları, resimli, mesajlar, nedir, resimler,ile ilgili, hakkında, kimdir, ne demek,
  • Meta Description
    Türkiyenin en kapsamlı blog sitesi. Resimler, şarkı çevirileri, taban puanları, mesajlar ve ansiklopedik bilgiler

Technical Analysis

  • Webserver
    nginx/1.0.4
  • Ip Address
    62.212.76.3
  • Domain Age
    6 Years, 6 Months, 3 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: nginx/1.0.4
  • date: Tue, 12 Mar 2013 20:52:32 GMT
  • content-type: text/html; charset=UTF-8
  • connection: keep-alive
  • x-powered-by: PHP/5.2.17
  • x-cf-powered-by: WP 1.3.9
  • x-pingback: http://www.nkfu.com/xmlrpc.php
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for nkfu.com

DNS Analysis


DNS servers
gurur.nkfu.com [62.212.76.3]
ugur.nkfu.com [62.212.76.6]


DNS Records

Answer records
nkfu.com SOA
server: ugur.nkfu.com
email: destek@nfku.com
serial: 2011062206
refresh: 86400
retry: 7200
expire: 3600000
minimum ttl: 86400
86400s
nkfu.com NS  ugur.nkfu.com 86400s
nkfu.com NS  gurur.nkfu.com 86400s
nkfu.com A 62.212.76.3 14400s
nkfu.com MX
preference: 0
exchange: nkfu.com
14400s

Authority records

Additional records
ugur.nkfu.com A 62.212.76.6 14400s
gurur.nkfu.com A 62.212.76.3 14400s

IP 62.212.76.3 Analysis

  • Country Code
    NL
  • Country Code3
    NLD
  • Country Name
    Netherlands
  • City
    Amsterdam
  • Continent Code
    EU
  • Latitude
    52.35
  • Longitude
    4.9167
  • No whois ip data for 62.212.76.3

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 46 Errors
  • 20 Warnings
Ratio Text/Html
  • 0.8013460819400673
Message Error
  • Error Line 108, Column 10: 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 113, Column 53: required attribute "type" not specified
    <script src="http://static.linkz.net/linkz/linkz.js"></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 306, Column 5: document type does not allow element "tr" here; assuming missing "table" start-tag
    	<tr><td colspan="2" width="1000"><div align="justify">
  • Error Line 307, Column 17: there is no attribute "height"
      <table height="27" border="0" cellspacing="0" bordercolor="#FF6600" class="br…

    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 307, Column 61: there is no attribute "bordercolor"
    …ble height="27" border="0" cellspacing="0" bordercolor="#FF6600" class="brovz">

    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 309, Column 35: there is no attribute "bordercolor"
         <td width="203"  bordercolor="#000000"><div align="center"><a class="style…

    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 342, Column 36: document type does not allow element "div" here
    	<div id="breadcrumb" class="clear">

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 346, Column 30: document type does not allow element "div" here
    	<div id="main" class="clear"><style type="text/css">

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 346, Column 53: document type does not allow element "style" here
    	<div id="main" class="clear"><style type="text/css">

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Warning Line 874, Column 96: reference not terminated by REFC delimiter
    … src="http://www.google.com.tr/cse/brand?form=cse-search-box&lang=tr"></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.

  • Error Line 876, Column 5: 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 876, Column 1: start tag was here
    <br>
  • Error Line 898, Column 18: document type does not allow element "th" here; assuming missing "tr" start-tag
      <th scope="row"><strong><a href="http://www.nkfu.com/dgs-kontenjanlari-ve-tab…
  • Error Line 903, Column 5: 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 903, Column 1: start tag was here
    <br>
  • Error Line 916, Column 14: end tag for "br" omitted, but OMITTAG NO was specified
    </script><br><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 916, Column 10: start tag was here
    </script><br><br>
  • Error Line 916, Column 18: end tag for "br" omitted, but OMITTAG NO was specified
    </script><br><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 916, Column 14: start tag was here
    </script><br><br>
  • Error Line 918, Column 23: document type does not allow element "style" here
    <style type="text/css">

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 928, Column 5: 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 928, Column 1: start tag was here
    <br>
  • Error Line 932, Column 89: required attribute "alt" not specified
    …142" scope="row"><img src="http://www.nkfu.com/resimler/atasozleri.jpg" /></th>

    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 933, Column 155: required attribute "alt" not specified
    …p://www.nkfu.com/resimler/birim-cevirici.jpg" width="142" height="81"></a></td>

    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 933, Column 159: end tag for "img" omitted, but OMITTAG NO was specified
    …p://www.nkfu.com/resimler/birim-cevirici.jpg" width="142" height="81"></a></td>

    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 933, Column 73: start tag was here
    …//www.nkfu.com/birimcevir/index.html"><img src="http://www.nkfu.com/resimler/b…
  • Error Line 948, Column 319: end tag for "strong" omitted, but OMITTAG NO was specified
    …//www.nkfu.com/atasozleri-ve-anlamlari-sozlugu-z-harfi"></a></font></span></th>

    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 936, Column 59: start tag was here
    …0099" class="stil1 stil2" scope="row"><strong><span class="stil2"><font color=…
  • Error Line 952, Column 5: 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 952, Column 1: start tag was here
    <br> 
  • Error Line 956, Column 173: required attribute "alt" not specified
    …://www.nkfu.com/resimler/periyodik-tablo.jpg" width="142" height="81"></a></th>

    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 956, Column 177: end tag for "img" omitted, but OMITTAG NO was specified
    …://www.nkfu.com/resimler/periyodik-tablo.jpg" width="142" height="81"></a></th>

    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 956, Column 90: start tag was here
    …riyodik-cetvel/periyodik-cetvel.html"><img src="http://www.nkfu.com/resimler/p…
  • Error Line 957, Column 158: required attribute "alt" not specified
    ….com/resimler/belirli-gunler-ve-haftalar.jpg" width="142" height="81"></a></td>

    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 957, Column 162: end tag for "img" omitted, but OMITTAG NO was specified
    ….com/resimler/belirli-gunler-ve-haftalar.jpg" width="142" height="81"></a></td>

    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 957, Column 64: start tag was here
    …ww.nkfu.com/belirli-gun-ve-haftalar/"><img src="http://www.nkfu.com/resimler/b…
  • Error Line 964, Column 5: 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 964, Column 1: start tag was here
    <br>
  • Error Line 976, Column 14: end tag for "br" omitted, but OMITTAG NO was specified
    </script><br><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 976, Column 10: start tag was here
    </script><br><br>
  • Error Line 976, Column 18: end tag for "br" omitted, but OMITTAG NO was specified
    </script><br><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 976, Column 14: start tag was here
    </script><br><br>
  • Error Line 978, Column 5: 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 978, Column 1: start tag was here
    <br>
  • Warning Line 979, Column 126: cannot generate system identifier for general entity "width"
    ….com%2Fpages%2FNKFU%2F185483961505722&width=300&colorscheme=light&show_faces=t…

    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 979, Column 126: general entity "width" not defined and no default entity
    ….com%2Fpages%2FNKFU%2F185483961505722&width=300&colorscheme=light&show_faces=t…

    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 979, Column 131: reference not terminated by REFC delimiter
    …2Fpages%2FNKFU%2F185483961505722&width=300&colorscheme=light&show_faces=true&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 979, Column 131: reference to external entity in attribute value
    …2Fpages%2FNKFU%2F185483961505722&width=300&colorscheme=light&show_faces=true&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 979, Column 131: reference to entity "width" for which no system identifier could be generated
    …2Fpages%2FNKFU%2F185483961505722&width=300&colorscheme=light&show_faces=true&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 979, Column 125: entity was defined here
    …k.com%2Fpages%2FNKFU%2F185483961505722&width=300&colorscheme=light&show_faces=…
  • Warning Line 979, Column 136: cannot generate system identifier for general entity "colorscheme"
    …es%2FNKFU%2F185483961505722&width=300&colorscheme=light&show_faces=true&stream…

    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 979, Column 136: general entity "colorscheme" not defined and no default entity
    …es%2FNKFU%2F185483961505722&width=300&colorscheme=light&show_faces=true&stream…

    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 979, Column 147: reference not terminated by REFC delimiter
    …F185483961505722&width=300&colorscheme=light&show_faces=true&stream=false&head…

    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 979, Column 147: reference to external entity in attribute value
    …F185483961505722&width=300&colorscheme=light&show_faces=true&stream=false&head…

    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 979, Column 147: reference to entity "colorscheme" for which no system identifier could be generated
    …F185483961505722&width=300&colorscheme=light&show_faces=true&stream=false&head…

    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 979, Column 135: entity was defined here
    …ges%2FNKFU%2F185483961505722&width=300&colorscheme=light&show_faces=true&strea…
  • Warning Line 979, Column 154: cannot generate system identifier for general entity "show_faces"
    …961505722&width=300&colorscheme=light&show_faces=true&stream=false&header=fals…

    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 979, Column 154: general entity "show_faces" not defined and no default entity
    …961505722&width=300&colorscheme=light&show_faces=true&stream=false&header=fals…

    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 979, Column 164: reference not terminated by REFC delimiter
    …width=300&colorscheme=light&show_faces=true&stream=false&header=false&height=2…

    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 979, Column 164: reference to external entity in attribute value
    …width=300&colorscheme=light&show_faces=true&stream=false&header=false&height=2…

    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 979, Column 164: reference to entity "show_faces" for which no system identifier could be generated
    …width=300&colorscheme=light&show_faces=true&stream=false&header=false&height=2…

    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 979, Column 153: entity was defined here
    …3961505722&width=300&colorscheme=light&show_faces=true&stream=false&header=fal…
  • Warning Line 979, Column 170: cannot generate system identifier for general entity "stream"
    …300&colorscheme=light&show_faces=true&stream=false&header=false&height=255" sc…

    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 979, Column 170: general entity "stream" not defined and no default entity
    …300&colorscheme=light&show_faces=true&stream=false&header=false&height=255" 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.

  • Warning Line 979, Column 176: reference not terminated by REFC delimiter
    …lorscheme=light&show_faces=true&stream=false&header=false&height=255" scrollin…

    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 979, Column 176: reference to external entity in attribute value
    …lorscheme=light&show_faces=true&stream=false&header=false&height=255" scrollin…

    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 979, Column 176: reference to entity "stream" for which no system identifier could be generated
    …lorscheme=light&show_faces=true&stream=false&header=false&height=255" scrollin…

    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 979, Column 169: entity was defined here
    …=300&colorscheme=light&show_faces=true&stream=false&header=false&height=255" s…
  • Warning Line 979, Column 183: cannot generate system identifier for general entity "header"
    …eme=light&show_faces=true&stream=false&header=false&height=255" scrolling="no" 

    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 979, Column 183: general entity "header" not defined and no default entity
    …eme=light&show_faces=true&stream=false&header=false&height=255" scrolling="no" 

    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 979, Column 189: reference not terminated by REFC delimiter
    …eme=light&show_faces=true&stream=false&header=false&height=255" scrolling="no" 

    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 979, Column 189: reference to external entity in attribute value
    …eme=light&show_faces=true&stream=false&header=false&height=255" scrolling="no" 

    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 979, Column 189: reference to entity "header" for which no system identifier could be generated
    …eme=light&show_faces=true&stream=false&header=false&height=255" scrolling="no" 

    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 979, Column 182: entity was defined here
    …eme=light&show_faces=true&stream=false&header=false&height=255" scrolling="no"…
  • Warning Line 979, Column 196: cannot generate system identifier for general entity "height"
    …eme=light&show_faces=true&stream=false&header=false&height=255" scrolling="no" 

    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 979, Column 196: general entity "height" not defined and no default entity
    …eme=light&show_faces=true&stream=false&header=false&height=255" scrolling="no" 

    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 979, Column 202: reference not terminated by REFC delimiter
    …eme=light&show_faces=true&stream=false&header=false&height=255" scrolling="no" 

    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 979, Column 202: reference to external entity in attribute value
    …eme=light&show_faces=true&stream=false&header=false&height=255" scrolling="no" 

    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 979, Column 202: reference to entity "height" for which no system identifier could be generated
    …eme=light&show_faces=true&stream=false&header=false&height=255" scrolling="no" 

    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 979, Column 195: entity was defined here
    …eme=light&show_faces=true&stream=false&header=false&height=255" scrolling="no" 
  • Error Line 987, Column 18: document type does not allow element "div" here
    	<div id="footer">

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Warning Line 1201, Column 111: character "&" is the first character of a delimiter but occurred as data
    …tp://sstatic1.histats.com/0.gif?409991&101" alt="free html hit counter" border…

    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 1201, Column 159: end tag for "img" omitted, but OMITTAG NO was specified
    …ts.com/0.gif?409991&101" alt="free html hit counter" border="0"></a></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 1201, Column 60: start tag was here
    …tp://www.histats.com" target="_blank"><img  src="http://sstatic1.histats.com/0…
  • Error Line 1218, Column 6: end tag for "table" omitted, but OMITTAG NO was specified
    </div> <!--end #wrapper -->

    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 306, Column 2: start tag was here
    	<tr><td colspan="2" width="1000"><div align="justify">

Visitor Analysis

Daily Visitor
  • 3.500 visits
Daily Visitor