Treato distills the collective patient voice from blogs and forums using Natural Language Processing, Big Data and a proprietary patient language knowledge ...

treato.com
  • Domain Name
    treato.com
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #31974
  • Page Size
    22.6 KB
  • Ip Address
    108.60.141.207
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    1 GIF, 1 JPG, 2 PNG

Website Meta Analysis

  • Title
    Posts about Drugs, Side effects, Conditions and Symptoms - Treato
  • Meta Keyword
    Drug side effects, drugs, medical information, Side effects, Conditions, Symptoms, Treato, Treato.com
  • Meta Description
    Treato distills the collective patient voice from blogs and forums using Natural Language Processing, Big Data and a proprietary patient language knowledge

Technical Analysis

  • Webserver
    Apache-Coyote/1.1
  • Ip Address
    108.60.141.207
  • Domain Age
    1 Years, 11 Months, 24 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: Apache-Coyote/1.1
  • pragma: no-cache
  • expires: Thu, 01 Jan 1970 00:00:00 GMT
  • cache-control: no-cache
  • content-type: text/html;charset=UTF-8
  • content-language: en-US
  • content-encoding: gzip
  • vary: Accept-Encoding
  • date: Mon, 04 Feb 2013 23:23:17 GMT
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for treato.com

DNS Analysis


DNS servers
ns1.dotquad.com [208.78.29.10]
ns2.dotquad.com [208.78.29.20]


DNS Records

Answer records
treato.com SOA
server: ns1.dotquad.com
email: hostmaster@dotquad.com
serial: 2010012001
refresh: 10800
retry: 15
expire: 604800
minimum ttl: 10800
86400s
treato.com NS  ns1.dotquad.com 86400s
treato.com MX
preference: 20
exchange: ALT1.ASPMX.L.GOOGLE.COM
86400s
treato.com NS  ns2.dotquad.com 86400s
treato.com TXT v=spf1 include:_spf.google.com ip4:108.60.141.192/27 ip4:69.162.169.32/29 ~all 86400s
treato.com MX
preference: 30
exchange: ASPMX2.GOOGLEMAIL.COM
86400s
treato.com MX
preference: 20
exchange: ALT2.ASPMX.L.GOOGLE.COM
86400s
treato.com MX
preference: 30
exchange: ASPMX3.GOOGLEMAIL.COM
86400s
treato.com MX
preference: 10
exchange: ASPMX.L.GOOGLE.COM
86400s
treato.com NS  ns3.dotquad.com 86400s
treato.com TXT google-site-verification=RIJl0avU56RcOVknxDWkJVXHqhEWywrTe2yB6vps8bY 86400s
treato.com A 108.60.141.207 10s

Authority records

Additional records
ns1.dotquad.com A 208.78.29.10 86400s
ns3.dotquad.com 28 [16 bytes] 86400s
0 [0 bytes] 0s
0 [0 bytes] 0s
0 [0 bytes] 0s
0 [0 bytes] 0s

IP 108.60.141.207 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Montclair
  • Continent Code
    07042
  • Latitude
    973
  • Longitude
    501
  • %rwhois V-1.0,V-1.5:00090h:00 portal.digitalproviders.net (Ubersmith RWhois Server V-2.3.0)
    autharea=108.60.141.0/24
    xautharea=108.60.141.0/24
    network:Class-Name:network
    network:Auth-Area:108.60.141.0/24
    network:ID:NET-3017.108.60.141.200/29
    network:Network-Name:LGA4 Colo
    network:IP-Network:108.60.141.200/29
    network:IP-Network-Block:108.60.141.200 - 108.60.141.207
    network:Org-Name:Treato Ltd
    network:Street-Address:9 Ha'atsmaut Road
    network:City:Yehud
    network:State:ISRAEL
    network:Postal-Code:56300
    network:Country-Code:IL
    network:Tech-Contact:MAINT-3017.108.60.141.200/29
    network:Created:20110127155328000
    network:Updated:20110526053407000
    network:Updated-By:support@atlanticmetro.net
    contact:POC-Name:Eyal Harkat
    contact:POC-Email:eyalh@treato.com
    contact:POC-Phone:+972-545677800
    contact:Tech-Name:Eyal Harkat
    contact:Tech-Email:eyalh@treato.com
    contact:Tech-Phone:+972-545677800
    contact:Abuse-Name:Abuse Department
    contact:Abuse-Email:abuse@atlanticmetro.net
    %ok

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 28 Errors
  • 21 Warnings
Ratio Text/Html
  • 0.690438091943087
Message Error
  • Error Line 6, Column 16: there is no attribute "property"
    <meta property="og:image" content="http://static.treato.com/carlos/1.4.32/resou…

    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 19, Column 8: required attribute "type" not specified
    <script>

    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 188, Column 147: cannot generate system identifier for general entity "utm_medium"
    …treato-service.htm?utm_source=Sign-Up&utm_medium=Treato&utm_campaign=Treato%2B…

    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 188, Column 147: general entity "utm_medium" not defined and no default entity
    …treato-service.htm?utm_source=Sign-Up&utm_medium=Treato&utm_campaign=Treato%2B…

    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 188, Column 157: reference not terminated by REFC delimiter
    …vice.htm?utm_source=Sign-Up&utm_medium=Treato&utm_campaign=Treato%2BPharma" cl…

    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 188, Column 157: reference to external entity in attribute value
    …vice.htm?utm_source=Sign-Up&utm_medium=Treato&utm_campaign=Treato%2BPharma" cl…

    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 188, Column 157: reference to entity "utm_medium" for which no system identifier could be generated
    …vice.htm?utm_source=Sign-Up&utm_medium=Treato&utm_campaign=Treato%2BPharma" cl…

    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 188, Column 146: entity was defined here
    …/treato-service.htm?utm_source=Sign-Up&utm_medium=Treato&utm_campaign=Treato%2…
  • Warning Line 188, Column 165: cannot generate system identifier for general entity "utm_campaign"
    …?utm_source=Sign-Up&utm_medium=Treato&utm_campaign=Treato%2BPharma" class="lin…

    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 188, Column 165: general entity "utm_campaign" not defined and no default entity
    …?utm_source=Sign-Up&utm_medium=Treato&utm_campaign=Treato%2BPharma" class="lin…

    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 188, Column 177: reference not terminated by REFC delimiter
    …Sign-Up&utm_medium=Treato&utm_campaign=Treato%2BPharma" class="link-color">Lea…

    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 188, Column 177: reference to external entity in attribute value
    …Sign-Up&utm_medium=Treato&utm_campaign=Treato%2BPharma" class="link-color">Lea…

    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 188, Column 177: reference to entity "utm_campaign" for which no system identifier could be generated
    …Sign-Up&utm_medium=Treato&utm_campaign=Treato%2BPharma" class="link-color">Lea…

    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 188, Column 164: entity was defined here
    …m?utm_source=Sign-Up&utm_medium=Treato&utm_campaign=Treato%2BPharma" class="li…
  • Error Line 282, Column 112: there is no attribute "autocomplete"
    …verId" class="new_search_inp , input_txt" name="userInput" autocomplete="off"/>

    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 319, Column 11: required attribute "type" not specified
    			<script>

    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 347, Column 124: end tag for "img" omitted, but OMITTAG NO was specified
    …treato.com/carlos/1.4.32/resources/images/carlos/black_header/logo_invert.png">

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

  • Info Line 347, Column 8: start tag was here
    		    	<img alt="Treato" src="http://static.treato.com/carlos/1.4.32/resources/…
  • Warning Line 353, Column 116: reference not terminated by REFC delimiter
    …rvice.htm?utm_source=Header&utm_medium=Treato&utm_campaign=Treato%2BPharma" st…

    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 353, Column 116: reference to external entity in attribute value
    …rvice.htm?utm_source=Header&utm_medium=Treato&utm_campaign=Treato%2BPharma" st…

    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 353, Column 116: reference to entity "utm_medium" for which no system identifier could be generated
    …rvice.htm?utm_source=Header&utm_medium=Treato&utm_campaign=Treato%2BPharma" st…

    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 188, Column 146: entity was defined here
    …/treato-service.htm?utm_source=Sign-Up&utm_medium=Treato&utm_campaign=Treato%2…
  • Warning Line 353, Column 136: reference not terminated by REFC delimiter
    …=Header&utm_medium=Treato&utm_campaign=Treato%2BPharma" style="margin-left:50p…

    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 353, Column 136: reference to external entity in attribute value
    …=Header&utm_medium=Treato&utm_campaign=Treato%2BPharma" style="margin-left:50p…

    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 353, Column 136: reference to entity "utm_campaign" for which no system identifier could be generated
    …=Header&utm_medium=Treato&utm_campaign=Treato%2BPharma" style="margin-left:50p…

    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 188, Column 164: entity was defined here
    …m?utm_source=Sign-Up&utm_medium=Treato&utm_campaign=Treato%2BPharma" class="li…
  • Warning Line 377, Column 116: reference not terminated by REFC delimiter
    …-service.htm?utm_source=Header&utm_medium=Treato&utm_campaign=Treato%2BPharma">

    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 377, Column 116: reference to external entity in attribute value
    …-service.htm?utm_source=Header&utm_medium=Treato&utm_campaign=Treato%2BPharma">

    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 377, Column 116: reference to entity "utm_medium" for which no system identifier could be generated
    …-service.htm?utm_source=Header&utm_medium=Treato&utm_campaign=Treato%2BPharma">

    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 188, Column 146: entity was defined here
    …/treato-service.htm?utm_source=Sign-Up&utm_medium=Treato&utm_campaign=Treato%2…
  • Warning Line 377, Column 136: reference not terminated by REFC delimiter
    …-service.htm?utm_source=Header&utm_medium=Treato&utm_campaign=Treato%2BPharma">

    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 377, Column 136: reference to external entity in attribute value
    …-service.htm?utm_source=Header&utm_medium=Treato&utm_campaign=Treato%2BPharma">

    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 377, Column 136: reference to entity "utm_campaign" for which no system identifier could be generated
    …-service.htm?utm_source=Header&utm_medium=Treato&utm_campaign=Treato%2BPharma">

    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 188, Column 164: entity was defined here
    …m?utm_source=Sign-Up&utm_medium=Treato&utm_campaign=Treato%2BPharma" class="li…
  • Error Line 378, Column 33: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    	         <div class="text-link">Learn more</div>

    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 394, Column 25: there is no attribute "autocomplete"
        	<form autocomplete="off" name="userSearchData"   action='javascript:void(0…

    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 418, Column 88: cannot generate system identifier for general entity "text"
    …url=http:%2F%2Fyoutu.be%2F8rEXhLXfOWM&text=Watch%20this%20video%20and%20see%20…

    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 418, Column 88: general entity "text" not defined and no default entity
    …url=http:%2F%2Fyoutu.be%2F8rEXhLXfOWM&text=Watch%20this%20video%20and%20see%20…

    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 418, Column 92: reference not terminated by REFC delimiter
    …http:%2F%2Fyoutu.be%2F8rEXhLXfOWM&text=Watch%20this%20video%20and%20see%20how%…

    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 418, Column 92: reference to external entity in attribute value
    …http:%2F%2Fyoutu.be%2F8rEXhLXfOWM&text=Watch%20this%20video%20and%20see%20how%…

    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 418, Column 92: reference to entity "text" for which no system identifier could be generated
    …http:%2F%2Fyoutu.be%2F8rEXhLXfOWM&text=Watch%20this%20video%20and%20see%20how%…

    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 418, Column 87: entity was defined here
    …?url=http:%2F%2Fyoutu.be%2F8rEXhLXfOWM&text=Watch%20this%20video%20and%20see%2…
  • Error Line 420, Column 143: required attribute "alt" not specified
    …4.32/resources/images/tweet_the_movie.png" style="float:right ; display:none"/>

    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 423, Column 144: required attribute "alt" not specified
    …/resources/images/video_btn.jpg"   style="float:right" onclick="startVideo()"/>

    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 425, Column 90: cannot generate system identifier for general entity "wmode"
    …w.youtube.com/embed/8rEXhLXfOWM?rel=0&wmode=transparent" frameborder="0" allow…

    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 425, Column 90: general entity "wmode" not defined and no default entity
    …w.youtube.com/embed/8rEXhLXfOWM?rel=0&wmode=transparent" frameborder="0" allow…

    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 425, Column 95: reference not terminated by REFC delimiter
    …tube.com/embed/8rEXhLXfOWM?rel=0&wmode=transparent" frameborder="0" allowfulls…

    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 425, Column 95: reference to external entity in attribute value
    …tube.com/embed/8rEXhLXfOWM?rel=0&wmode=transparent" frameborder="0" allowfulls…

    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 425, Column 95: reference to entity "wmode" for which no system identifier could be generated
    …tube.com/embed/8rEXhLXfOWM?rel=0&wmode=transparent" frameborder="0" allowfulls…

    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 425, Column 89: entity was defined here
    …ww.youtube.com/embed/8rEXhLXfOWM?rel=0&wmode=transparent" frameborder="0" allo…
  • Error Line 425, Column 140: "allowfullscreen" is not a member of a group specified for any attribute
    …/8rEXhLXfOWM?rel=0&wmode=transparent" frameborder="0" allowfullscreen></iframe>
  • Error Line 461, Column 73: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    				<div class="home-linkedin-link float_left" style="margin-left: 0px;">

    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 464, Column 73: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    				<div class="home-twitter-link float_left" style="margin-left: 10px;">

    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 468, Column 32: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    					style="margin-left: 10px;">

    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 471, Column 30: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    				<div style="clear: both;"></div> 

    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 476, Column 33: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
            	<div class="float_left">

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

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

  • Warning Line 477, Column 78: character "&" is the first character of a delimiter but occurred as data
    …reato.com/about/terms.html" target="_blank">Terms & Conditions</a>&nbsp;|&nbsp;

    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 484, Column 33: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
            	<div style="clear:both"></div>

    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>").

Visitor Analysis

Daily Visitor
  • 9.567 visits
Daily Visitor