youtubedownloadersite.com

YouTube Downloader lets you save and convert videos from YouTube and many other sites and play them on your computer, and best of all, it's free! Available for Windows & Mac ...

Display Widget for this domain on your website. Click Here
This data was last updated from 15-09-2013 12:26:32  (update).

Overview Info

  • Domain Name
    youtubedownloadersite.com
  • Favicon
  • Alexa Rank
    #11792
  • Google Page Rank
    PR 4
  • Ip Address
    95.211.187.90
  • Page Size
    50.5 KB
  • Images
    14 GIF, 2 JPG, 6 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 9 6 14 0 0

Website Meta Analysis



  • Title
    Youtube Downloader | YTD Downloader & Converter
  • Meta Keyword
    youtube download, freeware, youtube downloader, youtube video download, youtube videos download, download video youtube, download videos youtube, myspace video download, download video from youtube, download videos from youtube, convert video youtube, convert videos youtubes, download and convert video youtube, download and convert videos youtube, how to download video, how to download videos, how to download video from youtube, how to download videos from youtube
  • Meta Description
    YouTube Downloader lets you save and convert videos from YouTube and many other sites and play them on your computer, and best of all, it's free! Available for Windows & Mac

Technical Analysis



  • Webserver
    nginx/0.8.54
  • Ip Address
    95.211.187.90
  • Domain Age
    2 Years, 10 Months, 14 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: nginx/0.8.54
  • date: Sun, 15 Sep 2013 12:32:32 GMT
  • content-type: text/html
  • connection: keep-alive
  • x-powered-by: PHP/5.3.5-1ubuntu7.11
  • vary: Accept-Encoding
  • content-encoding: gzip
  • content-length: 12816
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
Domains by Proxy, Inc.
DomainsByProxy.com
15111 N. Hayden Rd., Ste 160, PMB 353
Scottsdale, Arizona 85260
United States
Domain Domain Name: YOUTUBEDOWNLOADERSITE.COM
Created: 16-Nov-10
Expires: 16-Nov-12
Updated: 16-Nov-10
Administrative Contact:
Private, Registration email
Domains by Proxy, Inc.
DomainsByProxy.com
15111 N. Hayden Rd., Ste 160, PMB 353
Scottsdale, Arizona 85260
United States
(480) 624-2599 Fax - (480) 624-2598
Technical Contact:
Private, Registration email
Domains by Proxy, Inc.
DomainsByProxy.com
15111 N. Hayden Rd., Ste 160, PMB 353
Scottsdale, Arizona 85260
United States
(480) 624-2599 Fax - (480) 624-2598
Name Servers:
NS57.DOMAINCONTROL.COM
NS58.DOMAINCONTROL.COM

0

DNS Analysis


DNS servers
ns57.domaincontrol.com [216.69.185.29]
ns58.domaincontrol.com [208.109.255.29]


DNS Records

Answer records
youtubedownloadersite.com A 62.212.88.31 3600s
youtubedownloadersite.com MX
preference: 10
exchange: mail.youtubedownloadersite.com
3600s
youtubedownloadersite.com NS  ns57.domaincontrol.com 3600s
youtubedownloadersite.com NS  ns58.domaincontrol.com 3600s
youtubedownloadersite.com TXT v=spf1 a mx ptr ~all 3600s
youtubedownloadersite.com SOA
server: ns57.domaincontrol.com
email: dns@jomax.net
serial: 2012112800
refresh: 28800
retry: 7200
expire: 604800
minimum ttl: 3600
3600s

Authority records

Additional records

IP 95.211.187.90 Analysis

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

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 172 Errors
  • 30 Warnings
Ratio Text/Html
  • 0.5490180918509355
Message Error
  • Warning Line 5, Column 38: character "&" is the first character of a delimiter but occurred as data
                <title>YouTube Converter & Free Downloader: Convert YouTube Videos …

    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 34, Column 628: cannot generate system identifier for general entity "u"
    …eoptimizer.com/j.php?a='+account_id+'&u='+encodeURIComponent(d.URL)+'&r='+Math…

    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 34, Column 628: general entity "u" not defined and no default entity
    …eoptimizer.com/j.php?a='+account_id+'&u='+encodeURIComponent(d.URL)+'&r='+Math…

    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 34, Column 629: reference not terminated by REFC delimiter
    …optimizer.com/j.php?a='+account_id+'&u='+encodeURIComponent(d.URL)+'&r='+Math.…

    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 34, Column 629: reference to entity "u" for which no system identifier could be generated
    …optimizer.com/j.php?a='+account_id+'&u='+encodeURIComponent(d.URL)+'&r='+Math.…

    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 34, Column 627: entity was defined here
    …teoptimizer.com/j.php?a='+account_id+'&u='+encodeURIComponent(d.URL)+'&r='+Mat…
  • Warning Line 34, Column 660: cannot generate system identifier for general entity "r"
    …_id+'&u='+encodeURIComponent(d.URL)+'&r='+Math.random());var a=d.createElement…

    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 34, Column 660: general entity "r" not defined and no default entity
    …_id+'&u='+encodeURIComponent(d.URL)+'&r='+Math.random());var a=d.createElement…

    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 34, Column 661: reference not terminated by REFC delimiter
    …id+'&u='+encodeURIComponent(d.URL)+'&r='+Math.random());var a=d.createElement(…

    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 34, Column 661: reference to entity "r" for which no system identifier could be generated
    …id+'&u='+encodeURIComponent(d.URL)+'&r='+Math.random());var a=d.createElement(…

    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 34, Column 659: entity was defined here
    …t_id+'&u='+encodeURIComponent(d.URL)+'&r='+Math.random());var a=d.createElemen…
  • Error Line 39, Column 25: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
                <body class=en>
  • Error Line 41, Column 11: required attribute "type" not specified
    			<script>(function(d, s, id) {

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 49, Column 18: "itemscope" is not a member of a group specified for any attribute
    <span  itemscope itemtype="http://schema.org/SoftwareApplication">
  • Error Line 49, Column 27: there is no attribute "itemtype"
    <span  itemscope itemtype="http://schema.org/SoftwareApplication">

    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 50, Column 20: there is no attribute "itemprop"
        <meta itemprop="name" content="YTD YouTube Converter & Downloader"/>

    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 50, Column 58: character "&" is the first character of a delimiter but occurred as data
        <meta itemprop="name" content="YTD YouTube Converter & Downloader"/>

    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 50, Column 72: document type does not allow element "meta" here
        <meta itemprop="name" content="YTD YouTube Converter & Downloader"/>

    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 51, Column 261: document type does not allow element "meta" here
    … Video (and many others) and convert YouTube videos to other video formats. "/>

    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 52, Column 48: document type does not allow element "meta" here
        <meta itemprop="fileSize" content="4.64MB"/>

    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 53, Column 100: document type does not allow element "meta" here
    …mage" content="http://www.youtubedownloadersite.com/images/ytd_schemaorg.jpg"/>

    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 54, Column 54: document type does not allow element "meta" here
        <meta itemprop="softwareVersion" content="3.9.6"/>

    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 55, Column 64: document type does not allow element "meta" here
        <meta itemprop="datePublished" content="December 06, 2012"/>

    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 57, Column 20: there is no attribute "itemprop"
        <span itemprop="offers" itemscope itemtype="http://schema.org/Offer">

    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 57, Column 39: "itemscope" is not a member of a group specified for any attribute
        <span itemprop="offers" itemscope itemtype="http://schema.org/Offer">
  • Error Line 58, Column 48: document type does not allow element "meta" here
            <meta itemprop="price" content="$0.00"/>

    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 59, Column 54: document type does not allow element "meta" here
            <meta itemprop="priceCurrency" content="USD"/>

    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 62, Column 40: "itemscope" is not a member of a group specified for any attribute
        <span itemprop="reviews" itemscope itemtype="http://schema.org/Review">
  • Error Line 63, Column 43: "itemscope" is not a member of a group specified for any attribute
    		<span itemprop="reviewRating" itemscope itemtype="http://schema.org/Rating">
  • Error Line 64, Column 44: document type does not allow element "meta" here
    		<meta itemprop="worstRating" content="1"/>

    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 65, Column 43: document type does not allow element "meta" here
    		<meta itemprop="bestRating" content="5"/>

    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 66, Column 46: document type does not allow element "meta" here
    		<meta itemprop="ratingValue" content="4.5"/>

    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 67, Column 45: "itemscope" is not a member of a group specified for any attribute
    		</span> <span itemprop="author" itemscope itemtype="http://schema.org/Person">
  • Error Line 68, Column 23: there is no attribute "rel"
                <meta rel="author" itemprop="name" content="CNET editor" />

    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 68, Column 71: document type does not allow element "meta" here
                <meta rel="author" itemprop="name" content="CNET editor" />

    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 72, Column 68: document type does not allow element "meta" here
        <meta itemprop="operatingSystems" content="Windows XP/Vista/7"/>

    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 73, Column 55: there is no attribute "href"
    …prop="softwareApplicationCategory" href="http://schema.org/OtherApplication" />

    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 73, Column 93: required attribute "content" not specified
    …prop="softwareApplicationCategory" href="http://schema.org/OtherApplication" />

    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 73, Column 93: document type does not allow element "meta" here
    …prop="softwareApplicationCategory" href="http://schema.org/OtherApplication" />

    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 74, Column 81: document type does not allow element "meta" here
    …  <meta itemprop="SoftwareApplicationSubCategory" content="Download Managers"/>

    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 76, Column 39: "itemscope" is not a member of a group specified for any attribute
        <span itemprop="author" itemscope itemtype="http://schema.org/Organization">
  • Error Line 77, Column 68: document type does not allow element "meta" here
            <meta itemprop="name" content="GreenTree Applications SRL"/>

    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 85, Column 53: character "&" is the first character of a delimiter but occurred as data
        <h1 style="margin-top: 32px;">YouTube Converter & Downloader</h1>

    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 91, Column 62: cannot generate system identifier for general entity "tid"
    …w.trialpay.com/productpage/?c=82754a7&tid=A7Dl2Al"><img border="0" src="http:/…

    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 91, Column 62: general entity "tid" not defined and no default entity
    …w.trialpay.com/productpage/?c=82754a7&tid=A7Dl2Al"><img border="0" src="http:/…

    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 91, Column 65: reference not terminated by REFC delimiter
    …rialpay.com/productpage/?c=82754a7&tid=A7Dl2Al"><img border="0" src="http://ww…

    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 91, Column 65: reference to external entity in attribute value
    …rialpay.com/productpage/?c=82754a7&tid=A7Dl2Al"><img border="0" src="http://ww…

    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 91, Column 65: reference to entity "tid" for which no system identifier could be generated
    …rialpay.com/productpage/?c=82754a7&tid=A7Dl2Al"><img border="0" src="http://ww…

    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 91, Column 61: entity was defined here
    …ww.trialpay.com/productpage/?c=82754a7&tid=A7Dl2Al"><img border="0" src="http:…
  • Warning Line 91, Column 129: cannot generate system identifier for general entity "ri"
    …src="http://www.trialpay.com/mi/?rc=v&ri=11895947&p=Vt3jA37r&t=A7Dl2Al&type=im…

    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 91, Column 129: general entity "ri" not defined and no default entity
    …src="http://www.trialpay.com/mi/?rc=v&ri=11895947&p=Vt3jA37r&t=A7Dl2Al&type=im…

    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 91, Column 131: reference not terminated by REFC delimiter
    …c="http://www.trialpay.com/mi/?rc=v&ri=11895947&p=Vt3jA37r&t=A7Dl2Al&type=img"…

    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 91, Column 131: reference to external entity in attribute value
    …c="http://www.trialpay.com/mi/?rc=v&ri=11895947&p=Vt3jA37r&t=A7Dl2Al&type=img"…

    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 91, Column 131: reference to entity "ri" for which no system identifier could be generated
    …c="http://www.trialpay.com/mi/?rc=v&ri=11895947&p=Vt3jA37r&t=A7Dl2Al&type=img"…

    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 91, Column 128: entity was defined here
    … src="http://www.trialpay.com/mi/?rc=v&ri=11895947&p=Vt3jA37r&t=A7Dl2Al&type=i…
  • Warning Line 91, Column 141: cannot generate system identifier for general entity "p"
    …p://www.trialpay.com/mi/?rc=v&ri=11895947&p=Vt3jA37r&t=A7Dl2Al&type=img" /></a>

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

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

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

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

  • Error Line 91, Column 141: general entity "p" not defined and no default entity
    …p://www.trialpay.com/mi/?rc=v&ri=11895947&p=Vt3jA37r&t=A7Dl2Al&type=img" /></a>

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

  • Warning Line 91, Column 142: reference not terminated by REFC delimiter
    …p://www.trialpay.com/mi/?rc=v&ri=11895947&p=Vt3jA37r&t=A7Dl2Al&type=img" /></a>

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

  • Warning Line 91, Column 142: reference to external entity in attribute value
    …p://www.trialpay.com/mi/?rc=v&ri=11895947&p=Vt3jA37r&t=A7Dl2Al&type=img" /></a>

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

  • Error Line 91, Column 142: reference to entity "p" for which no system identifier could be generated
    …p://www.trialpay.com/mi/?rc=v&ri=11895947&p=Vt3jA37r&t=A7Dl2Al&type=img" /></a>

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

  • Info Line 91, Column 140: entity was defined here
    …p://www.trialpay.com/mi/?rc=v&ri=11895947&p=Vt3jA37r&t=A7Dl2Al&type=img" /></a>
  • Warning Line 91, Column 152: cannot generate system identifier for general entity "t"
    …p://www.trialpay.com/mi/?rc=v&ri=11895947&p=Vt3jA37r&t=A7Dl2Al&type=img" /></a>

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

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

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

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

  • Error Line 91, Column 152: general entity "t" not defined and no default entity
    …p://www.trialpay.com/mi/?rc=v&ri=11895947&p=Vt3jA37r&t=A7Dl2Al&type=img" /></a>

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

  • Warning Line 91, Column 153: reference not terminated by REFC delimiter
    …p://www.trialpay.com/mi/?rc=v&ri=11895947&p=Vt3jA37r&t=A7Dl2Al&type=img" /></a>

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

  • Warning Line 91, Column 153: reference to external entity in attribute value
    …p://www.trialpay.com/mi/?rc=v&ri=11895947&p=Vt3jA37r&t=A7Dl2Al&type=img" /></a>

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

  • Error Line 91, Column 153: reference to entity "t" for which no system identifier could be generated
    …p://www.trialpay.com/mi/?rc=v&ri=11895947&p=Vt3jA37r&t=A7Dl2Al&type=img" /></a>

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

  • Info Line 91, Column 151: entity was defined here
    …p://www.trialpay.com/mi/?rc=v&ri=11895947&p=Vt3jA37r&t=A7Dl2Al&type=img" /></a>
  • Warning Line 91, Column 162: cannot generate system identifier for general entity "type"
    …p://www.trialpay.com/mi/?rc=v&ri=11895947&p=Vt3jA37r&t=A7Dl2Al&type=img" /></a>

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

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

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

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

  • Error Line 91, Column 162: general entity "type" not defined and no default entity
    …p://www.trialpay.com/mi/?rc=v&ri=11895947&p=Vt3jA37r&t=A7Dl2Al&type=img" /></a>

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

  • Warning Line 91, Column 166: reference not terminated by REFC delimiter
    …p://www.trialpay.com/mi/?rc=v&ri=11895947&p=Vt3jA37r&t=A7Dl2Al&type=img" /></a>

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

  • Warning Line 91, Column 166: reference to external entity in attribute value
    …p://www.trialpay.com/mi/?rc=v&ri=11895947&p=Vt3jA37r&t=A7Dl2Al&type=img" /></a>

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

  • Error Line 91, Column 166: reference to entity "type" for which no system identifier could be generated
    …p://www.trialpay.com/mi/?rc=v&ri=11895947&p=Vt3jA37r&t=A7Dl2Al&type=img" /></a>

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

  • Info Line 91, Column 161: entity was defined here
    …p://www.trialpay.com/mi/?rc=v&ri=11895947&p=Vt3jA37r&t=A7Dl2Al&type=img" /></a>
  • Error Line 91, Column 173: required attribute "alt" not specified
    …p://www.trialpay.com/mi/?rc=v&ri=11895947&p=Vt3jA37r&t=A7Dl2Al&type=img" /></a>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 98, Column 39: there is no attribute "href"
    	  <div class="fb-like"><fb:like href="https://www.facebook.com/YTDYouTubeDownl…

    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 98, Column 101: there is no attribute "send"
    …m/YTDYouTubeDownloaderConverter" send="false" layout="button_count" width="50"…

    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 98, Column 116: there is no attribute "layout"
    …nloaderConverter" send="false" layout="button_count" width="50" show_faces="fa…

    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 98, Column 137: there is no attribute "width"
    …nd="false" layout="button_count" width="50" show_faces="false"></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 98, Column 153: there is no attribute "show_faces"
    …nd="false" layout="button_count" width="50" show_faces="false"></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 98, Column 160: element "fb:like" undefined
    …nd="false" layout="button_count" width="50" show_faces="false"></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 100, Column 90: there is no attribute "addthis:url"
    …tyle addthis_32x32_style" addthis:url="http://www.youtubedownloadersite.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 136, Column 23: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    							<li>Facebook<li>        

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

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

  • Error Line 137, Column 11: 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 136, Column 20: start tag was here
    							<li>Facebook<li>        
  • Error Line 137, Column 11: 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 136, Column 8: start tag was here
    							<li>Facebook<li>        
  • Error Line 141, Column 70: there is no attribute "onClick"
    …te.html" class="freedown_btn" onClick="_gaq.push(['_trackEvent', 'downloads', …

    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 145, Column 98: there is no attribute "onSubmit"
    …gi-bin/webscr" method="post" onSubmit="_gaq.push(['_trackEvent', 'downloads', …

    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 145, Column 335: end tag for "input" omitted, but OMITTAG NO was specified
    …ame" value="YTD Video Downloader PRO"><input type="hidden" name="business" val…

    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 145, Column 264: start tag was here
    …]); return true;" class="paypal-btn "><input type="hidden" name="item_name" va…
  • Error Line 145, Column 402: end tag for "input" omitted, but OMITTAG NO was specified
    …siness" value="premiumapps@yahoo.com"><input type="hidden" name="cmd" value="_…

    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 145, Column 335: start tag was here
    …ame" value="YTD Video Downloader PRO"><input type="hidden" name="business" val…
  • Error Line 145, Column 450: end tag for "input" omitted, but OMITTAG NO was specified
    …e="hidden" name="cmd" value="_xclick"><input type="hidden" name="return" value…

    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 145, Column 402: start tag was here
    …siness" value="premiumapps@yahoo.com"><input type="hidden" name="cmd" value="_…
  • Error Line 145, Column 547: end tag for "input" omitted, but OMITTAG NO was specified
    …edownloadersite.com/thankyoupro.html"><input type="hidden" name="discount_rate…

    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 145, Column 450: start tag was here
    …e="hidden" name="cmd" value="_xclick"><input type="hidden" name="return" value…
  • Error Line 145, Column 599: end tag for "input" omitted, but OMITTAG NO was specified
    …idden" name="discount_rate" value="0"><input type="hidden" name="discount_rate…

    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 145, Column 547: start tag was here
    …edownloadersite.com/thankyoupro.html"><input type="hidden" name="discount_rate…
  • Error Line 145, Column 653: end tag for "input" omitted, but OMITTAG NO was specified
    …den" name="discount_rate2" value="25"><input type="hidden" name="discount_num"…

    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 145, Column 599: start tag was here
    …idden" name="discount_rate" value="0"><input type="hidden" name="discount_rate…
  • Error Line 145, Column 705: end tag for "input" omitted, but OMITTAG NO was specified
    …idden" name="discount_num" value="50"><input type="hidden" name="notify_url" v…

    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 145, Column 653: start tag was here
    …den" name="discount_rate2" value="25"><input type="hidden" name="discount_num"…
  • Error Line 145, Column 801: end tag for "input" omitted, but OMITTAG NO was specified
    …outubedownloadersite.com/api/ipn.php"><input type="hidden" name="amount" value…

    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 145, Column 705: start tag was here
    …idden" name="discount_num" value="50"><input type="hidden" name="notify_url" v…
  • Error Line 145, Column 850: end tag for "input" omitted, but OMITTAG NO was specified
    …="hidden" name="amount" value="29.90"><input type="hidden" name="currency_code…

    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 145, Column 801: start tag was here
    …outubedownloadersite.com/api/ipn.php"><input type="hidden" name="amount" value…
  • Error Line 145, Column 904: end tag for "input" omitted, but OMITTAG NO was specified
    …den" name="currency_code" value="USD"><input type="hidden" name="undefined_qua…

    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 145, Column 850: start tag was here
    …="hidden" name="amount" value="29.90"><input type="hidden" name="currency_code…
  • Error Line 145, Column 961: end tag for "input" omitted, but OMITTAG NO was specified
    …" name="undefined_quantity" value="1"><input type="hidden" name="custom" value…

    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 145, Column 904: start tag was here
    …den" name="currency_code" value="USD"><input type="hidden" name="undefined_qua…
  • Error Line 145, Column 1007: end tag for "input" omitted, but OMITTAG NO was specified
    …ype="hidden" name="custom" value="US"><input type="submit" class="buypro-link"…

    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 145, Column 961: start tag was here
    …" name="undefined_quantity" value="1"><input type="hidden" name="custom" value…
  • Error Line 145, Column 1071: there is no attribute "border"
    …ut type="submit" class="buypro-link" value="Buy Now" border="0" name="submit" >

    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 145, Column 1090: end tag for "input" omitted, but OMITTAG NO was specified
    …ut type="submit" class="buypro-link" value="Buy Now" border="0" name="submit" >

    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 145, Column 1007: start tag was here
    …ype="hidden" name="custom" value="US"><input type="submit" class="buypro-link"…
  • Error Line 150, Column 21: ID "paypalf" already defined
    										<form id="paypalf" action="https://www.paypal.com/cgi-bin/webscr" met…

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 145, Column 19: ID "paypalf" first defined here
    								<form id="paypalf" action="https://www.paypal.com/cgi-bin/webscr" metho…
  • Error Line 150, Column 255: document type does not allow element "form" here; missing one of "object", "applet", "map", "iframe", "ins", "del" start-tag
    …']); return true;" class="paypal-btn "><input type="hidden" name="item_name" v…

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

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

  • Error Line 150, Column 327: end tag for "input" omitted, but OMITTAG NO was specified
    …ame" value="YTD Video Downloader PRO"><input type="hidden" name="business" val…

    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 150, Column 256: start tag was here
    …]); return true;" class="paypal-btn "><input type="hidden" name="item_name" va…
  • Error Line 150, Column 394: end tag for "input" omitted, but OMITTAG NO was specified
    …siness" value="premiumapps@yahoo.com"><input type="hidden" name="cmd" value="_…

    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 150, Column 327: start tag was here
    …ame" value="YTD Video Downloader PRO"><input type="hidden" name="business" val…
  • Error Line 150, Column 442: end tag for "input" omitted, but OMITTAG NO was specified
    …e="hidden" name="cmd" value="_xclick"><input type="hidden" name="return" value…

    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 150, Column 394: start tag was here
    …siness" value="premiumapps@yahoo.com"><input type="hidden" name="cmd" value="_…
  • Error Line 150, Column 539: end tag for "input" omitted, but OMITTAG NO was specified
    …edownloadersite.com/thankyoupro.html"><input type="hidden" name="discount_rate…

    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 150, Column 442: start tag was here
    …e="hidden" name="cmd" value="_xclick"><input type="hidden" name="return" value…
  • Error Line 150, Column 591: end tag for "input" omitted, but OMITTAG NO was specified
    …idden" name="discount_rate" value="0"><input type="hidden" name="discount_rate…

    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 150, Column 539: start tag was here
    …edownloadersite.com/thankyoupro.html"><input type="hidden" name="discount_rate…
  • Error Line 150, Column 645: end tag for "input" omitted, but OMITTAG NO was specified
    …den" name="discount_rate2" value="25"><input type="hidden" name="discount_num"…

    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 150, Column 591: start tag was here
    …idden" name="discount_rate" value="0"><input type="hidden" name="discount_rate…
  • Error Line 150, Column 697: end tag for "input" omitted, but OMITTAG NO was specified
    …idden" name="discount_num" value="50"><input type="hidden" name="notify_url" v…

    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 150, Column 645: start tag was here
    …den" name="discount_rate2" value="25"><input type="hidden" name="discount_num"…
  • Error Line 150, Column 793: end tag for "input" omitted, but OMITTAG NO was specified
    …outubedownloadersite.com/api/ipn.php"><input type="hidden" name="amount" value…

    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 150, Column 697: start tag was here
    …idden" name="discount_num" value="50"><input type="hidden" name="notify_url" v…
  • Error Line 150, Column 842: end tag for "input" omitted, but OMITTAG NO was specified
    …="hidden" name="amount" value="29.90"><input type="hidden" name="currency_code…

    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 150, Column 793: start tag was here
    …outubedownloadersite.com/api/ipn.php"><input type="hidden" name="amount" value…
  • Error Line 150, Column 896: end tag for "input" omitted, but OMITTAG NO was specified
    …den" name="currency_code" value="USD"><input type="hidden" name="undefined_qua…

    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 150, Column 842: start tag was here
    …="hidden" name="amount" value="29.90"><input type="hidden" name="currency_code…
  • Error Line 150, Column 953: end tag for "input" omitted, but OMITTAG NO was specified
    …" name="undefined_quantity" value="1"><input type="hidden" name="custom" value…

    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 150, Column 896: start tag was here
    …den" name="currency_code" value="USD"><input type="hidden" name="undefined_qua…
  • Error Line 150, Column 999: end tag for "input" omitted, but OMITTAG NO was specified
    …ype="hidden" name="custom" value="US"><div onclick="javascript:this.parentNode…

    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 150, Column 953: start tag was here
    …" name="undefined_quantity" value="1"><input type="hidden" name="custom" value…
  • Warning Line 154, Column 81: cannot generate system identifier for general entity "QTY"
    ….com/order/checkout.php?PRODS=4549027&QTY=1&CART=2" onClick="_gaq.push(['_trac…

    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 154, Column 81: general entity "QTY" not defined and no default entity
    ….com/order/checkout.php?PRODS=4549027&QTY=1&CART=2" onClick="_gaq.push(['_trac…

    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 154, Column 84: reference not terminated by REFC delimiter
    …m/order/checkout.php?PRODS=4549027&QTY=1&CART=2" onClick="_gaq.push(['_trackEv…

    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 154, Column 84: reference to external entity in attribute value
    …m/order/checkout.php?PRODS=4549027&QTY=1&CART=2" onClick="_gaq.push(['_trackEv…

    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 154, Column 84: reference to entity "QTY" for which no system identifier could be generated
    …m/order/checkout.php?PRODS=4549027&QTY=1&CART=2" onClick="_gaq.push(['_trackEv…

    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 154, Column 80: entity was defined here
    …e.com/order/checkout.php?PRODS=4549027&QTY=1&CART=2" onClick="_gaq.push(['_tra…
  • Warning Line 154, Column 87: cannot generate system identifier for general entity "CART"
    …rder/checkout.php?PRODS=4549027&QTY=1&CART=2" onClick="_gaq.push(['_trackEvent…

    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 154, Column 87: general entity "CART" not defined and no default entity
    …rder/checkout.php?PRODS=4549027&QTY=1&CART=2" onClick="_gaq.push(['_trackEvent…

    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 154, Column 91: reference not terminated by REFC delimiter
    …/checkout.php?PRODS=4549027&QTY=1&CART=2" onClick="_gaq.push(['_trackEvent', '…

    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 154, Column 91: reference to external entity in attribute value
    …/checkout.php?PRODS=4549027&QTY=1&CART=2" onClick="_gaq.push(['_trackEvent', '…

    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 154, Column 91: reference to entity "CART" for which no system identifier could be generated
    …/checkout.php?PRODS=4549027&QTY=1&CART=2" onClick="_gaq.push(['_trackEvent', '…

    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 154, Column 86: entity was defined here
    …order/checkout.php?PRODS=4549027&QTY=1&CART=2" onClick="_gaq.push(['_trackEven…
  • Error Line 164, Column 42: required attribute "alt" not specified
    						<img src="/images/cnet-badge.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 167, Column 247: required attribute "alt" not specified
    …icks/download/screenshot']);"><img src="/images/screen-download-btn.jpg" /></a>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 168, Column 46: required attribute "alt" not specified
    						<img src="/images/new-ytd-screen.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>.

  • Warning Line 250, Column 41: character "&" is the first character of a delimiter but occurred as data
    …		- Download playlists (All versions) & Download multiple videos in the same t…

    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 349, Column 92: end tag for "br" omitted, but OMITTAG NO was specified
    …Copyright &copy; 2012 GreenTree Applications SRL. All rights reserved. <br><br>

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

  • Info Line 349, Column 88: start tag was here
    …Copyright &copy; 2012 GreenTree Applications SRL. All rights reserved. <br><br>
  • Error Line 349, Column 96: end tag for "br" omitted, but OMITTAG NO was specified
    …Copyright &copy; 2012 GreenTree Applications SRL. All rights reserved. <br><br>

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

  • Info Line 349, Column 92: start tag was here
    …Copyright &copy; 2012 GreenTree Applications SRL. All rights reserved. <br><br>

Visitor Analysis

Daily Visitor
  • 11.200 visits

In Page Analysis