downvids.net

Download Facebook Videos Online - Download and Save Videos from Facebook,Youtube.Online Easily with one simple click. ...

Display Widget for this domain on your website. Click Here
Processing update domain...

Overview Info

  • Domain Name
    downvids.net
  • Favicon
  • Alexa Rank
    #31999
  • Google Page Rank
    PR 3
  • Ip Address
    46.105.38.101
  • Page Size
    23.1 KB
  • Images
    0 GIF, 16 JPG, 4 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 0 1 0 0 0

Website Meta Analysis



  • Title
    Download Facebook, Youtube Videos
  • Meta Keyword
    download youtube videos, download facebook videos,facebook video download, youtube video download,download video onto facebook, online video download, online video converter
  • Meta Description
    Download Facebook Videos Online - Download and Save Videos from Facebook,Youtube.Online Easily with one simple click.

Technical Analysis



  • Webserver
    Apache/2
  • Ip Address
    46.105.38.101
  • Domain Age
    12 Months, 0 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from downvids.net.

HTML Analysis

  • date: Tue, 13 Aug 2013 12:38:39 GMT
  • server: Apache/2
  • x-powered-by: PHP/5.2.17
  • vary: Accept-Encoding,User-Agent
  • content-encoding: gzip
  • content-length: 5160
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for downvids.net

DNS Analysis


DNS servers
ns1.downvids.net [213.128.82.74]
ns2.downvids.net [213.128.82.74]


DNS Records

Answer records
downvids.net MX
preference: 10
exchange: mail.downvids.net
14400s
downvids.net TXT v=spf1 a mx ip4:213.128.82.74 ~all 14400s
downvids.net SOA
server: ns1.downvids.net
email: hostmaster@downvids.net
serial: 2012111500
refresh: 14400
retry: 3600
expire: 1209600
minimum ttl: 86400
14400s
downvids.net NS  ns1.downvids.net 14400s
downvids.net NS  ns2.downvids.net 14400s
downvids.net A 213.128.82.74 14400s

Authority records

Additional records
mail.downvids.net A 213.128.82.74 14400s
ns1.downvids.net A 213.128.82.74 14400s
ns2.downvids.net A 213.128.82.74 14400s

IP 46.105.38.101 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 49 Errors
  • 5 Warnings
Ratio Text/Html
  • 0.6774179894179895
Message Error
  • Error Line 1, Column 109: DTD did not contain element declaration for document type name
    …/DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">

    A DOCTYPE declares the version of the language used, as well as what the root (top) element of your document will be. For example, if the top element of your document is <html>, the DOCTYPE declaration will look like: "<!DOCTYPE html".

    In most cases, it is safer not to type or edit the DOCTYPE declaration at all, and preferable to let a tool include it, or copy and paste it from a trusted list of DTDs.

  • Error Line 3, Column 67: document type does not allow element "html" here
    <html xml:lang="en" xmlns="http://www.w3.org/1999/xhtml" lang="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).

  • Error Line 19, Column 36: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta name="verify-v1" content="" >

    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 19, Column 1: start tag was here
    <meta name="verify-v1" content="" >
  • Error Line 84, Column 24: document type does not allow element "br" here
    		$('#yuk').html('<br /><img src="http://downvids.net/yukleniyor.gif" /> <font …

    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 84, Column 72: required attribute "alt" not specified
    …"http://downvids.net/yukleniyor.gif" /> <font color="#FFFFFF">Loading ...</fon…

    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 84, Column 72: document type does not allow element "img" here
    …"http://downvids.net/yukleniyor.gif" /> <font color="#FFFFFF">Loading ...</fon…

    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 84, Column 86: there is no attribute "color"
    …://downvids.net/yukleniyor.gif" /> <font color="#FFFFFF">Loading ...</font> ');

    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 84, Column 95: element "font" undefined
    …://downvids.net/yukleniyor.gif" /> <font color="#FFFFFF">Loading ...</font> ');

    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 164, Column 42: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    <div style="margin-left:100%;float:left;">

    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 165, Column 63: required attribute "type" not specified
    …ect.facebook.net/en_US/all.js#xfbml=1"></script><fb:like href="http://www.face…

    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 165, Column 87: there is no attribute "href"
    …ll.js#xfbml=1"></script><fb:like href="http://www.facebook.com/pages/Download-…

    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 165, Column 158: there is no attribute "layout"
    …wnload-Videos/186942371340141" layout="box_count" show_faces="false" width="20…

    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 165, Column 181: there is no attribute "show_faces"
    …340141" layout="box_count" show_faces="false" width="200" font="lucida grande"…

    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 165, Column 195: there is no attribute "width"
    …="box_count" show_faces="false" width="200" font="lucida grande"></fb:like></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 165, Column 206: there is no attribute "font"
    …box_count" show_faces="false" width="200" font="lucida grande"></fb:like></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 165, Column 221: element "fb:like" undefined
    …box_count" show_faces="false" width="200" font="lucida grande"></fb:like></div>

    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 179, Column 150: end tag for "input" omitted, but OMITTAG NO was specified
    …ty_token" value="c9122443e71d035817e319b1d5845eacbb112fb9" type="hidden"></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 179, Column 49: start tag was here
    …iv style="margin: 0pt; padding: 0pt;"><input name="authenticity_token" value="…
  • Error Line 189, Column 103: end tag for "input" omitted, but OMITTAG NO was specified
    …="home_search_q" size="40" name="arama" accesskey="/" tabindex="1" type="text">

    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 189, Column 15: start tag was here
                  <input id="home_search_q" size="40" name="arama" accesskey="/" ta…
  • Error Line 191, Column 109: end tag for "input" omitted, but OMITTAG NO was specified
    …mit" name="gonder" id="home_search_submit" class="submit" value=" DOWNLOAD !"> 

    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 191, Column 15: start tag was here
                  <input type="submit" name="gonder" id="home_search_submit" class=…
  • Error Line 193, Column 21: element "center" undefined
                 <center>

    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 196, Column 28: there is no attribute "border"
                   <img border="0" src="img/250_100_tur2.png">

    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 196, Column 58: required attribute "alt" not specified
                   <img border="0" src="img/250_100_tur2.png">

    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 196, Column 59: end tag for "img" omitted, but OMITTAG NO was specified
                   <img border="0" src="img/250_100_tur2.png">

    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 196, Column 16: start tag was here
                   <img border="0" src="img/250_100_tur2.png">
  • Warning Line 214, Column 71: cannot generate system identifier for general entity "s"
    …"http://mediaget.com/torrent.php?r="+ref+"&s="+mediaget_str+"&f="+mediaget_str;

    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 214, Column 71: general entity "s" not defined and no default entity
    …"http://mediaget.com/torrent.php?r="+ref+"&s="+mediaget_str+"&f="+mediaget_str;

    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 214, Column 72: reference not terminated by REFC delimiter
    …"http://mediaget.com/torrent.php?r="+ref+"&s="+mediaget_str+"&f="+mediaget_str;

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

  • Error Line 214, Column 72: reference to entity "s" for which no system identifier could be generated
    …"http://mediaget.com/torrent.php?r="+ref+"&s="+mediaget_str+"&f="+mediaget_str;

    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 214, Column 70: entity was defined here
    …"http://mediaget.com/torrent.php?r="+ref+"&s="+mediaget_str+"&f="+mediaget_str;
  • Warning Line 214, Column 90: cannot generate system identifier for general entity "f"
    …"http://mediaget.com/torrent.php?r="+ref+"&s="+mediaget_str+"&f="+mediaget_str;

    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 214, Column 90: general entity "f" not defined and no default entity
    …"http://mediaget.com/torrent.php?r="+ref+"&s="+mediaget_str+"&f="+mediaget_str;

    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 214, Column 91: reference not terminated by REFC delimiter
    …"http://mediaget.com/torrent.php?r="+ref+"&s="+mediaget_str+"&f="+mediaget_str;

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

  • Error Line 214, Column 91: reference to entity "f" for which no system identifier could be generated
    …"http://mediaget.com/torrent.php?r="+ref+"&s="+mediaget_str+"&f="+mediaget_str;

    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 214, Column 89: entity was defined here
    …"http://mediaget.com/torrent.php?r="+ref+"&s="+mediaget_str+"&f="+mediaget_str;
  • Error Line 226, Column 7: document type does not allow element "br" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
     <br />

    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 228, Column 16: document type does not allow element "span" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
     <span id="yuk"><font color="#E9E9E9">Exp:http://www.facebook.com/video/video.p…

    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 228, Column 38: element "font" undefined
     <span id="yuk"><font color="#E9E9E9">Exp:http://www.facebook.com/video/video.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 382, Column 114: end tag for "img" omitted, but OMITTAG NO was specified
    …src="images/icon-what.png" title="what download" height="16" width="16"><p></p>

    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 382, Column 20: start tag was here
          <span></span><img alt="Trend Info" src="images/icon-what.png" title="what…
  • Error Line 400, Column 8: element "center" undefined
    <center>    				<li><a href="http://facebook.com" name="#itsnotcheating" rel="n…

    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 400, Column 57: character "#" is not allowed in the value of attribute "name"
    …i><a href="http://facebook.com" name="#itsnotcheating" rel="nofollow" title="#…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Error Line 407, Column 9: end tag for "ul" which is not finished
        </ul>

    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 413, Column 12: element "center" undefined
        <center>   

    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 414, Column 26: there is no attribute "target"
     <a title="video" target="_blank" href="http://www.seyir.org">video</a>

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

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

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

  • Error Line 417, Column 9: end tag for "ul" which is not finished
        </ul>

    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 512, Column 15: no document element
    </body></html>

Visitor Analysis

Daily Visitor
  • 17.500 visits

In Page Analysis