acunn.com

Yetenek Sizsiniz, Yok Böyle Dans, O ses Türkiye, Survivor Ünlüler Gönüllüler, Var Mısın Yok Musun, Süper Lig maç özetleri ve gol görüntüleri, videolar, ödüllü yarışmalar, son dakika haberleri, sinema, müzik, foto galeri, magazin ...

Display Widget for this domain on your website. Click Here
This data was last updated from 30-06-2013 09:48:25  (update).

Overview Info

  • Domain Name
    acunn.com
  • Favicon
  • Alexa Rank
    #3743
  • Google Page Rank
    PR 5
  • Ip Address
    212.58.28.164
  • Page Size
    272.2 KB
  • Images
    118 GIF, 32 JPG, 80 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 0 0 0 0 0

Website Meta Analysis



  • Title
    Acunn
  • Meta Keyword
  • Meta Description
    Yetenek Sizsiniz, Yok Böyle Dans, O ses Türkiye, Survivor Ünlüler Gönüllüler, Var Mısın Yok Musun, Süper Lig maç özetleri ve gol görüntüleri, videolar, ödüllü yarışmalar, son dakika haberleri, sinema, müzik, foto galeri, magazin ve spor dünyasıyla ilgili başka hiçbir yerde okuyamayacağınız özel ropörtajlar ile internet medyasının yeni yüzü, dizi izle, oyun, tavla, okey

Technical Analysis



  • Webserver
    Apache
  • Ip Address
    212.58.28.164
  • Domain Age
    2 Years, 6 Months, 14 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Sun, 30 Jun 2013 09:48:07 GMT
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-cache,no-store,must-revalidate,post-check=0,pre-check=0
  • connection: Keep-Alive
  • via: (c)Acunn.com
  • server: Apache
  • x-powered-by: PHP/5.3.8
  • pragma: no-cache
  • vary: Accept-Encoding
  • content-encoding: gzip
  • content-length: 33865
  • content-type: text/html; charset=utf-8
  • x-google-cache-control: remote-fetch
Domain Name: ACUNN.COM
Created on: 29-Dec-10
Expires on: 29-Dec-18
Last Updated on: 07-Aug-12

Registrant:
acunn internet ve bilisim teknolojileri a.s
karanfil araligi no 20
1.levent
istanbul, 34100
Turkey

Administrative Contact:
Ilicali, Acun email
acunn internet ve bilisim teknolojileri a.s
karanfil araligi no 20
1.levent
istanbul, 34100
Turkey
+90.2122826177 Fax -- +90.2122826177

Technical Contact:
Ilicali, Acun email
acunn internet ve bilisim teknolojileri a.s
karanfil araligi no 20
1.levent
istanbul, 34100
Turkey
+90.2122826177 Fax -- +90.2122826177

Domain servers in listed order:
NS1.WEBKONTROL.DORUK.NET.TR
NS2.WEBKONTROL.DORUK.NET.TR

DNS Analysis


DNS servers
ns1.webkontrol.doruk.net.tr
ns2.webkontrol.doruk.net.tr [212.58.3.8]

DNS Records

Answer records
acunn.com SOA
server: webkontrol.doruk.net.tr
email: root@webkontrol.doruk.net.tr
serial: 2012121402
refresh: 7200
retry: 3600
expire: 604800
minimum ttl: 3600
3600s
acunn.com MX
preference: 1
exchange: aspmx.l.google.com
600s
acunn.com MX
preference: 5
exchange: alt1.aspmx.l.google.com
600s
acunn.com MX
preference: 5
exchange: alt2.aspmx.l.google.com
600s
acunn.com MX
preference: 10
exchange: aspmx2.l.google.com
600s
acunn.com MX
preference: 10
exchange: aspmx3.l.google.com
600s
acunn.com MX
preference: 10
exchange: aspmx4.l.google.com
600s
acunn.com A 212.58.28.164 600s
acunn.com NS  ns1.webkontrol.doruk.net.tr 600s
acunn.com NS  ns2.webkontrol.doruk.net.tr 600s

Authority records

Additional records
aspmx.l.google.com A 173.194.70.26 166s
ns1.webkontrol.doruk.net.tr A 212.58.3.7 906s
ns2.webkontrol.doruk.net.tr A 212.58.3.8 918s

IP 212.58.28.164 Analysis

  • Country Code
    TR
  • Country Code3
    TUR
  • Country Name
    Turkey
  • City
    Doruk
  • Continent Code
    EU
  • Latitude
    37.7008
  • Longitude
    40.7869
  • No whois ip data for 212.58.28.164

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 248 Errors
  • 42 Warnings
Ratio Text/Html
  • 0.7631813125695217
Message Error
  • Error Line 1, Column 218: there is no attribute "prefix"
    …://www.facebook.com/2008/fbml" prefix="og: http://ogp.me/ns#"><head><!-- css -…

    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 1, Column 807: end tag for "meta" omitted, but OMITTAG NO was specified
    …equiv="content-language" content="tr"><meta property="fb:app_id" content="1943…

    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 1, Column 758: start tag was here
    …yüzü, dizi izle, oyun, tavla, okey" /><meta http-equiv="content-language" cont…
  • Error Line 1, Column 822: there is no attribute "property"
    …language" content="tr"><meta property="fb:app_id" content="194377410579075" />…

    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 9, Column 142: there is no attribute "border"
    …/news.php" style="border: 0px" border="0" scrolling="no" width="300" height="2…

    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 9, Column 185: document type does not allow element "iframe" here
    …e="border: 0px" border="0" scrolling="no" width="300" height="255"></iframe>');

    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 25, Column 1139: required attribute "type" not specified
    …jscrollpane.js?v=116"></script><script>document.write('<script src="http://run…

    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 25, Column 1212: cannot generate system identifier for general entity "preredir"
    …//run.admost.com/adx/get.ashx?k=17655&preredir={amClickThru}&r='+Math.random()…

    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 25, Column 1212: general entity "preredir" not defined and no default entity
    …//run.admost.com/adx/get.ashx?k=17655&preredir={amClickThru}&r='+Math.random()…

    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 25, Column 1220: reference not terminated by REFC delimiter
    …most.com/adx/get.ashx?k=17655&preredir={amClickThru}&r='+Math.random()+'"><\/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 25, Column 1220: reference to external entity in attribute value
    …most.com/adx/get.ashx?k=17655&preredir={amClickThru}&r='+Math.random()+'"><\/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 25, Column 1220: reference to entity "preredir" for which no system identifier could be generated
    …most.com/adx/get.ashx?k=17655&preredir={amClickThru}&r='+Math.random()+'"><\/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 25, Column 1211: entity was defined here
    …://run.admost.com/adx/get.ashx?k=17655&preredir={amClickThru}&r='+Math.random(…
  • Warning Line 25, Column 1235: cannot generate system identifier for general entity "r"
    …t.ashx?k=17655&preredir={amClickThru}&r='+Math.random()+'"><\/script>');</scri…

    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 25, Column 1235: general entity "r" not defined and no default entity
    …t.ashx?k=17655&preredir={amClickThru}&r='+Math.random()+'"><\/script>');</scri…

    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 25, Column 1236: reference not terminated by REFC delimiter
    ….ashx?k=17655&preredir={amClickThru}&r='+Math.random()+'"><\/script>');</scrip…

    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 25, Column 1236: reference to external entity in attribute value
    ….ashx?k=17655&preredir={amClickThru}&r='+Math.random()+'"><\/script>');</scrip…

    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 25, Column 1236: reference to entity "r" for which no system identifier could be generated
    ….ashx?k=17655&preredir={amClickThru}&r='+Math.random()+'"><\/script>');</scrip…

    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 25, Column 1234: entity was defined here
    …et.ashx?k=17655&preredir={amClickThru}&r='+Math.random()+'"><\/script>');</scr…
  • Error Line 25, Column 1255: required attribute "type" not specified
    …dir={amClickThru}&r='+Math.random()+'"><\/script>');</script><script src="http…

    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 25, Column 1255: document type does not allow element "script" here
    …dir={amClickThru}&r='+Math.random()+'"><\/script>');</script><script src="http…

    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 25, Column 1256: character "<" is the first character of a delimiter but occurred as data
    …ir={amClickThru}&r='+Math.random()+'"><\/script>');</script><script src="http:…

    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 25, Column 1342: reference not terminated by REFC delimiter
    …most.com/adx/get.ashx?k=17926&preredir={amClickThru}"></script></head><body><d…

    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 25, Column 1342: reference to external entity in attribute value
    …most.com/adx/get.ashx?k=17926&preredir={amClickThru}"></script></head><body><d…

    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 25, Column 1342: reference to entity "preredir" for which no system identifier could be generated
    …most.com/adx/get.ashx?k=17926&preredir={amClickThru}"></script></head><body><d…

    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 25, Column 1211: entity was defined here
    …://run.admost.com/adx/get.ashx?k=17655&preredir={amClickThru}&r='+Math.random(…
  • Error Line 25, Column 1357: required attribute "type" not specified
    …t.ashx?k=17926&preredir={amClickThru}"></script></head><body><div id="fb-root"…

    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 25, Column 1357: document type does not allow element "script" here
    …t.ashx?k=17926&preredir={amClickThru}"></script></head><body><div id="fb-root"…

    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 25, Column 1373: end tag for "script" omitted, but OMITTAG NO was specified
    …reredir={amClickThru}"></script></head><body><div id="fb-root"></div><script t…

    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 25, Column 1132: start tag was here
    …/v2/js/jscrollpane.js?v=116"></script><script>document.write('<script src="htt…
  • Warning Line 48, Column 53: character "&" is the first character of a delimiter but occurred as data
    …tor.userAgent.indexOf('iPhone') != -1 && $.cookie('SkipiPhoneCookie') != 1) { …

    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 48, Column 54: character "&" is the first character of a delimiter but occurred as data
    …or.userAgent.indexOf('iPhone') != -1 && $.cookie('SkipiPhoneCookie') != 1) { d…

    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 49, Column 115: required attribute "type" not specified
    … relative"><div class="advert"><script>document.write('<script src="http://run…

    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 49, Column 196: reference not terminated by REFC delimiter
    …most.com/adx/get.ashx?k=17651&preredir={amClickThru}&r='+Math.random()+'"><\/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 49, Column 196: reference to external entity in attribute value
    …most.com/adx/get.ashx?k=17651&preredir={amClickThru}&r='+Math.random()+'"><\/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 49, Column 196: reference to entity "preredir" for which no system identifier could be generated
    …most.com/adx/get.ashx?k=17651&preredir={amClickThru}&r='+Math.random()+'"><\/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 25, Column 1211: entity was defined here
    …://run.admost.com/adx/get.ashx?k=17655&preredir={amClickThru}&r='+Math.random(…
  • Warning Line 49, Column 212: reference not terminated by REFC delimiter
    ….ashx?k=17651&preredir={amClickThru}&r='+Math.random()+'"><\/script>');</scrip…

    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 49, Column 212: reference to external entity in attribute value
    ….ashx?k=17651&preredir={amClickThru}&r='+Math.random()+'"><\/script>');</scrip…

    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 49, Column 212: reference to entity "r" for which no system identifier could be generated
    ….ashx?k=17651&preredir={amClickThru}&r='+Math.random()+'"><\/script>');</scrip…

    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 25, Column 1234: entity was defined here
    …et.ashx?k=17655&preredir={amClickThru}&r='+Math.random()+'"><\/script>');</scr…
  • Error Line 49, Column 231: required attribute "type" not specified
    …dir={amClickThru}&r='+Math.random()+'"><\/script>');</script></div><!-- header…

    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 49, Column 231: document type does not allow element "script" here
    …dir={amClickThru}&r='+Math.random()+'"><\/script>');</script></div><!-- header…

    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 49, Column 232: character "<" is the first character of a delimiter but occurred as data
    …ir={amClickThru}&r='+Math.random()+'"><\/script>');</script></div><!-- header …

    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 49, Column 259: end tag for "script" omitted, but OMITTAG NO was specified
    …andom()+'"><\/script>');</script></div><!-- header start --><div id="header"><…

    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 49, Column 108: start tag was here
    …sition: relative"><div class="advert"><script>document.write('<script src="htt…
  • Error Line 51, Column 176: end tag for "ul" which is not finished
    …_login" style="list-style: none;"></ul></div><div class="search"><form action=…

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Error Line 57, Column 158: end tag for "br" omitted, but OMITTAG NO was specified
    …nla-gunun-sorusu">Günün Sorusu</a><br><a style="border-bottom:none !important;…

    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 57, Column 154: start tag was here
    …urkanla-gunun-sorusu">Günün Sorusu</a><br><a style="border-bottom:none !import…
  • Error Line 57, Column 258: end tag for "br" omitted, but OMITTAG NO was specified
    …nn.com/videolar/komedi">Komedi</a><br><a style="border-bottom:none !important;…

    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 57, Column 254: start tag was here
    ….acunn.com/videolar/komedi">Komedi</a><br><a style="border-bottom:none !import…
  • Error Line 57, Column 354: end tag for "br" omitted, but OMITTAG NO was specified
    ….acunn.com/videolar/spor">Spor</a><br><a style="border-bottom:none !important;…

    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 57, Column 350: start tag was here
    …/www.acunn.com/videolar/spor">Spor</a><br><a style="border-bottom:none !import…
  • Error Line 57, Column 460: end tag for "br" omitted, but OMITTAG NO was specified
    …/videolar/hayvanlar">Hayvanlar</a><br><a style="border-bottom:none !important;…

    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 57, Column 456: start tag was here
    ….com/videolar/hayvanlar">Hayvanlar</a><br><a style="border-bottom:none !import…
  • Error Line 57, Column 564: end tag for "br" omitted, but OMITTAG NO was specified
    …om/videolar/otomobil">Otomobil</a><br><a style="border-bottom:none !important;…

    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 57, Column 560: start tag was here
    …nn.com/videolar/otomobil">Otomobil</a><br><a style="border-bottom:none !import…
  • Error Line 57, Column 672: end tag for "br" omitted, but OMITTAG NO was specified
    …ideolar/film-ve-tv">Film ve TV</a><br><a style="border-bottom:none !important;…

    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 57, Column 668: start tag was here
    …om/videolar/film-ve-tv">Film ve TV</a><br><a style="border-bottom:none !import…
  • Error Line 57, Column 776: end tag for "br" omitted, but OMITTAG NO was specified
    …om/videolar/cocuklar">Çocuklar</a><br><a style="border-bottom:none !important;…

    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 57, Column 772: start tag was here
    …nn.com/videolar/cocuklar">Çocuklar</a><br><a style="border-bottom:none !import…
  • Error Line 57, Column 876: end tag for "br" omitted, but OMITTAG NO was specified
    …nn.com/videolar/insan">Magazin</a><br><a style="border-bottom:none !important;…

    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 57, Column 872: start tag was here
    ….acunn.com/videolar/insan">Magazin</a><br><a style="border-bottom:none !import…
  • Error Line 57, Column 985: end tag for "br" omitted, but OMITTAG NO was specified
    …deolar/oyunlar">Video Oyunları</a><br><a style="border-bottom:none !important;…

    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 57, Column 981: start tag was here
    …m/videolar/oyunlar">Video Oyunları</a><br><a style="border-bottom:none !import…
  • Error Line 57, Column 1087: end tag for "br" omitted, but OMITTAG NO was specified
    ….com/videolar/kadinca">Kadınca</a><br><a style="border-bottom:none !important;…

    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 57, Column 1083: start tag was here
    …cunn.com/videolar/kadinca">Kadınca</a><br><a style="border-bottom:none !import…
  • Error Line 57, Column 1211: end tag for "br" omitted, but OMITTAG NO was specified
    …-teknoloji">Bilim ve Teknoloji</a><br><a style="border-bottom:none !important;…

    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 57, Column 1207: start tag was here
    …m-ve-teknoloji">Bilim ve Teknoloji</a><br><a style="border-bottom:none !import…
  • Error Line 57, Column 1309: end tag for "br" omitted, but OMITTAG NO was specified
    …cunn.com/videolar/okul">Eğitim</a><br><a style="border-bottom:none !important;…

    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 57, Column 1305: start tag was here
    …ww.acunn.com/videolar/okul">Eğitim</a><br><a style="border-bottom:none !import…
  • Error Line 57, Column 1407: end tag for "br" omitted, but OMITTAG NO was specified
    …cunn.com/videolar/sanat">Sanat</a><br><a style="border-bottom:none !important;…

    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 57, Column 1403: start tag was here
    …ww.acunn.com/videolar/sanat">Sanat</a><br><a style="border-bottom:none !import…
  • Error Line 57, Column 1509: end tag for "br" omitted, but OMITTAG NO was specified
    ….com/videolar/seyahat">Seyahat</a><br><a style="border-bottom:none !important;…

    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 57, Column 1505: start tag was here
    …cunn.com/videolar/seyahat">Seyahat</a><br><a style="border-bottom:none !import…
  • Error Line 57, Column 1622: end tag for "br" omitted, but OMITTAG NO was specified
    …ar/televizyon">Televizyon</a><br></div></div><div class="branches pop_cat"><di…

    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 57, Column 1613: start tag was here
    …om/videolar/televizyon">Televizyon</a><br></div></div><div class="branches pop…
  • Error Line 59, Column 96: end tag for "br" omitted, but OMITTAG NO was specified
    …p://www.acunn.com/haber">Haber</a><br><a href="http://www.acunn.com/haber/maga…

    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 59, Column 92: start tag was here
    …"http://www.acunn.com/haber">Haber</a><br><a href="http://www.acunn.com/haber/…
  • Error Line 59, Column 156: end tag for "br" omitted, but OMITTAG NO was specified
    …unn.com/haber/magazin">Magazin</a><br><a href="http://www.acunn.com/spor">Spor…

    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 59, Column 152: start tag was here
    …w.acunn.com/haber/magazin">Magazin</a><br><a href="http://www.acunn.com/spor">…
  • Error Line 59, Column 204: end tag for "br" omitted, but OMITTAG NO was specified
    …ttp://www.acunn.com/spor">Spor</a><br><a href="http://www.acunn.com/sinema">Si…

    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 59, Column 200: start tag was here
    …f="http://www.acunn.com/spor">Spor</a><br><a href="http://www.acunn.com/sinema…
  • Error Line 59, Column 256: end tag for "br" omitted, but OMITTAG NO was specified
    …//www.acunn.com/sinema">Sinema</a><br><a href="http://www.acunn.com/haber/muzi…

    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 59, Column 252: start tag was here
    …ttp://www.acunn.com/sinema">Sinema</a><br><a href="http://www.acunn.com/haber/…
  • Error Line 59, Column 312: end tag for "br" omitted, but OMITTAG NO was specified
    …w.acunn.com/haber/muzik">Müzik</a><br><a href="http://www.acunn.com/galeri">Fo…

    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 59, Column 308: start tag was here
    …//www.acunn.com/haber/muzik">Müzik</a><br><a href="http://www.acunn.com/galeri…
  • Error Line 59, Column 369: end tag for "br" omitted, but OMITTAG NO was specified
    ….acunn.com/galeri">Foto Galeri</a><br><a href="http://www.acunn.com/haber/kadi…

    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 59, Column 365: start tag was here
    …/www.acunn.com/galeri">Foto Galeri</a><br><a href="http://www.acunn.com/haber/…
  • Error Line 59, Column 425: end tag for "br" omitted, but OMITTAG NO was specified
    …w.acunn.com/haber/kadin">Kadın</a><br><a href="http://www.acunn.com/haber/tekn…

    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 59, Column 421: start tag was here
    …//www.acunn.com/haber/kadin">Kadın</a><br><a href="http://www.acunn.com/haber/…
  • Error Line 59, Column 489: end tag for "br" omitted, but OMITTAG NO was specified
    …com/haber/teknoloji">Teknoloji</a><br><a href="http://www.acunn.com/saglik">Sa…

    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 59, Column 485: start tag was here
    …unn.com/haber/teknoloji">Teknoloji</a><br><a href="http://www.acunn.com/saglik…
  • Error Line 59, Column 541: end tag for "br" omitted, but OMITTAG NO was specified
    …//www.acunn.com/saglik">Sağlık</a><br><a href="http://www.acunn.com/yazarlar">…

    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 59, Column 537: start tag was here
    …ttp://www.acunn.com/saglik">Sağlık</a><br><a href="http://www.acunn.com/yazarl…
  • Error Line 59, Column 902: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …p://forum.acunn.com/"><div class="img"><img src="http://s.cdn.acunn.com/static…

    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 59, Column 996: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …//s.cdn.acunn.com/static/v3/images/forum.png" alt="" /></div><div class="text">

    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 63, Column 108: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …com/" target="_blank"><div class="img"><img src="http://s.cdn.acunn.com/static…

    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 63, Column 201: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …://s.cdn.acunn.com/static/v3/images/okey.png" alt="" /></div><div class="text">

    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 65, Column 122: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …com/" target="_blank"><div class="img"><img src="http://s.cdn.acunn.com/static…

    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 65, Column 216: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …//s.cdn.acunn.com/static/v3/images/tavla.png" alt="" /></div><div class="text">

    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 67, Column 121: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …m/top-patlatma-oyunu"><div class="img"><img src="http://s.cdn.acunn.com/static…

    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 67, Column 221: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …n.acunn.com/static/v3/images/top_patlama.png" alt="" /></div><div class="text">

    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 69, Column 214: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …w.acunn.com/iletisim"><div class="img"><img src="http://s.cdn.acunn.com/static…

    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 69, Column 311: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    ….cdn.acunn.com/static/v3/images/iletisim.png" alt="" /></div><div class="text">

    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 71, Column 5566: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …com/spor/tur-almanyaya-kaldi/61343"><p>1</p></a></li><li><a href="http://www.a…

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

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

  • Error Line 71, Column 5661: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …seviyede-bu-hatalar-olmamali/61350"><p>2</p></a></li><li><a href="http://www.a…

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

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

  • Error Line 71, Column 5760: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …rust-insallah-turu-gececegiz/61353"><p>3</p></a></li><li><a href="http://www.a…

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

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

  • Error Line 71, Column 5844: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …om/galeri/galatasaray-schalke/6075"><p>4</p></a></li><li><a href="http://www.a…

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

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

  • Error Line 71, Column 5935: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …/milan2-barcelona0-mac-ozeti/61345"><p>5</p></a></li><li><a href="http://www.a…

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

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

  • Error Line 71, Column 6027: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …/beyoglunda-catisma-3-yarali/61346"><p>6</p></a></li><li><a href="http://www.a…

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

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

  • Error Line 71, Column 6126: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …n-imrali-heyeti-karari-yarin/61339"><p>7</p></a></li><li><a href="http://www.a…

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

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

  • Error Line 71, Column 6226: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …a-gidecek-isimler-belli-oldu/61328"><p>8</p></a></li><li><a href="http://www.a…

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

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

  • Error Line 71, Column 6297: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …//www.acunn.com/makale/mustafa/806"><p>9</p></a></li><li><a href="http://www.a…

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

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

  • Error Line 71, Column 6392: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …ses-turkiye-cocuklar-elemesi/61329"><p>10</p></a></li><li><a href="http://www.…

    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 71, Column 6468: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …w.acunn.com/makale/neoldiiiiii/805"><p>11</p></a></li><li><a href="http://www.…

    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 71, Column 6555: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …/haber/eroglu-yaziklar-olsun/61330"><p>12</p></a></li><li><a href="http://www.…

    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 71, Column 6660: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …fim-yeniden-avrupada-oynamak/61340"><p>13</p></a></li><li><a href="http://www.…

    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 71, Column 6796: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …r-merak-edilenleri-yanitladi/61344"><p>14</p></a></li><li><a href="http://www.…

    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 71, Column 6876: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …unn.com/haber/psy-istanbulda/61341"><p>15</p></a></li></ul><!-- pagination end…

    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 71, Column 9744: there is no attribute "data-class"
    …<div class="img content-1" data-class="content-1" data-color="#CF18A6"><a href…

    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 71, Column 9767: there is no attribute "data-color"
    …-1" data-class="content-1" data-color="#CF18A6"><a href="http://www.acunn.com/…

    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 79, Column 9745: required attribute "type" not specified
    … adv start --><div class="adv"><script>document.write('<script src="http://run…

    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 79, Column 9826: reference not terminated by REFC delimiter
    …most.com/adx/get.ashx?k=17654&preredir={amClickThru}&r='+Math.random()+'"><\/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 79, Column 9826: reference to external entity in attribute value
    …most.com/adx/get.ashx?k=17654&preredir={amClickThru}&r='+Math.random()+'"><\/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 79, Column 9826: reference to entity "preredir" for which no system identifier could be generated
    …most.com/adx/get.ashx?k=17654&preredir={amClickThru}&r='+Math.random()+'"><\/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 25, Column 1211: entity was defined here
    …://run.admost.com/adx/get.ashx?k=17655&preredir={amClickThru}&r='+Math.random(…
  • Warning Line 79, Column 9842: reference not terminated by REFC delimiter
    ….ashx?k=17654&preredir={amClickThru}&r='+Math.random()+'"><\/script>');</scrip…

    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 79, Column 9842: reference to external entity in attribute value
    ….ashx?k=17654&preredir={amClickThru}&r='+Math.random()+'"><\/script>');</scrip…

    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 79, Column 9842: reference to entity "r" for which no system identifier could be generated
    ….ashx?k=17654&preredir={amClickThru}&r='+Math.random()+'"><\/script>');</scrip…

    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 25, Column 1234: entity was defined here
    …et.ashx?k=17655&preredir={amClickThru}&r='+Math.random()+'"><\/script>');</scr…
  • Error Line 79, Column 9861: required attribute "type" not specified
    …dir={amClickThru}&r='+Math.random()+'"><\/script>');</script></div><!-- adv en…

    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 79, Column 9861: document type does not allow element "script" here
    …dir={amClickThru}&r='+Math.random()+'"><\/script>');</script></div><!-- adv en…

    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 79, Column 9862: character "<" is the first character of a delimiter but occurred as data
    …ir={amClickThru}&r='+Math.random()+'"><\/script>');</script></div><!-- adv end…

    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 79, Column 9889: end tag for "script" omitted, but OMITTAG NO was specified
    …andom()+'"><\/script>');</script></div><!-- adv end --><!-- magazine start -->…

    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 79, Column 9738: start tag was here
    …iv><!-- adv start --><div class="adv"><script>document.write('<script src="htt…
  • Error Line 103, Column 1106: required attribute "type" not specified
    … mixed end --><div class="adv"><script>document.write('<script src="http://run…

    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 103, Column 1187: reference not terminated by REFC delimiter
    …most.com/adx/get.ashx?k=17656&preredir={amClickThru}&r='+Math.random()+'"><\/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 103, Column 1187: reference to external entity in attribute value
    …most.com/adx/get.ashx?k=17656&preredir={amClickThru}&r='+Math.random()+'"><\/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 103, Column 1187: reference to entity "preredir" for which no system identifier could be generated
    …most.com/adx/get.ashx?k=17656&preredir={amClickThru}&r='+Math.random()+'"><\/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 25, Column 1211: entity was defined here
    …://run.admost.com/adx/get.ashx?k=17655&preredir={amClickThru}&r='+Math.random(…
  • Warning Line 103, Column 1203: reference not terminated by REFC delimiter
    ….ashx?k=17656&preredir={amClickThru}&r='+Math.random()+'"><\/script>');</scrip…

    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 103, Column 1203: reference to external entity in attribute value
    ….ashx?k=17656&preredir={amClickThru}&r='+Math.random()+'"><\/script>');</scrip…

    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 103, Column 1203: reference to entity "r" for which no system identifier could be generated
    ….ashx?k=17656&preredir={amClickThru}&r='+Math.random()+'"><\/script>');</scrip…

    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 25, Column 1234: entity was defined here
    …et.ashx?k=17655&preredir={amClickThru}&r='+Math.random()+'"><\/script>');</scr…
  • Error Line 103, Column 1222: required attribute "type" not specified
    …dir={amClickThru}&r='+Math.random()+'"><\/script>');</script></div><div class=…

    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 103, Column 1222: document type does not allow element "script" here
    …dir={amClickThru}&r='+Math.random()+'"><\/script>');</script></div><div class=…

    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 103, Column 1223: character "<" is the first character of a delimiter but occurred as data
    …ir={amClickThru}&r='+Math.random()+'"><\/script>');</script></div><div class="…

    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 103, Column 1250: end tag for "script" omitted, but OMITTAG NO was specified
    …andom()+'"><\/script>');</script></div><div class="clear"></div><div class="ma…

    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 103, Column 1099: start tag was here
    …iv><!-- mixed end --><div class="adv"><script>document.write('<script src="htt…
  • Error Line 111, Column 862: required attribute "type" not specified
    …v></div></div><div class="adv"><script>document.write('<script src="http://run…

    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 111, Column 943: reference not terminated by REFC delimiter
    …most.com/adx/get.ashx?k=17657&preredir={amClickThru}&r='+Math.random()+'"><\/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 111, Column 943: reference to external entity in attribute value
    …most.com/adx/get.ashx?k=17657&preredir={amClickThru}&r='+Math.random()+'"><\/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 111, Column 943: reference to entity "preredir" for which no system identifier could be generated
    …most.com/adx/get.ashx?k=17657&preredir={amClickThru}&r='+Math.random()+'"><\/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 25, Column 1211: entity was defined here
    …://run.admost.com/adx/get.ashx?k=17655&preredir={amClickThru}&r='+Math.random(…
  • Warning Line 111, Column 959: reference not terminated by REFC delimiter
    ….ashx?k=17657&preredir={amClickThru}&r='+Math.random()+'"><\/script>');</scrip…

    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 111, Column 959: reference to external entity in attribute value
    ….ashx?k=17657&preredir={amClickThru}&r='+Math.random()+'"><\/script>');</scrip…

    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 111, Column 959: reference to entity "r" for which no system identifier could be generated
    ….ashx?k=17657&preredir={amClickThru}&r='+Math.random()+'"><\/script>');</scrip…

    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 25, Column 1234: entity was defined here
    …et.ashx?k=17655&preredir={amClickThru}&r='+Math.random()+'"><\/script>');</scr…
  • Error Line 111, Column 978: required attribute "type" not specified
    …dir={amClickThru}&r='+Math.random()+'"><\/script>');</script></div><div class=…

    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 978: document type does not allow element "script" here
    …dir={amClickThru}&r='+Math.random()+'"><\/script>');</script></div><div class=…

    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 111, Column 979: character "<" is the first character of a delimiter but occurred as data
    …ir={amClickThru}&r='+Math.random()+'"><\/script>');</script></div><div class="…

    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 111, Column 1006: end tag for "script" omitted, but OMITTAG NO was specified
    …andom()+'"><\/script>');</script></div><div class="magazine"><div class="img c…

    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 111, Column 855: start tag was here
    …iv></div></div></div><div class="adv"><script>document.write('<script src="htt…
  • Error Line 125, Column 954: required attribute "type" not specified
    …"clear"></div><div class="adv"><script>document.write('<script src="http://run…

    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 125, Column 1035: reference not terminated by REFC delimiter
    …most.com/adx/get.ashx?k=17658&preredir={amClickThru}&r='+Math.random()+'"><\/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 125, Column 1035: reference to external entity in attribute value
    …most.com/adx/get.ashx?k=17658&preredir={amClickThru}&r='+Math.random()+'"><\/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 125, Column 1035: reference to entity "preredir" for which no system identifier could be generated
    …most.com/adx/get.ashx?k=17658&preredir={amClickThru}&r='+Math.random()+'"><\/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 25, Column 1211: entity was defined here
    …://run.admost.com/adx/get.ashx?k=17655&preredir={amClickThru}&r='+Math.random(…
  • Warning Line 125, Column 1051: reference not terminated by REFC delimiter
    ….ashx?k=17658&preredir={amClickThru}&r='+Math.random()+'"><\/script>');</scrip…

    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 125, Column 1051: reference to external entity in attribute value
    ….ashx?k=17658&preredir={amClickThru}&r='+Math.random()+'"><\/script>');</scrip…

    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 125, Column 1051: reference to entity "r" for which no system identifier could be generated
    ….ashx?k=17658&preredir={amClickThru}&r='+Math.random()+'"><\/script>');</scrip…

    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 25, Column 1234: entity was defined here
    …et.ashx?k=17655&preredir={amClickThru}&r='+Math.random()+'"><\/script>');</scr…
  • Error Line 125, Column 1070: required attribute "type" not specified
    …dir={amClickThru}&r='+Math.random()+'"><\/script>');</script></div><div class=…

    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 125, Column 1070: document type does not allow element "script" here
    …dir={amClickThru}&r='+Math.random()+'"><\/script>');</script></div><div class=…

    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 125, Column 1071: character "<" is the first character of a delimiter but occurred as data
    …ir={amClickThru}&r='+Math.random()+'"><\/script>');</script></div><div class="…

    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 125, Column 1098: end tag for "script" omitted, but OMITTAG NO was specified
    …andom()+'"><\/script>');</script></div><div class="magazine"><div class="img c…

    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 125, Column 947: start tag was here
    … class="clear"></div><div class="adv"><script>document.write('<script src="htt…
  • Error Line 133, Column 906: required attribute "type" not specified
    …v></div></div><div class="adv"><script>document.write('<script src="http://run…

    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 133, Column 987: reference not terminated by REFC delimiter
    …most.com/adx/get.ashx?k=17659&preredir={amClickThru}&r='+Math.random()+'"><\/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 133, Column 987: reference to external entity in attribute value
    …most.com/adx/get.ashx?k=17659&preredir={amClickThru}&r='+Math.random()+'"><\/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 133, Column 987: reference to entity "preredir" for which no system identifier could be generated
    …most.com/adx/get.ashx?k=17659&preredir={amClickThru}&r='+Math.random()+'"><\/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 25, Column 1211: entity was defined here
    …://run.admost.com/adx/get.ashx?k=17655&preredir={amClickThru}&r='+Math.random(…
  • Warning Line 133, Column 1003: reference not terminated by REFC delimiter
    ….ashx?k=17659&preredir={amClickThru}&r='+Math.random()+'"><\/script>');</scrip…

    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 133, Column 1003: reference to external entity in attribute value
    ….ashx?k=17659&preredir={amClickThru}&r='+Math.random()+'"><\/script>');</scrip…

    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 133, Column 1003: reference to entity "r" for which no system identifier could be generated
    ….ashx?k=17659&preredir={amClickThru}&r='+Math.random()+'"><\/script>');</scrip…

    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 25, Column 1234: entity was defined here
    …et.ashx?k=17655&preredir={amClickThru}&r='+Math.random()+'"><\/script>');</scr…
  • Error Line 133, Column 1022: required attribute "type" not specified
    …dir={amClickThru}&r='+Math.random()+'"><\/script>');</script></div><div class=…

    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 133, Column 1022: document type does not allow element "script" here
    …dir={amClickThru}&r='+Math.random()+'"><\/script>');</script></div><div class=…

    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 133, Column 1023: character "<" is the first character of a delimiter but occurred as data
    …ir={amClickThru}&r='+Math.random()+'"><\/script>');</script></div><div class="…

    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 133, Column 1050: end tag for "script" omitted, but OMITTAG NO was specified
    …andom()+'"><\/script>');</script></div><div class="agenda"><!-- left start -->…

    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 133, Column 899: start tag was here
    …iv></div></div></div><div class="adv"><script>document.write('<script src="htt…
  • Error Line 147, Column 931: required attribute "type" not specified
    … woman end --><div class="adv"><script>document.write('<script src="http://run…

    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 147, Column 1012: reference not terminated by REFC delimiter
    …most.com/adx/get.ashx?k=17660&preredir={amClickThru}&r='+Math.random()+'"><\/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 147, Column 1012: reference to external entity in attribute value
    …most.com/adx/get.ashx?k=17660&preredir={amClickThru}&r='+Math.random()+'"><\/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 147, Column 1012: reference to entity "preredir" for which no system identifier could be generated
    …most.com/adx/get.ashx?k=17660&preredir={amClickThru}&r='+Math.random()+'"><\/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 25, Column 1211: entity was defined here
    …://run.admost.com/adx/get.ashx?k=17655&preredir={amClickThru}&r='+Math.random(…
  • Warning Line 147, Column 1028: reference not terminated by REFC delimiter
    ….ashx?k=17660&preredir={amClickThru}&r='+Math.random()+'"><\/script>');</scrip…

    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 147, Column 1028: reference to external entity in attribute value
    ….ashx?k=17660&preredir={amClickThru}&r='+Math.random()+'"><\/script>');</scrip…

    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 147, Column 1028: reference to entity "r" for which no system identifier could be generated
    ….ashx?k=17660&preredir={amClickThru}&r='+Math.random()+'"><\/script>');</scrip…

    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 25, Column 1234: entity was defined here
    …et.ashx?k=17655&preredir={amClickThru}&r='+Math.random()+'"><\/script>');</scr…
  • Error Line 147, Column 1047: required attribute "type" not specified
    …dir={amClickThru}&r='+Math.random()+'"><\/script>');</script></div><div class=…

    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 147, Column 1047: document type does not allow element "script" here
    …dir={amClickThru}&r='+Math.random()+'"><\/script>');</script></div><div class=…

    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 147, Column 1048: character "<" is the first character of a delimiter but occurred as data
    …ir={amClickThru}&r='+Math.random()+'"><\/script>');</script></div><div class="…

    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 147, Column 1075: end tag for "script" omitted, but OMITTAG NO was specified
    …andom()+'"><\/script>');</script></div><div class="agenda"><!-- left start -->…

    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 147, Column 924: start tag was here
    …iv><!-- woman end --><div class="adv"><script>document.write('<script src="htt…
  • Error Line 195, Column 1087: required attribute "type" not specified
    …rfix"><div class="advertising"><script>document.write('<script src="http://run…

    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 195, Column 1168: reference not terminated by REFC delimiter
    …most.com/adx/get.ashx?k=17652&preredir={amClickThru}&r='+Math.random()+'"><\/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 195, Column 1168: reference to external entity in attribute value
    …most.com/adx/get.ashx?k=17652&preredir={amClickThru}&r='+Math.random()+'"><\/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 195, Column 1168: reference to entity "preredir" for which no system identifier could be generated
    …most.com/adx/get.ashx?k=17652&preredir={amClickThru}&r='+Math.random()+'"><\/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 25, Column 1211: entity was defined here
    …://run.admost.com/adx/get.ashx?k=17655&preredir={amClickThru}&r='+Math.random(…
  • Warning Line 195, Column 1184: reference not terminated by REFC delimiter
    ….ashx?k=17652&preredir={amClickThru}&r='+Math.random()+'"><\/script>');</scrip…

    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 195, Column 1184: reference to external entity in attribute value
    ….ashx?k=17652&preredir={amClickThru}&r='+Math.random()+'"><\/script>');</scrip…

    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 195, Column 1184: reference to entity "r" for which no system identifier could be generated
    ….ashx?k=17652&preredir={amClickThru}&r='+Math.random()+'"><\/script>');</scrip…

    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 25, Column 1234: entity was defined here
    …et.ashx?k=17655&preredir={amClickThru}&r='+Math.random()+'"><\/script>');</scr…
  • Error Line 195, Column 1203: required attribute "type" not specified
    …dir={amClickThru}&r='+Math.random()+'"><\/script>');</script></div><div class=…

    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 195, Column 1203: document type does not allow element "script" here
    …dir={amClickThru}&r='+Math.random()+'"><\/script>');</script></div><div class=…

    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 195, Column 1204: character "<" is the first character of a delimiter but occurred as data
    …ir={amClickThru}&r='+Math.random()+'"><\/script>');</script></div><div class="…

    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 195, Column 1231: end tag for "script" omitted, but OMITTAG NO was specified
    …andom()+'"><\/script>');</script></div><div class="thinLine"></div><div class=…

    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 195, Column 1080: start tag was here
    …s="clearfix"><div class="advertising"><script>document.write('<script src="htt…
  • Error Line 195, Column 2615: required attribute "alt" not specified
    …argin-top: 10px;margin-bottom: 5px;" /><div id="sondakika2"><p class=digerbg><…

    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 195, Column 2646: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …5px;" /><div id="sondakika2"><p class=digerbg><b>01:09</b><a href="http://www.…
  • Error Line 195, Column 3120: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …Geçeceğiz&#039;&#039;</a></p><p class=digerbg><b>00:44</b><a href="http://www.…
  • Error Line 195, Column 3533: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …e Bu Hatalar Olmamalı</a></p><p class=digerbg><b>00:06</b><a href="http://www.…
  • Error Line 195, Column 3955: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …da Çatışma: 3 Yaralı!</a></p><p class=digerbg><b>23:55</b><a href="http://www.…
  • Error Line 195, Column 4464: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … Edilenleri Yanıtladı</a></p><p class=digerbg><b>23:36</b><a href="http://www.…
  • Error Line 195, Column 4829: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …PSY İstanbul&#039;da!</a></p><p class=digerbg><b>20:01</b><a href="http://www.…
  • Error Line 195, Column 5327: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ti Kararı Yarın&quot;</a></p><p class=digerbg><b>19:43</b><a href="http://www.…
  • Error Line 195, Column 5677: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …#039;in Büyük Korkusu</a></p><p class=digerbg><b>19:31</b><a href="http://www.…
  • Error Line 195, Column 6009: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …">Diebler 4 Hafta Yok</a></p><p class=digerbg><b>19:24</b><a href="http://www.…
  • Error Line 195, Column 6446: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …an Karşıtları Sokakta</a></p><p class=digerbg><b>19:12</b><a href="http://www.…
  • Error Line 195, Column 6879: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …asal Koruyucu Kıyafet</a></p><p class=digerbg><b>19:05</b><a href="http://www.…
  • Error Line 195, Column 7270: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …kiye Çocuklar Elemesi</a></p><p class=digerbg><b>17:33</b><a href="http://www.…
  • Error Line 195, Column 7742: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ımız Tecrübemiz&quot;</a></p><p class=digerbg><b>16:42</b><a href="http://www.…
  • Error Line 195, Column 8181: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ojede mi Yer Alacak? </a></p><p class=digerbg><b>15:58</b><a href="http://www.…
  • Error Line 195, Column 8558: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …enerbahçe Rahat Geçti</a></p><p class=digerbg><b>15:33</b><a href="http://www.…
  • Error Line 195, Column 8968: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … &#039;Sefiller&#039;</a></p><p class=digerbg><b>15:23</b><a href="http://www.…
  • Error Line 195, Column 9363: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …Randevu İçin İpuçları</a></p><p class=digerbg><b>15:10</b><a href="http://www.…
  • Error Line 195, Column 9787: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …n Hakemleri Açıklandı</a></p><p class=digerbg><b>15:03</b><a href="http://www.…
  • Error Line 195, Column 10191: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …Mete Kalkavan&#039;ın</a></p><p class=digerbg><b>15:03</b><a href="http://www.…
  • Error Line 195, Column 10640: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …adın Formula 1 Pilotu</a></p><p class=digerbg><b>14:49</b><a href="http://www.…
  • Error Line 195, Column 11096: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …in Biletleri Tükendi!</a></p><p class=digerbg><b>14:37</b><a href="http://www.…
  • Error Line 195, Column 11575: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …çeküstü Bir Doğallık!</a></p><p class=digerbg><b>14:25</b><a href="http://www.…
  • Error Line 195, Column 12005: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … Saçma Gelen Detaylar</a></p><p class=digerbg><b>14:19</b><a href="http://www.…
  • Error Line 195, Column 12441: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …m Olduğunuzu Öğrenin!</a></p><p class=digerbg><b>14:08</b><a href="http://www.…
  • Error Line 195, Column 12836: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ivasspor Hazırlıkları</a></p><p class=digerbg><b>14:08</b><a href="http://www.…
  • Error Line 195, Column 13198: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …#039;dan Özel Tanıtım</a></p><p class=digerbg><b>14:06</b><a href="http://www.…
  • Error Line 195, Column 13562: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …a İhtiyacınız Var mı?</a></p><p class=digerbg><b>13:47</b><a href="http://www.…
  • Error Line 195, Column 13944: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …Adana Derbisine Doğru</a></p><p class=digerbg><b>13:25</b><a href="http://www.…
  • Error Line 195, Column 14345: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … Zorluk Derecesi Aynı</a></p><p class=digerbg><b>13:25</b><a href="http://www.…
  • Error Line 195, Column 14786: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … Finale Yakışır Jest!</a></p><p class=digerbg><b>13:10</b><a href="http://www.…
  • Error Line 195, Column 15201: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …acı Hayatını Kaybetti</a></p><p class=digerbg><b>12:54</b><a href="http://www.…
  • Error Line 195, Column 15628: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …di 3&#039;mü Geliyor?</a></p><p class=digerbg><b>12:33</b><a href="http://www.…
  • Error Line 195, Column 16037: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …nde Göz Kamaştırdılar</a></p><p class=digerbg><b>12:32</b><a href="http://www.…
  • Error Line 195, Column 16393: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …lı&#039;ya Özel Görev</a></p><p class=digerbg><b>12:32</b><a href="http://www.…
  • Error Line 195, Column 16764: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … Doğum Günü Kutlaması</a></p><p class=digerbg><b>12:23</b><a href="http://www.…
  • Error Line 195, Column 35202: required attribute "type" not specified
    …sing" style="margin-top:10px;"><script>document.write('<script src="http://run…

    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 195, Column 35283: reference not terminated by REFC delimiter
    …most.com/adx/get.ashx?k=17653&preredir={amClickThru}&r='+Math.random()+'"><\/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 195, Column 35283: reference to external entity in attribute value
    …most.com/adx/get.ashx?k=17653&preredir={amClickThru}&r='+Math.random()+'"><\/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 195, Column 35283: reference to entity "preredir" for which no system identifier could be generated
    …most.com/adx/get.ashx?k=17653&preredir={amClickThru}&r='+Math.random()+'"><\/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 25, Column 1211: entity was defined here
    …://run.admost.com/adx/get.ashx?k=17655&preredir={amClickThru}&r='+Math.random(…
  • Warning Line 195, Column 35299: reference not terminated by REFC delimiter
    ….ashx?k=17653&preredir={amClickThru}&r='+Math.random()+'"><\/script>');</scrip…

    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 195, Column 35299: reference to external entity in attribute value
    ….ashx?k=17653&preredir={amClickThru}&r='+Math.random()+'"><\/script>');</scrip…

    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 195, Column 35299: reference to entity "r" for which no system identifier could be generated
    ….ashx?k=17653&preredir={amClickThru}&r='+Math.random()+'"><\/script>');</scrip…

    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 25, Column 1234: entity was defined here
    …et.ashx?k=17655&preredir={amClickThru}&r='+Math.random()+'"><\/script>');</scr…
  • Error Line 195, Column 35318: required attribute "type" not specified
    …dir={amClickThru}&r='+Math.random()+'"><\/script>');</script></div><div class=…

    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 195, Column 35318: document type does not allow element "script" here
    …dir={amClickThru}&r='+Math.random()+'"><\/script>');</script></div><div class=…

    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 195, Column 35319: character "<" is the first character of a delimiter but occurred as data
    …ir={amClickThru}&r='+Math.random()+'"><\/script>');</script></div><div class="…

    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 195, Column 35346: end tag for "script" omitted, but OMITTAG NO was specified
    …andom()+'"><\/script>');</script></div><div class="top10"><div class="title"><…

    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 195, Column 35195: start tag was here
    …advertising" style="margin-top:10px;"><script>document.write('<script src="htt…
  • Error Line 203, Column 535: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …0; height: 206px;" id="gunun_sorusu_1"><p style="padding-top: 45px"><img borde…

    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 203, Column 667: required attribute "alt" not specified
    …urkan/sur_110057782251215a5522c3e.png"></p></div></a><a href="http://www.acunn…

    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 203, Column 671: end tag for "img" omitted, but OMITTAG NO was specified
    …n/sur_110057782251215a5522c3e.png"></p></div></a><a href="http://www.acunn.com…

    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 203, Column 565: start tag was here
    …orusu_1"><p style="padding-top: 45px"><img border="0" width="298" src="http://…
  • Error Line 203, Column 887: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …0; height: 206px;" id="gunun_sorusu_2"><p style="padding-top: 45px"><img borde…

    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 203, Column 1020: required attribute "alt" not specified
    …rkan/soru_110889405451197ea2f3ce6.png"></p></div></a><script>var aktifId = 3;<…

    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 203, Column 1024: end tag for "img" omitted, but OMITTAG NO was specified
    …/soru_110889405451197ea2f3ce6.png"></p></div></a><script>var aktifId = 3;</scr…

    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 203, Column 917: start tag was here
    …orusu_2"><p style="padding-top: 45px"><img border="0" width="298" src="http://…
  • Error Line 203, Column 1042: required attribute "type" not specified
    …197ea2f3ce6.png"></p></div></a><script>var aktifId = 3;</script><a href="http:…

    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 203, Column 1238: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …0; height: 206px;" id="gunun_sorusu_3"><p style="padding-top: 45px"><img borde…

    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 203, Column 1370: required attribute "alt" not specified
    …urkan/title_52069478510903c8c9fa3.jpg"></p></div></a><a href="http://www.acunn…

    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 203, Column 1374: end tag for "img" omitted, but OMITTAG NO was specified
    …n/title_52069478510903c8c9fa3.jpg"></p></div></a><a href="http://www.acunn.com…

    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 203, Column 1268: start tag was here
    …orusu_3"><p style="padding-top: 45px"><img border="0" width="298" src="http://…
  • Error Line 203, Column 1564: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …0; height: 206px;" id="gunun_sorusu_4"><p style="padding-top: 45px"><img borde…

    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 203, Column 1698: required attribute "alt" not specified
    …kan/title_145045080150f73b8cb572d.png"></p></div></a><a href="http://www.acunn…

    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 203, Column 1702: end tag for "img" omitted, but OMITTAG NO was specified
    …title_145045080150f73b8cb572d.png"></p></div></a><a href="http://www.acunn.com…

    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 203, Column 1594: start tag was here
    …orusu_4"><p style="padding-top: 45px"><img border="0" width="298" src="http://…
  • Error Line 203, Column 1897: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …0; height: 206px;" id="gunun_sorusu_5"><p style="padding-top: 45px"><img borde…

    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 203, Column 2029: required attribute "alt" not specified
    …urkan/flx_1618182042508a763aca56f.png"></p></div></a><div class="clear"></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 203, Column 2033: end tag for "img" omitted, but OMITTAG NO was specified
    …n/flx_1618182042508a763aca56f.png"></p></div></a><div class="clear"></div><div…

    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 203, Column 1927: start tag was here
    …orusu_5"><p style="padding-top: 45px"><img border="0" width="298" src="http://…
  • Error Line 203, Column 2474: required attribute "alt" not specified
    …a5529153.png" width="210" height="120"><img style="margin: 0 0 6px -45px;" alt…

    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 203, Column 2475: end tag for "img" omitted, but OMITTAG NO was specified
    …5529153.png" width="210" height="120"><img style="margin: 0 0 6px -45px;" alt=…

    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 203, Column 2340: start tag was here
    …/523561" onmouseover="gununsorusu(1)"><img style="border-radius: 3px;" src="ht…
  • Error Line 203, Column 2594: end tag for "img" omitted, but OMITTAG NO was specified
    …/v2/images/video/v6-play-icon.png"></a></div><div id="gunun_sorusu_img_2" styl…

    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 203, Column 2475: start tag was here
    …5529153.png" width="210" height="120"><img style="margin: 0 0 6px -45px;" alt=…
  • Error Line 203, Column 2962: required attribute "alt" not specified
    …ea306ff6.png" width="210" height="120"><img style="margin: 0 0 6px -45px;" alt…

    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 203, Column 2963: end tag for "img" omitted, but OMITTAG NO was specified
    …a306ff6.png" width="210" height="120"><img style="margin: 0 0 6px -45px;" alt=…

    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 203, Column 2831: start tag was here
    …/518004" onmouseover="gununsorusu(2)"><img style="border-radius: 3px;" src="ht…
  • Error Line 203, Column 3082: end tag for "img" omitted, but OMITTAG NO was specified
    …/v2/images/video/v6-play-icon.png"></a></div><div id="gunun_sorusu_img_3" styl…

    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 203, Column 2963: start tag was here
    …a306ff6.png" width="210" height="120"><img style="margin: 0 0 6px -45px;" alt=…
  • Error Line 203, Column 3416: required attribute "alt" not specified
    …3c8d654a.jpg" width="210" height="120"><img style="margin: 0 0 6px -45px;" alt…

    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 203, Column 3417: end tag for "img" omitted, but OMITTAG NO was specified
    …c8d654a.jpg" width="210" height="120"><img style="margin: 0 0 6px -45px;" alt=…

    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 203, Column 3284: start tag was here
    …/525561" onmouseover="gununsorusu(3)"><img style="border-radius: 3px;" src="ht…
  • Error Line 203, Column 3536: end tag for "img" omitted, but OMITTAG NO was specified
    …/v2/images/video/v6-play-icon.png"></a></div><div id="gunun_sorusu_img_4" styl…

    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 203, Column 3417: start tag was here
    …c8d654a.jpg" width="210" height="120"><img style="margin: 0 0 6px -45px;" alt=…
  • Error Line 203, Column 3879: required attribute "alt" not specified
    …b8cba71f.png" width="210" height="120"><img style="margin: 0 0 6px -45px;" alt…

    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 203, Column 3880: end tag for "img" omitted, but OMITTAG NO was specified
    …8cba71f.png" width="210" height="120"><img style="margin: 0 0 6px -45px;" alt=…

    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 203, Column 3747: start tag was here
    …/512869" onmouseover="gununsorusu(4)"><img style="border-radius: 3px;" src="ht…
  • Error Line 203, Column 3999: end tag for "img" omitted, but OMITTAG NO was specified
    …/v2/images/video/v6-play-icon.png"></a></div><div id="gunun_sorusu_img_5" styl…

    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 203, Column 3880: start tag was here
    …8cba71f.png" width="210" height="120"><img style="margin: 0 0 6px -45px;" alt=…
  • Error Line 203, Column 4347: required attribute "alt" not specified
    …0ba35c46.png" width="210" height="120"><img style="margin: 0 0 6px -45px;" alt…

    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 203, Column 4348: end tag for "img" omitted, but OMITTAG NO was specified
    …ba35c46.png" width="210" height="120"><img style="margin: 0 0 6px -45px;" alt=…

    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 203, Column 4215: start tag was here
    …/441099" onmouseover="gununsorusu(5)"><img style="border-radius: 3px;" src="ht…
  • Error Line 203, Column 4467: end tag for "img" omitted, but OMITTAG NO was specified
    …/v2/images/video/v6-play-icon.png"></a></div></div><div class="clear"></div><u…

    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 203, Column 4348: start tag was here
    …ba35c46.png" width="210" height="120"><img style="margin: 0 0 6px -45px;" alt=…
  • Error Line 203, Column 4647: document type does not allow element "a" here; assuming missing "li" start-tag
    …r/523561" onmouseover="gununsorusu(1)"><li id="day_1" class="pts"></li></a><a …
  • Error Line 203, Column 4674: document type does not allow element "li" here
    …nsorusu(1)"><li id="day_1" class="pts"></li></a><a href="http://www.acunn.com/…

    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 203, Column 4834: document type does not allow element "li" here
    …nsorusu(2)"><li id="day_2" class="sal"></li></a><a href="http://www.acunn.com/…

    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 203, Column 4965: document type does not allow element "li" here
    …(3)"><li id="day_3" class="car-active"></li></a><a href="http://www.acunn.com/…

    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 203, Column 5099: document type does not allow element "li" here
    …nsorusu(4)"><li id="day_4" class="per"></li></a><a href="http://www.acunn.com/…

    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 203, Column 5238: document type does not allow element "li" here
    …nsorusu(5)"><li id="day_5" class="cum"></li></a></ul><div class="clear"></div>…

    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 203, Column 5252: end tag for "li" omitted, but OMITTAG NO was specified
    …i id="day_5" class="cum"></li></a></ul><div class="clear"></div></div><!--Günü…

    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 203, Column 4525: start tag was here
    …ass="clear"></div><ul class="fd-list"><a href="http://www.acunn.com/video/izle…
  • Error Line 203, Column 5405: there is no attribute "href"
    …iv class="facebook"><fb:like-box href="http://www.facebook.com/acunncom" width…

    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 203, Column 5446: there is no attribute "width"
    …tp://www.facebook.com/acunncom" width="300" height="255" show_faces="true" str…

    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 203, Column 5459: there is no attribute "height"
    …book.com/acunncom" width="300" height="255" show_faces="true" stream="false" h…

    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 203, Column 5476: there is no attribute "show_faces"
    …" width="300" height="255" show_faces="true" stream="false" header="false"></f…

    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 203, Column 5490: there is no attribute "stream"
    …height="255" show_faces="true" stream="false" header="false"></fb:like-box></d…

    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 203, Column 5505: there is no attribute "header"
    …ow_faces="true" stream="false" header="false"></fb:like-box></div></div><!-- r…

    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 203, Column 5512: element "fb:like-box" undefined
    …s="true" stream="false" header="false"></fb:like-box></div></div><!-- right en…

    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 203, Column 6317: end tag for "input" omitted, but OMITTAG NO was specified
    …?'Acunn.com'da Ara':this.value;"></div></form></div><div class="clear"></div><…

    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 203, Column 6081: start tag was here
    …t="" /></div><div style="float:left;"><input style="height: 18px;width: 186px;…
  • Error Line 207, Column 101: end tag for "br" omitted, but OMITTAG NO was specified
    …p://www.acunn.com/haber">Haber</a><br><a href="http://www.acunn.com/haber/maga…

    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 207, Column 97: start tag was here
    …"http://www.acunn.com/haber">Haber</a><br><a href="http://www.acunn.com/haber/…
  • Error Line 207, Column 161: end tag for "br" omitted, but OMITTAG NO was specified
    …unn.com/haber/magazin">Magazin</a><br><a href="http://www.acunn.com/sinema">Si…

    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 207, Column 157: start tag was here
    …w.acunn.com/haber/magazin">Magazin</a><br><a href="http://www.acunn.com/sinema…
  • Error Line 207, Column 213: end tag for "br" omitted, but OMITTAG NO was specified
    …//www.acunn.com/sinema">Sinema</a><br><a href="http://www.acunn.com/haber/muzi…

    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 207, Column 209: start tag was here
    …ttp://www.acunn.com/sinema">Sinema</a><br><a href="http://www.acunn.com/haber/…
  • Error Line 207, Column 269: end tag for "br" omitted, but OMITTAG NO was specified
    …w.acunn.com/haber/muzik">Müzik</a><br><a href="http://www.acunn.com/galeri">Fo…

    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 207, Column 265: start tag was here
    …//www.acunn.com/haber/muzik">Müzik</a><br><a href="http://www.acunn.com/galeri…
  • Error Line 207, Column 326: end tag for "br" omitted, but OMITTAG NO was specified
    ….acunn.com/galeri">Foto Galeri</a><br><a href="http://www.acunn.com/haber/kadi…

    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 207, Column 322: start tag was here
    …/www.acunn.com/galeri">Foto Galeri</a><br><a href="http://www.acunn.com/haber/…
  • Error Line 207, Column 382: end tag for "br" omitted, but OMITTAG NO was specified
    …w.acunn.com/haber/kadin">Kadın</a><br><a href="http://www.acunn.com/haber/tekn…

    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 207, Column 378: start tag was here
    …//www.acunn.com/haber/kadin">Kadın</a><br><a href="http://www.acunn.com/haber/…
  • Error Line 207, Column 446: end tag for "br" omitted, but OMITTAG NO was specified
    …com/haber/teknoloji">Teknoloji</a><br><a href="http://www.acunn.com/spor">Spor…

    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 207, Column 442: start tag was here
    …unn.com/haber/teknoloji">Teknoloji</a><br><a href="http://www.acunn.com/spor">…
  • Error Line 207, Column 494: end tag for "br" omitted, but OMITTAG NO was specified
    …ttp://www.acunn.com/spor">Spor</a><br><a href="http://www.acunn.com/saglik">Sa…

    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 207, Column 490: start tag was here
    …f="http://www.acunn.com/spor">Spor</a><br><a href="http://www.acunn.com/saglik…
  • Error Line 207, Column 551: end tag for "br" omitted, but OMITTAG NO was specified
    ….acunn.com/saglik">Sağlık</a><br></div></div><div class="competitions"><div cl…

    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 207, Column 542: start tag was here
    …ttp://www.acunn.com/saglik">Sağlık</a><br></div></div><div class="competitions…
  • Error Line 213, Column 107: end tag for "br" omitted, but OMITTAG NO was specified
    …w.acunn.com/iletisim">İletişim</a><br><a href="http://www.acunn.com/yasal-uyar…

    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 213, Column 103: start tag was here
    …//www.acunn.com/iletisim">İletişim</a><br><a href="http://www.acunn.com/yasal-…
  • Error Line 213, Column 195: end tag for "br" omitted, but OMITTAG NO was specified
    …Acunn Yasal Uyarı">Yasal Uyarı</a><br><a href="http://www.acunn.com/kullanim-k…

    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 213, Column 191: start tag was here
    …le="Acunn Yasal Uyarı">Yasal Uyarı</a><br><a href="http://www.acunn.com/kullan…
  • Error Line 213, Column 304: end tag for "br" omitted, but OMITTAG NO was specified
    … Koşulları">Kullanım Koşulları</a><br><a href="http://www.acunn.com/guvenlik-g…

    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 213, Column 300: start tag was here
    …anım Koşulları">Kullanım Koşulları</a><br><a href="http://www.acunn.com/guvenl…
  • Warning Line 213, Column 375: character "&" is the first character of a delimiter but occurred as data
    …enlik-gizlilik" title="Acunn Güvenlik & Gizlilik">Güvenlik &amp; Gizlilik</a><…

    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 213, Column 423: end tag for "br" omitted, but OMITTAG NO was specified
    …">Güvenlik &amp; Gizlilik</a><br></div></div></div><!-- right end --><div clas…

    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 213, Column 414: start tag was here
    … Gizlilik">Güvenlik &amp; Gizlilik</a><br></div></div></div><!-- right end -->…
  • Error Line 273, Column 16: required attribute "type" not specified
    </script><style>

    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 273, Column 16: document type does not allow element "style" here
    </script><style>

    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 280, Column 381: required attribute "alt" not specified
    …lute; left: 580px; cursor:pointer; " /><div class="likebox"><div class="fb-lik…

    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 280, Column 434: there is no attribute "data-href"
    …kebox"><div class="fb-like" data-href="http://www.facebook.com/acunncom" data-…

    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 280, Column 479: there is no attribute "data-send"
    …/www.facebook.com/acunncom" data-send="false" data-layout="button_count" data-…

    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 280, Column 499: there is no attribute "data-layout"
    …unncom" data-send="false" data-layout="button_count" data-width="450" data-sho…

    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 280, Column 525: there is no attribute "data-width"
    …data-layout="button_count" data-width="450" data-show-faces="false"></div></di…

    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 280, Column 547: there is no attribute "data-show-faces"
    …unt" data-width="450" data-show-faces="false"></div></div><div class="likebox2…

    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 280, Column 688: there is no attribute "data-height"
    …cunncom" data-width="555" data-height="180" data-show-faces="true" data-stream…

    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 280, Column 729: there is no attribute "data-stream"
    …0" data-show-faces="true" data-stream="false" data-header="false"></div></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 280, Column 749: there is no attribute "data-header"
    …true" data-stream="false" data-header="false"></div></div></div></div></body><…

    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.

Visitor Analysis

Daily Visitor
  • 15.983 visits

In Page Analysis