zikostartube.com has Alexa Rank 1.710.085 and Google Page Rank is 0

zikostartube.com
  • Domain Name
    zikostartube.com
  • Favicon
  • Google Page Rank
    0
  • Alexa Rank
    #1710085
  • Page Size
    521 B
  • Ip Address
    208.43.167.116
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 0 JPG, 0 PNG

Website Meta Analysis

  • Title
  • Meta Keyword
  • Meta Description

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    208.43.167.116
  • Domain Age
    7 Months, 18 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Wed, 26 Jun 2013 23:40:51 GMT
  • server: Apache
  • content-length: 521
  • connection: close
  • content-type: text/html; charset=UTF-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for zikostartube.com

DNS Analysis


DNS servers
ns1.idhostinger.com [31.170.163.241]
ns2.idhostinger.com [64.191.115.234]
ns3.idhostinger.com [173.192.183.247]
ns4.idhostinger.com [31.170.164.249]


DNS Records

Answer records
zikostartube.com SOA
server: ns1.idhostinger.com
email: postmaster@zikostartube.com
serial: 2012121519
refresh: 28800
retry: 7200
expire: 604800
minimum ttl: 86400
86400s
zikostartube.com A 27.122.14.168 86400s
zikostartube.com MX
preference: 0
exchange: mx1.idhostinger.com
86400s
zikostartube.com NS  ns1.idhostinger.com 86400s
zikostartube.com NS  ns2.idhostinger.com 86400s
zikostartube.com NS  ns3.idhostinger.com 86400s
zikostartube.com NS  ns4.idhostinger.com 86400s

Authority records

Additional records
mx1.idhostinger.com A 31.170.164.5 86400s
ns1.idhostinger.com A 31.170.163.241 86400s
ns2.idhostinger.com A 64.191.115.234 86400s
ns3.idhostinger.com A 173.192.183.247 86400s
ns4.idhostinger.com A 31.170.164.249 86400s

IP 208.43.167.116 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 2 Errors
  • 2 Warnings
Ratio Text/Html
  • 0.8426103646833013
Message Error
  • Error Line 16, Column 21: required attribute "type" not specified
    <script id="_waup0s">var _wau = _wau || [];

    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 20: there is no attribute "language"
    		<script language="JavaScript" type="text/javascript" src="http://zikostartube…

    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 114, Column 68: end tag for element "a" which is not open
    		<a href="http://zikostartube.com/uye-ol" class="favo" />DAFTAR</a>

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

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

  • Error Line 115, Column 66: end tag for element "a" which is not open
    		<a href="http://zikostartube.com/login" class="inde" />MASUK</a>

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

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

  • Error Line 137, Column 9: element "center" undefined
    	<center><form id="searchform" method="get" action="http://zikostartube.com/">

    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 139, Column 167: document type does not allow element "input" here; missing one of "ins", "del", "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "address", "fieldset" start-tag
    …') {this.value = '';}" onblur="if (this.value == '') {this.value = 'Cari';}" />

    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 141, Column 50: document type does not allow element "input" here; missing one of "ins", "del", "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "address", "fieldset" start-tag
    <input type="submit" id="searchbutton" value="" />

    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 143, Column 7: end tag for "form" which is not finished
    </form></center>

    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 163, Column 48: document type does not allow element "ul" here; assuming missing "li" start-tag
    …="menu-custom-small-menu" class="menu"><li id="menu-item-1625" class="menu-ite…
  • Error Line 171, Column 8: end tag for "li" omitted, but OMITTAG NO was specified
    			</ul>

    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 163, Column 4: start tag was here
    			<ul id="menu-custom-small-menu" class="menu"><li id="menu-item-1625" class="…
  • Error Line 472, Column 18: there is no attribute "LANGUAGE"
    <SCRIPT LANGUAGE="JavaScript1.1" SRC="http://bdv.bidvertiser.com/BidVertiser.db…

    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 472, Column 38: there is no attribute "SRC"
    <SCRIPT LANGUAGE="JavaScript1.1" SRC="http://bdv.bidvertiser.com/BidVertiser.db…

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

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

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

  • Warning Line 472, Column 93: cannot generate system identifier for general entity "bid"
    …rtiser.com/BidVertiser.dbm?pid=477574&bid=1236072" type="text/javascript"></SC…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 472, Column 93: general entity "bid" not defined and no default entity
    …rtiser.com/BidVertiser.dbm?pid=477574&bid=1236072" type="text/javascript"></SC…

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

  • Warning Line 472, Column 96: reference not terminated by REFC delimiter
    …ser.com/BidVertiser.dbm?pid=477574&bid=1236072" type="text/javascript"></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 472, Column 96: reference to external entity in attribute value
    …ser.com/BidVertiser.dbm?pid=477574&bid=1236072" type="text/javascript"></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 472, Column 96: reference to entity "bid" for which no system identifier could be generated
    …ser.com/BidVertiser.dbm?pid=477574&bid=1236072" type="text/javascript"></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 472, Column 92: entity was defined here
    …ertiser.com/BidVertiser.dbm?pid=477574&bid=1236072" type="text/javascript"></S…
  • Error Line 472, Column 111: there is no attribute "type"
    …om/BidVertiser.dbm?pid=477574&bid=1236072" type="text/javascript"></SCRIPT></p>

    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 472, Column 128: element "SCRIPT" undefined
    …om/BidVertiser.dbm?pid=477574&bid=1236072" type="text/javascript"></SCRIPT></p>

    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 473, Column 82: document type does not allow element "a" here; missing one of "ins", "del", "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "pre", "address", "fieldset" start-tag
    ….bidvertiser.com/bdv/BidVertiser/bdv_advertiser.dbm">advertising</a></noscript>

    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 473, Column 108: end tag for "noscript" which is not finished
    ….bidvertiser.com/bdv/BidVertiser/bdv_advertiser.dbm">advertising</a></noscript>

    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 526, Column 100: document type does not allow element "form" here; assuming missing "li" start-tag
    …rm" id="loginform" action="http://zikostartube.com/wp-login.php" method="post">
  • Error Line 543, Column 262: end tag for "li" omitted, but OMITTAG NO was specified
    …llow">Lost Password</a></li></ul></div></div><div class="sidebarborder"><div 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 526, Column 3: start tag was here
    		<form name="loginform" id="loginform" action="http://zikostartube.com/wp-logi…
  • Error Line 543, Column 262: end tag for "ul" omitted, but OMITTAG NO was specified
    …llow">Lost Password</a></li></ul></div></div><div class="sidebarborder"><div 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 524, Column 91: start tag was here
    …ebarborder"><div class="sidebar-right"><h2><span>MASUK / LOGIN</span></h2>	<ul>
  • Error Line 545, Column 15: there is no attribute "src"
    		<iframe src="http://www.facebook.com/plugins/likebox.php?href=http%3A%2F%2Fww…

    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 545, Column 245: there is no attribute "scrolling"
    …eader=false&amp;height=800" scrolling="no" frameborder="0" style="border:none;…

    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 545, Column 262: there is no attribute "frameborder"
    …eight=800" scrolling="no" frameborder="0" style="border:none; overflow:hidden;…

    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 545, Column 272: there is no attribute "style"
    … scrolling="no" frameborder="0" style="border:none; overflow:hidden; width:240…

    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 545, Column 350: there is no attribute "allowTransparency"
    …verflow:hidden; width:240px; height: 800px;" allowTransparency="true"></iframe>

    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 545, Column 356: element "iframe" undefined
    …verflow:hidden; width:240px; height: 800px;" allowTransparency="true"></iframe>

    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 557, Column 23: document type does not allow element "style" here
    <style type="text/css">

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

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

  • Error Line 601, Column 183: required attribute "alt" not specified
    …ick = "javascript:lbx_hide_lightbox()"><!-- <div width="100%" height="20px" st…

    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 601, Column 184: end tag for "img" omitted, but OMITTAG NO was specified
    …ck = "javascript:lbx_hide_lightbox()"><!-- <div width="100%" height="20px" sty…

    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 601, Column 41: start tag was here
    …iv id="lbx_light" class="lbx_content"><img id="closediv"   src="http://zikosta…
  • Warning Line 718, Column 17: character "&" is the first character of a delimiter but occurred as data
    if ( ( !start ) && ( name != document.cookie.substring( 0, name.length ) ) )

    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 718, Column 18: character "&" is the first character of a delimiter but occurred as data
    if ( ( !start ) && ( name != document.cookie.substring( 0, name.length ) ) )

    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 763, Column 84: end tag for element "br" which is not open
    …p://zikostartube.com">ZIKOSTARTUBE.COM</a></br><span>All Rights Reserved</span>

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

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

  • Error Line 769, Column 79: there is no attribute "target"
    …" title="social movies online" target="_blank"><img src="http://zikostartube.c…

    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 770, Column 23: an attribute value must be a literal unless it contains only name characters
                <a target=_new” href=”http://www.esflim.com/” title=”SOCIAL MOVIES…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 770, Column 35: an attribute value must be a literal unless it contains only name characters
                <a target=”_new” href=http://www.esflim.com/” title=”SOCIAL MOVIES…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 770, Column 66: an attribute value must be a literal unless it contains only name characters
    …” href=”http://www.esflim.com/” title=SOCIAL MOVIES ONLINE,belgesel video,der…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 770, Column 81: "MOVIES" is not a member of a group specified for any attribute
    …www.esflim.com/” title=”SOCIAL MOVIES ONLINE,belgesel video,ders videoları” >S…
  • Error Line 770, Column 87: "ONLINE" is not a member of a group specified for any attribute
    …flim.com/” title=”SOCIAL MOVIES ONLINE,belgesel video,ders videoları” >SOCIAL …
  • Error Line 770, Column 102: "video" is not a member of a group specified for any attribute
    …e=”SOCIAL MOVIES ONLINE,belgesel video,ders videoları” >SOCIAL MOVIES ONLINE</…
  • Error Line 770, Column 117: "videoları" is not a member of a group specified for any attribute
    …=”SOCIAL MOVIES ONLINE,belgesel video,ders videoları >SOCIAL MOVIES ONLINE</a>
  • Error Line 786, Column 20: an attribute specification must start with a name or name token
    document.write("<sc"+"ript type='text/javascript' src='" +

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 786, Column 20: element "sc" undefined
    document.write("<sc"+"ript type='text/javascript' src='" +

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 790, Column 38: character "<" is the first character of a delimiter but occurred as data
    "statcounter.com/counter/counter.js'></"+"script>");

    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 792, Column 9: end tag for "sc" omitted, but OMITTAG NO was specified
    </script>

    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 786, Column 17: start tag was here
    document.write("<sc"+"ript type='text/javascript' src='" +
  • Error Line 802, Column 27: end tag for "img" omitted, but OMITTAG NO was specified
    alt="free hit counter"></a></div></noscript>

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

  • Info Line 798, Column 17: start tag was here
    target="_blank"><img class="statcounter"

Visitor Analysis

Daily Visitor
  • 70 visits