fragman, fragman izle, dizi fragmanları sitemiz üzerinden dizi ve film fragmanlarına, kullanıcı yorumlarına ulaşabilirsiniz. | fragmanlar.org ...

fragmanlar.org
  • Domain Name
    fragmanlar.org
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #67651
  • Page Size
    49.7 KB
  • Ip Address
    185.12.109.98
  • Heading
    H1: 1, H2: 4, H3: 4, H4: 3, H5: 0, H6: 3
  • Images
    0 GIF, 27 JPG, 21 PNG

Website Meta Analysis

  • Title
    fragmanlar.org | fragman, fragman izle, film ve dizi fragmanları
  • Meta Keyword
    fragman, fragmanlar, fragman izle, dizi fragmanları, film fragmanları
  • Meta Description
    fragman, fragman izle, dizi fragmanları sitemiz üzerinden dizi ve film fragmanlarına, kullanıcı yorumlarına ulaşabilirsiniz. | fragmanlar.org

Technical Analysis

  • Webserver
  • Ip Address
    185.12.109.98
  • Domain Age
  • Javascript Library
    jquery, yui
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from fragmanlar.org.

HTML Analysis

  • content-encoding: gzip
  • vary: Accept-Encoding
  • date: Tue, 27 Aug 2013 17:19:05 GMT
  • connection: close
  • x-powered-by: PHP/5.2.17
  • x-pingback: http://www.fragmanlar.org/xmlrpc.php
  • content-type: text/html; charset=UTF-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for fragmanlar.org

DNS Analysis


DNS servers
ns1.hosturka.com [185.12.109.93]
ns2.hosturka.com [185.12.109.94]


DNS Records

Answer records
fragmanlar.org TXT v=spf1 ip4:77.223.154.162 ip4:77.223.154.134 a mx include:websitewelcome.com ~all 14400s
fragmanlar.org MX
preference: 0
exchange: fragmanlar.org
14400s
fragmanlar.org SOA
server: ns1.hosturka.com
email: aykantoprak@gmail.com
serial: 2012121001
refresh: 86400
retry: 7200
expire: 3600000
minimum ttl: 86400
86400s
fragmanlar.org NS  ns1.hosturka.com 86400s
fragmanlar.org NS  ns2.hosturka.com 86400s
fragmanlar.org A 185.12.109.98 14400s

Authority records

Additional records
fragmanlar.org A 185.12.109.98 14400s
ns1.hosturka.com A 185.12.109.93 14400s
ns2.hosturka.com A 185.12.109.94 14400s

IP 185.12.109.98 Analysis

  • Country Code
    EU
  • Country Code3
    EU
  • Country Name
    Europe
  • City
    EU
  • Continent Code
    47° North
  • Latitude
    8.
  • Longitude
  • No whois ip data for 185.12.109.98

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 37 Errors
  • 1 Warnings
Ratio Text/Html
  • 0.6118611094735601
Message Error
  • Error Line 2, Column 1: Missing xmlns attribute for element html. The value should be: http://www.w3.org/1999/xhtml
    <html>

    Many Document Types based on XML need a mandatory xmlns attribute on the root element. For example, the root element for XHTML might look like:
    <html xmlns="http://www.w3.org/1999/xhtml">

  • Error Line 4, Column 15: there is no attribute "charset"
    <meta charset="UTF-8" />

    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 24: required attribute "content" not specified
    <meta charset="UTF-8" />

    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 9, Column 126: end tag for "link" omitted, but OMITTAG NO was specified
    …/www.fragmanlar.org/wp-content/themes/fevk-fragman-plus/gorseller/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 9, Column 1: start tag was here
    <link rel="icon" type="image/png" href="http://www.fragmanlar.org/wp-content/th…
  • Error Line 64, Column 8: required attribute "type" not specified
    <script>(function(d, s, id) {

    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 71, Column 38: document type does not allow element "html" here
    <html xmlns:fb="http://ogp.me/ns/fb#">

    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 71, Column 1: Missing xmlns attribute for element html. The value should be: http://www.w3.org/1999/xhtml
    <html xmlns:fb="http://ogp.me/ns/fb#">

    Many Document Types based on XML need a mandatory xmlns attribute on the root element. For example, the root element for XHTML might look like:
    <html xmlns="http://www.w3.org/1999/xhtml">

  • Error Line 74, Column 32: document type does not allow element "div" here
    	<div class="fragmanlar-baslik">

    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 78, Column 58: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …"><a href="http://www.fragmanlar.org/"><img style="vertical-align:middle" src=…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 94, Column 24: document type does not allow element "div" here
    <div class="ortalayici">		<div class="guncel-fragmanlar">

    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 96, Column 92: there is no attribute "data-show-count"
    …witter-follow-button" data-show-count="false" data-lang="tr" data-show-screen-…

    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 96, Column 110: there is no attribute "data-lang"
    …on" data-show-count="false" data-lang="tr" data-show-screen-name="false">Takip…

    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 96, Column 137: there is no attribute "data-show-screen-name"
    …="false" data-lang="tr" data-show-screen-name="false">Takip et: @fragmanlar</a>

    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 97, Column 8: required attribute "type" not specified
    <script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0];if(!d.getElem…

    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 11: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    								<p>Dila Hanım 24.Bölüm Fragmanı konusu sitemize eklenmiştir. Kaliteli f…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 125, Column 11: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    								<p>İntikam 9.Bölüm Fragmanı konusu sitemize eklenmiştir. Kaliteli forma…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 137, Column 11: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    								<p>Muhteşem Yüzyıl 89.Bölüm Fragmanı konusu sitemize eklenmiştir. Kalit…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 150, Column 11: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    								<p>Benim İçin Üzülme 18.Bölüm Fragmanı konusu sitemize eklenmiştir. Kal…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 447, Column 28: document type does not allow element "div" here
    			<div id="fragman-altlik">

    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 490, Column 15: there is no attribute "href"
    <fb:like href="http://www.facebook.com/fragmanlar.org" send="false" width="325"…

    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 490, Column 61: there is no attribute "send"
    …www.facebook.com/fragmanlar.org" send="false" width="325" height="30" show_fac…

    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 490, Column 75: there is no attribute "width"
    …om/fragmanlar.org" send="false" width="325" height="30" show_faces="false" fon…

    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 490, Column 88: there is no attribute "height"
    ….org" send="false" width="325" height="30" show_faces="false" font="verdana"><…

    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 490, Column 104: there is no attribute "show_faces"
    …d="false" width="325" height="30" show_faces="false" font="verdana"></fb:like>	

    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 490, Column 117: there is no attribute "font"
    …d="false" width="325" height="30" show_faces="false" font="verdana"></fb:like>	

    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 490, Column 126: element "fb:like" undefined
    …d="false" width="325" height="30" show_faces="false" font="verdana"></fb:like>	

    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 494, Column 121: there is no attribute "data-size"
    …a-show-count="false" data-lang="tr" data-size="large">Takip et: @fragmanlar</a>

    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 495, Column 8: required attribute "type" not specified
    <script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0];if(!d.getElem…

    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 500, Column 40: there is no attribute "data-annotation"
    <div class="g-plusone" data-annotation="inline" data-width="200"></div>

    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 500, Column 60: there is no attribute "data-width"
    <div class="g-plusone" data-annotation="inline" data-width="200"></div>

    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 523, Column 53: cannot generate system identifier for general entity "ikon"
    <img src="http://www.iyisayfa.net/inc.php?site=7498&ikon=1" border="0"></a>

    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 523, Column 53: general entity "ikon" not defined and no default entity
    <img src="http://www.iyisayfa.net/inc.php?site=7498&ikon=1" border="0"></a>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 523, Column 57: reference not terminated by REFC delimiter
    <img src="http://www.iyisayfa.net/inc.php?site=7498&ikon=1" border="0"></a>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 523, Column 57: reference to external entity in attribute value
    <img src="http://www.iyisayfa.net/inc.php?site=7498&ikon=1" border="0"></a>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 523, Column 57: reference to entity "ikon" for which no system identifier could be generated
    <img src="http://www.iyisayfa.net/inc.php?site=7498&ikon=1" border="0"></a>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 523, Column 52: entity was defined here
    <img src="http://www.iyisayfa.net/inc.php?site=7498&ikon=1" border="0"></a>
  • Error Line 523, Column 71: required attribute "alt" not specified
    <img src="http://www.iyisayfa.net/inc.php?site=7498&ikon=1" border="0"></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 523, Column 75: end tag for "img" omitted, but OMITTAG NO was specified
    <img src="http://www.iyisayfa.net/inc.php?site=7498&ikon=1" border="0"></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 523, Column 1: start tag was here
    <img src="http://www.iyisayfa.net/inc.php?site=7498&ikon=1" border="0"></a>
  • Error Line 540, Column 150: document type does not allow element "script" here; assuming missing "head" start-tag
    …/contact-form-7/includes/js/jquery.form.min.js?ver=3.25.0-2013.01.18'></script>
  • Error Line 547, Column 7: "head" not finished but containing element ended
    </body>
  • Error Line 547, Column 7: end tag for "head" omitted, but OMITTAG NO was specified
    </body>

    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 540, Column 1: start tag was here
    <script type='text/javascript' src='http://www.fragmanlar.org/wp-content/plugin…
  • Error Line 547, Column 7: "html" not finished but containing element ended
    </body>
  • Error Line 547, Column 7: end tag for "html" omitted, but OMITTAG NO was specified
    </body>

    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 71, Column 1: start tag was here
    <html xmlns:fb="http://ogp.me/ns/fb#">

Visitor Analysis

Daily Visitor
  • 2.450 visits