Free online Word to PDF converter converts Microsoft Word to Adobe Acrobat PDF ...

convertonlinefree.com
  • Domain Name
    convertonlinefree.com
  • Favicon
  • Google Page Rank
    3
  • Alexa Rank
    #32270
  • Page Size
    43.7 KB
  • Ip Address
    64.187.226.10
  • Heading
    H1: 1, H2: 1, H3: 0, H4: 5, H5: 11, H6: 0
  • Images
    8 GIF, 2 JPG, 11 PNG

Website Meta Analysis

  • Title
    Convert DOC to PDF Online | Convert DOCX to PDF Online | Convert Word to PDF Online | Free online converter
  • Meta Keyword
    100%,free,online,file,convert,converter,conversion,word,pdf,doc,docx,document,zip,.pdf,.doc,.docx,.zip
  • Meta Description
    Free online Word to PDF converter converts Microsoft Word to Adobe Acrobat PDF

Technical Analysis

  • Webserver
    Microsoft-IIS/8.0
  • Ip Address
    64.187.226.10
  • Domain Age
    2 Years, 5 Months, 3 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • cache-control: private
  • content-type: text/html; charset=utf-8
  • content-encoding: gzip
  • vary: Accept-Encoding
  • server: Microsoft-IIS/8.0
  • x-aspnet-version: 4.0.30319
  • x-powered-by: ASP.NET
  • date: Thu, 05 Sep 2013 12:11:08 GMT
  • content-length: 13419
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain name: convertonlinefree.com

Registrant Contact:
WhoisGuard
WhoisGuard Protected ()

Fax:
11400 W. Olympic Blvd. Suite 200
Los Angeles, CA 90064
US

Administrative Contact:
WhoisGuard
WhoisGuard Protected ( email )
+1.6613102107
Fax: +1.6613102107
11400 W. Olympic Blvd. Suite 200
Los Angeles, CA 90064
US

Technical Contact:
WhoisGuard
WhoisGuard Protected ( email )
+1.6613102107
Fax: +1.6613102107
11400 W. Olympic Blvd. Suite 200
Los Angeles, CA 90064
US

Status: Locked

Name Servers:
dns1.name-services.com
dns2.name-services.com
dns3.name-services.com
dns4.name-services.com
dns5.name-services.com

Creation date: 17 Mar 2011 21:05:00
Expiration date: 17 Mar 2020 16:05:00

DNS Analysis


DNS servers
dns1.name-services.com [98.124.192.1]
dns2.name-services.com [98.124.197.1]
dns3.name-services.com [98.124.193.1]
dns4.name-services.com [98.124.194.1]
dns5.name-services.com [98.124.196.1]


DNS Records

Answer records
convertonlinefree.com SOA
server: dns1.name-services.com
email: info@name-services.com
serial: 2002050701
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 3600
1800s
convertonlinefree.com NS  dns5.name-services.com 3600s
convertonlinefree.com NS  dns1.name-services.com 3600s
convertonlinefree.com NS  dns3.name-services.com 3600s
convertonlinefree.com NS  dns4.name-services.com 3600s
convertonlinefree.com A 199.96.86.90 1800s
convertonlinefree.com NS  dns2.name-services.com 3600s

Authority records

Additional records

IP 64.187.226.10 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 36 Errors
  • 33 Warnings
Ratio Text/Html
  • 0.4728390920272839
Message Error
  • Error Line 37, Column 96: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …en" name="__VIEWSTATE" id="__VIEWSTATE" value="/wEPDwULLTEzNDgzNTIwMDFkZA==" />

    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 154, Column 66: there is no attribute "target"
    …                     <a style="text-decoration: none;" target="_self" href="/">

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

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

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

  • Error Line 167, Column 36: there is no attribute "width"
                <td valign="top" width="166px">

    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 191, Column 28: there is no attribute "align"
                    <div align="left">

    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 284, Column 148: there is no attribute "border"
    …tl00$MainContent$fu" id="MainContent_fu" class="button" size="50" border="1" />

    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 285, Column 417: there is no attribute "Title"
    …tent_btnConvert" class="button" Title="Convert the file and return output PDF …

    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 313, Column 119: ID "aDocumentsToPDF" already defined
    …please, use the following link <a id="aDocumentsToPDF" title="Convert file(s) …

    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 57, Column 48: ID "aDocumentsToPDF" first defined here
    …                               <a id="aDocumentsToPDF" title="Convert file(s) …
  • Error Line 315, Column 152: ID "aImagesToPDF" already defined
    …please, use the following link <a id="aImagesToPDF" title="Convert image to PD…

    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 67, Column 48: ID "aImagesToPDF" first defined here
    …                               <a id="aImagesToPDF" title="Convert image to PD…
  • Error Line 318, Column 121: ID "aPDFToTXT" already defined
    …F, please, use the following link <a id="aPDFToTXT" title="Convert PDF to text"

    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 77, Column 48: ID "aPDFToTXT" first defined here
    …                                  <a id="aPDFToTXT" title="Convert PDF to TXT" 
  • Error Line 324, Column 99: ID "aDocumentsToFB2" already defined
    …        use the following link <a id="aDocumentsToFB2" title="Convert to FB2" …

    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 95, Column 48: ID "aDocumentsToFB2" first defined here
    …                                <a id="aDocumentsToFB2" title="Convert to DB2" 
  • Error Line 326, Column 130: ID "aConvertImage" already defined
    …ats, please, use the following link <a id="aConvertImage" title="Convert image"

    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 115, Column 48: ID "aConvertImage" first defined here
    …                               <a id="aConvertImage" title="Convert image to a…
  • Error Line 390, Column 96: there is no attribute "color"
    …      <span id="MainContent_lblErrorZip"><font color="Red"></font></span></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 390, Column 101: element "font" undefined
    …      <span id="MainContent_lblErrorZip"><font color="Red"></font></span></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).
  • Warning Line 436, Column 127: cannot generate system identifier for general entity "v"
    …l="nofollow" href="http://go.microsoft.com/fwlink/?LinkID=149156&v=4.0.50826.0"

    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 436, Column 127: general entity "v" not defined and no default entity
    …l="nofollow" href="http://go.microsoft.com/fwlink/?LinkID=149156&v=4.0.50826.0"

    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 436, Column 128: reference not terminated by REFC delimiter
    …l="nofollow" href="http://go.microsoft.com/fwlink/?LinkID=149156&v=4.0.50826.0"

    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 436, Column 128: reference to external entity in attribute value
    …l="nofollow" href="http://go.microsoft.com/fwlink/?LinkID=149156&v=4.0.50826.0"

    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 436, Column 128: reference to entity "v" for which no system identifier could be generated
    …l="nofollow" href="http://go.microsoft.com/fwlink/?LinkID=149156&v=4.0.50826.0"

    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 436, Column 126: entity was defined here
    …l="nofollow" href="http://go.microsoft.com/fwlink/?LinkID=149156&v=4.0.50826.0"
  • Warning Line 575, Column 134: cannot generate system identifier for general entity "bkmk"
    …/www.google.com/bookmarks/mark?op=add&bkmk=http://convertonlinefree.com&title=…

    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 575, Column 134: general entity "bkmk" not defined and no default entity
    …/www.google.com/bookmarks/mark?op=add&bkmk=http://convertonlinefree.com&title=…

    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 575, Column 138: reference not terminated by REFC delimiter
    ….google.com/bookmarks/mark?op=add&bkmk=http://convertonlinefree.com&title=Free…

    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 575, Column 138: reference to external entity in attribute value
    ….google.com/bookmarks/mark?op=add&bkmk=http://convertonlinefree.com&title=Free…

    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 575, Column 138: reference to entity "bkmk" for which no system identifier could be generated
    ….google.com/bookmarks/mark?op=add&bkmk=http://convertonlinefree.com&title=Free…

    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 575, Column 133: entity was defined here
    …//www.google.com/bookmarks/mark?op=add&bkmk=http://convertonlinefree.com&title…
  • Warning Line 575, Column 168: cannot generate system identifier for general entity "title"
    …arks/mark?op=add&bkmk=http://convertonlinefree.com&title=Free online converter"

    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 575, Column 168: general entity "title" not defined and no default entity
    …arks/mark?op=add&bkmk=http://convertonlinefree.com&title=Free online converter"

    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 575, Column 173: reference not terminated by REFC delimiter
    …arks/mark?op=add&bkmk=http://convertonlinefree.com&title=Free online converter"

    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 575, Column 173: reference to external entity in attribute value
    …arks/mark?op=add&bkmk=http://convertonlinefree.com&title=Free online converter"

    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 575, Column 173: reference to entity "title" for which no system identifier could be generated
    …arks/mark?op=add&bkmk=http://convertonlinefree.com&title=Free online converter"

    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 575, Column 167: entity was defined here
    …arks/mark?op=add&bkmk=http://convertonlinefree.com&title=Free online converter"
  • Error Line 577, Column 135: there is no attribute "border"
    …google.gif" alt="Google Bookmarks" width="20px" height="20px" border="0" /></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.

  • Warning Line 581, Column 127: cannot generate system identifier for general entity "t"
    …savebm?u=http://convertonlinefree.com&t=Free online converter&opener=bm&ei=UTF…

    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 581, Column 127: general entity "t" not defined and no default entity
    …savebm?u=http://convertonlinefree.com&t=Free online converter&opener=bm&ei=UTF…

    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 581, Column 128: reference not terminated by REFC delimiter
    …avebm?u=http://convertonlinefree.com&t=Free online converter&opener=bm&ei=UTF-…

    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 581, Column 128: reference to external entity in attribute value
    …avebm?u=http://convertonlinefree.com&t=Free online converter&opener=bm&ei=UTF-…

    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 581, Column 128: reference to entity "t" for which no system identifier could be generated
    …avebm?u=http://convertonlinefree.com&t=Free online converter&opener=bm&ei=UTF-…

    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 581, Column 126: entity was defined here
    …/savebm?u=http://convertonlinefree.com&t=Free online converter&opener=bm&ei=UT…
  • Warning Line 581, Column 151: cannot generate system identifier for general entity "opener"
    …nlinefree.com&t=Free online converter&opener=bm&ei=UTF-8&d=Free online convert…

    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 581, Column 151: general entity "opener" not defined and no default entity
    …nlinefree.com&t=Free online converter&opener=bm&ei=UTF-8&d=Free online convert…

    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 581, Column 157: reference not terminated by REFC delimiter
    …inefree.com&t=Free online converter&opener=bm&ei=UTF-8&d=Free online converter"

    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 581, Column 157: reference to external entity in attribute value
    …inefree.com&t=Free online converter&opener=bm&ei=UTF-8&d=Free online converter"

    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 581, Column 157: reference to entity "opener" for which no system identifier could be generated
    …inefree.com&t=Free online converter&opener=bm&ei=UTF-8&d=Free online converter"

    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 581, Column 150: entity was defined here
    …onlinefree.com&t=Free online converter&opener=bm&ei=UTF-8&d=Free online conver…
  • Warning Line 581, Column 161: cannot generate system identifier for general entity "ei"
    …inefree.com&t=Free online converter&opener=bm&ei=UTF-8&d=Free online converter"

    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 581, Column 161: general entity "ei" not defined and no default entity
    …inefree.com&t=Free online converter&opener=bm&ei=UTF-8&d=Free online converter"

    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 581, Column 163: reference not terminated by REFC delimiter
    …inefree.com&t=Free online converter&opener=bm&ei=UTF-8&d=Free online converter"

    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 581, Column 163: reference to external entity in attribute value
    …inefree.com&t=Free online converter&opener=bm&ei=UTF-8&d=Free online converter"

    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 581, Column 163: reference to entity "ei" for which no system identifier could be generated
    …inefree.com&t=Free online converter&opener=bm&ei=UTF-8&d=Free online converter"

    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 581, Column 160: entity was defined here
    …inefree.com&t=Free online converter&opener=bm&ei=UTF-8&d=Free online converter"
  • Warning Line 581, Column 170: cannot generate system identifier for general entity "d"
    …inefree.com&t=Free online converter&opener=bm&ei=UTF-8&d=Free online converter"

    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 581, Column 170: general entity "d" not defined and no default entity
    …inefree.com&t=Free online converter&opener=bm&ei=UTF-8&d=Free online converter"

    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 581, Column 171: reference not terminated by REFC delimiter
    …inefree.com&t=Free online converter&opener=bm&ei=UTF-8&d=Free online converter"

    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 581, Column 171: reference to external entity in attribute value
    …inefree.com&t=Free online converter&opener=bm&ei=UTF-8&d=Free online converter"

    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 581, Column 171: reference to entity "d" for which no system identifier could be generated
    …inefree.com&t=Free online converter&opener=bm&ei=UTF-8&d=Free online converter"

    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 581, Column 169: entity was defined here
    …inefree.com&t=Free online converter&opener=bm&ei=UTF-8&d=Free online converter"
  • Warning Line 593, Column 122: cannot generate system identifier for general entity "event"
    …om/update.bml?subject=Free online converter&event=http://convertonlinefree.com"

    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 593, Column 122: general entity "event" not defined and no default entity
    …om/update.bml?subject=Free online converter&event=http://convertonlinefree.com"

    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 593, Column 127: reference not terminated by REFC delimiter
    …om/update.bml?subject=Free online converter&event=http://convertonlinefree.com"

    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 593, Column 127: reference to external entity in attribute value
    …om/update.bml?subject=Free online converter&event=http://convertonlinefree.com"

    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 593, Column 127: reference to entity "event" for which no system identifier could be generated
    …om/update.bml?subject=Free online converter&event=http://convertonlinefree.com"

    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 593, Column 121: entity was defined here
    …om/update.bml?subject=Free online converter&event=http://convertonlinefree.com"
  • Warning Line 596, Column 118: reference not terminated by REFC delimiter
    …elicious.com/save?url=http://convertonlinefree.com&title=Free online converter"

    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 596, Column 118: reference to external entity in attribute value
    …elicious.com/save?url=http://convertonlinefree.com&title=Free online converter"

    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 596, Column 118: reference to entity "title" for which no system identifier could be generated
    …elicious.com/save?url=http://convertonlinefree.com&title=Free online converter"

    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 575, Column 167: entity was defined here
    …arks/mark?op=add&bkmk=http://convertonlinefree.com&title=Free online converter"
  • Warning Line 599, Column 94: cannot generate system identifier for general entity "u"
    …tp://www.blogger.com/blog_this.pyra?t&u=http://convertonlinefree.com&n=Free on…

    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 599, Column 94: general entity "u" not defined and no default entity
    …tp://www.blogger.com/blog_this.pyra?t&u=http://convertonlinefree.com&n=Free on…

    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 599, Column 95: reference not terminated by REFC delimiter
    …p://www.blogger.com/blog_this.pyra?t&u=http://convertonlinefree.com&n=Free onl…

    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 599, Column 95: reference to external entity in attribute value
    …p://www.blogger.com/blog_this.pyra?t&u=http://convertonlinefree.com&n=Free onl…

    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 599, Column 95: reference to entity "u" for which no system identifier could be generated
    …p://www.blogger.com/blog_this.pyra?t&u=http://convertonlinefree.com&n=Free onl…

    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 599, Column 93: entity was defined here
    …ttp://www.blogger.com/blog_this.pyra?t&u=http://convertonlinefree.com&n=Free o…
  • Warning Line 599, Column 125: cannot generate system identifier for general entity "n"
    …er.com/blog_this.pyra?t&u=http://convertonlinefree.com&n=Free online converter"

    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 599, Column 125: general entity "n" not defined and no default entity
    …er.com/blog_this.pyra?t&u=http://convertonlinefree.com&n=Free online converter"

    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 599, Column 126: reference not terminated by REFC delimiter
    …er.com/blog_this.pyra?t&u=http://convertonlinefree.com&n=Free online converter"

    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 599, Column 126: reference to external entity in attribute value
    …er.com/blog_this.pyra?t&u=http://convertonlinefree.com&n=Free online converter"

    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 599, Column 126: reference to entity "n" for which no system identifier could be generated
    …er.com/blog_this.pyra?t&u=http://convertonlinefree.com&n=Free online converter"

    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 599, Column 124: entity was defined here
    …er.com/blog_this.pyra?t&u=http://convertonlinefree.com&n=Free online converter"
  • Error Line 615, Column 60: there is no attribute "nowrap"
                                                    <td nowrap="nowrap">

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

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

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

Visitor Analysis

Daily Visitor
  • 10.967 visits