logomaker.com

Easy-to-use logo design tool helps you create a logo you'll love in as little as 15 minutes. Try it now for free. See what other customers say... ...

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

Overview Info

  • Domain Name
    logomaker.com
  • Favicon
  • Alexa Rank
    #12661
  • Google Page Rank
    PR 0
  • Ip Address
    107.22.236.46
  • Page Size
    13.7 KB
  • Images
    3 GIF, 9 JPG, 4 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    7 0 4 6 0 0

Website Meta Analysis



  • Title
    FREE Logo Maker - FREE Logo Creator - FREE Online Logo Design
  • Meta Keyword
    free logo, do-it-yourself logo design, free logo creator, logo icons, logo design, most popular logo design tool, business logo, branding
  • Meta Description
    Easy-to-use logo design tool helps you create a logo you'll love in as little as 15 minutes. Try it now for free. See what other customers say...

Technical Analysis



  • Webserver
    Apache/2.2.3 (CentOS)
  • Ip Address
    107.22.236.46
  • Domain Age
    10 Years, 2 Months, 12 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Tue, 09 Jul 2013 20:02:42 GMT
  • server: Apache/2.2.3 (CentOS)
  • x-powered-by: PHP/5.2.4
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • connection: close
  • content-type: text/html; charset=UTF-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
Domain Administrator
Hewlett-Packard Company
3000 Hanover St.
Palo Alto CA 94304
US
email +1.8005247638 Fax: +1.6508522936

Domain Name: logomaker.com

Registrar: Markmonitor.com
Registrar Whois: whois.markmonitor.com
Registrar URL: http://www.markmonitor.com

Administrative Contact:
Domain Administrator
Hewlett-Packard Company
3000 Hanover St.
Palo Alto CA 94304
US
email +1.8005247638 Fax: +1.6508522936
Technical Contact, Zone Contact:
HP Hostmaster
Hewlett-Packard Company
1000 NE Circle Blvd MS 413A
Corvallis OR 97330
US
email +1.8005247638 Fax: +1.5417156789

Created: 2003-04-21.
Expires: 2012-05-01.
Updated: 2011-03-30.

Name Servers:

ns13.zoneedit.com
ns17.zoneedit.com

IP 107.22.236.46 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Seattle
  • Continent Code
    98144
  • Latitude
    206
  • Longitude
    819
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 107.22.236.46"
    #
    # Use "?" to get help.
    #

    #
    # The following results may also be obtained via:
    # http://whois.arin.net/rest/nets;q=107.22.236.46?showDetails=true&showARIN=false&ext=netref2
    #

    NetRange: 107.20.0.0 - 107.23.255.255
    CIDR: 107.20.0.0/14
    OriginAS:
    NetName: AMAZON-EC2-8
    NetHandle: NET-107-20-0-0-1
    Parent: NET-107-0-0-0-0
    NetType: Direct Assignment
    Comment: The activity you have detected originates from a dynamic hosting environment.
    Comment: For fastest response, please submit abuse reports at http://aws-portal.amazon.com/gp/aws/html-forms-controller/contactus/AWSAbuse
    Comment: For more information regarding EC2 see:
    Comment: http://ec2.amazonaws.com/
    Comment: All reports MUST include:
    Comment: * src IP
    Comment: * dest IP (your IP)
    Comment: * dest port
    Comment: * Accurate date/timestamp and timezone of activity
    Comment: * Intensity/frequency (short log extracts)
    Comment: * Your contact details (phone and email) Without these we will be unable to identify the correct owner of the IP address at that point in time.
    RegDate: 2011-05-03
    Updated: 2012-03-02
    Ref: http://whois.arin.net/rest/net/NET-107-20-0-0-1


    OrgName: Amazon.com, Inc.
    OrgId: AMAZO-4
    Address: Amazon Web Services, Elastic Compute Cloud, EC2
    Address: 1200 12th Avenue South
    City: Seattle
    StateProv: WA
    PostalCode: 98144
    Country: US
    RegDate: 2005-09-29
    Updated: 2009-06-02
    Comment: For details of this service please see
    Comment: http://ec2.amazonaws.com/
    Ref: http://whois.arin.net/rest/org/AMAZO-4

    OrgTechHandle: ANO24-ARIN
    OrgTechName: Amazon EC2 Network Operations
    OrgTechPhone: +1-206-266-4064
    OrgTechEmail: aes-noc@amazon.com
    OrgTechRef: http://whois.arin.net/rest/poc/ANO24-ARIN

    OrgAbuseHandle: AEA8-ARIN
    OrgAbuseName: Amazon EC2 Abuse
    OrgAbusePhone: +1-206-266-4064
    OrgAbuseEmail: ec2-abuse@amazon.com
    OrgAbuseRef: http://whois.arin.net/rest/poc/AEA8-ARIN

    #
    # ARIN WHOIS data and services are subject to the Terms of Use
    # available at: https://www.arin.net/whois_tou.html
    #

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 38 Errors
  • 10 Warnings
Ratio Text/Html
  • 0.5949946371111905
Message Error
  • Error Line 39, Column 12: 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 46, Column 36: there is no attribute "data-href"
    				<div class="fb-like" data-href="https://www.facebook.com/FreeLogomaker" dat…

    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 46, Column 87: there is no attribute "data-send"
    …facebook.com/FreeLogomaker" data-send="false" data-layout="button_count" data-…

    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 46, Column 107: there is no attribute "data-layout"
    …omaker" data-send="false" data-layout="button_count" data-width="100" data-sho…

    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 46, Column 133: there is no attribute "data-width"
    …data-layout="button_count" data-width="100" data-show-faces="false" data-font=…

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

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

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

  • Error Line 46, Column 155: there is no attribute "data-show-faces"
    …button_count" data-width="100" data-show-faces="false" data-font="arial"></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 46, Column 173: there is no attribute "data-font"
    …button_count" data-width="100" data-show-faces="false" data-font="arial"></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 50, Column 79: there is no attribute "data-url"
    …class="twitter-share-button" data-url="http://www.logomaker.com" data-count="h…

    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 117: there is no attribute "data-count"
    …"http://www.logomaker.com" data-count="horizontal">Tweet</a><script type="text…

    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 54, Column 21: there is no attribute "size"
    				<g:plusone size="medium" href="http://www.logomaker.com/"></g:plusone>			

    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 54, Column 35: there is no attribute "href"
    				<g:plusone size="medium" href="http://www.logomaker.com/"></g:plusone>			

    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 54, Column 62: element "g:plusone" undefined
    				<g:plusone size="medium" href="http://www.logomaker.com/"></g:plusone>			

    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 76, Column 102: cannot generate system identifier for general entity "source"
    …ogomaker.com/logoMaker.html?fromSite=&source=&domain=logomaker.com')">Start No…

    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 76, Column 102: general entity "source" not defined and no default entity
    …ogomaker.com/logoMaker.html?fromSite=&source=&domain=logomaker.com')">Start No…

    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 76, Column 108: reference not terminated by REFC delimiter
    …er.com/logoMaker.html?fromSite=&source=&domain=logomaker.com')">Start Now</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 76, Column 108: reference to external entity in attribute value
    …er.com/logoMaker.html?fromSite=&source=&domain=logomaker.com')">Start Now</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 76, Column 108: reference to entity "source" for which no system identifier could be generated
    …er.com/logoMaker.html?fromSite=&source=&domain=logomaker.com')">Start Now</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 76, Column 101: entity was defined here
    …logomaker.com/logoMaker.html?fromSite=&source=&domain=logomaker.com')">Start N…
  • Warning Line 76, Column 110: cannot generate system identifier for general entity "domain"
    ….com/logoMaker.html?fromSite=&source=&domain=logomaker.com')">Start Now</a></l…

    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 76, Column 110: general entity "domain" not defined and no default entity
    ….com/logoMaker.html?fromSite=&source=&domain=logomaker.com')">Start Now</a></l…

    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 76, Column 116: reference not terminated by REFC delimiter
    …com/logoMaker.html?fromSite=&source=&domain=logomaker.com')">Start Now</a></li>

    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 76, Column 116: reference to external entity in attribute value
    …com/logoMaker.html?fromSite=&source=&domain=logomaker.com')">Start Now</a></li>

    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 76, Column 116: reference to entity "domain" for which no system identifier could be generated
    …com/logoMaker.html?fromSite=&source=&domain=logomaker.com')">Start Now</a></li>

    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 76, Column 109: entity was defined here
    …r.com/logoMaker.html?fromSite=&source=&domain=logomaker.com')">Start Now</a></…
  • Error Line 198, Column 60: required attribute "alt" not specified
    							<img src="images/icon1.jpg" class="floatLeftNoPad" />

    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 203, Column 60: required attribute "alt" not specified
    							<img src="images/icon2.jpg" class="floatLeftNoPad" />

    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 207, Column 17: there is no attribute "height"
    					<tr height="35">

    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 208, Column 73: required attribute "alt" not specified
    						<td width="391"><img src="images/spc.gif" height="1" width="391" /></td>

    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 209, Column 71: required attribute "alt" not specified
    						<td width="50"><img src="images/spc.gif" height="1" width="50" /></td>

    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 210, Column 73: required attribute "alt" not specified
    						<td width="391"><img src="images/spc.gif" height="1" width="391" /></td>

    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 214, Column 60: required attribute "alt" not specified
    							<img src="images/icon3.jpg" class="floatLeftNoPad" />

    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 219, Column 60: required attribute "alt" not specified
    							<img src="images/icon4.jpg" class="floatLeftNoPad" />

    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 223, Column 26: end tag for "tr" which is not finished
    					<tr height="35"></tr>				

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Error Line 226, Column 23: "itemscope" is not a member of a group specified for any attribute
    							<div itemscope itemtype="http://schema.org/Product">
  • Error Line 226, Column 32: there is no attribute "itemtype"
    							<div itemscope itemtype="http://schema.org/Product">

    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 227, Column 46: there is no attribute "itemprop"
    								<span style="display:none;" itemprop="name">Logo Design</span>

    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 228, Column 61: required attribute "alt" not specified
    								<img src="images/icon5.jpg" class="floatLeftNoPad" />

    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 231, Column 23: there is no attribute "itemprop"
    								<div itemprop="aggregateRating" itemscope itemtype="http://schema.org/A…

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

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

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

  • Error Line 231, Column 51: "itemscope" is not a member of a group specified for any attribute
    … itemprop="aggregateRating" itemscope itemtype="http://schema.org/AggregateRat…
  • Error Line 232, Column 37: there is no attribute "itemprop"
    									<meta content="1" itemprop="worstRating">

    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 232, Column 50: document type does not allow element "meta" here
    									<meta content="1" itemprop="worstRating">

    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 232, Column 51: end tag for "meta" omitted, but OMITTAG NO was specified
    									<meta content="1" itemprop="worstRating">

    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 232, Column 10: start tag was here
    									<meta content="1" itemprop="worstRating">
  • Error Line 233, Column 49: document type does not allow element "meta" here
    									<meta content="5" itemprop="bestRating">

    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 233, Column 50: end tag for "meta" omitted, but OMITTAG NO was specified
    									<meta content="5" itemprop="bestRating">

    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 233, Column 10: start tag was here
    									<meta content="5" itemprop="bestRating">
  • Warning Line 256, Column 113: reference not terminated by REFC delimiter
    …er.com/logoMaker.html?fromSite=&source=&domain=logomaker.com')" title="Start 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 256, Column 113: reference to external entity in attribute value
    …er.com/logoMaker.html?fromSite=&source=&domain=logomaker.com')" title="Start 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 256, Column 113: reference to entity "source" for which no system identifier could be generated
    …er.com/logoMaker.html?fromSite=&source=&domain=logomaker.com')" title="Start 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 76, Column 101: entity was defined here
    …logomaker.com/logoMaker.html?fromSite=&source=&domain=logomaker.com')">Start N…
  • Warning Line 256, Column 121: reference not terminated by REFC delimiter
    …ogoMaker.html?fromSite=&source=&domain=logomaker.com')" title="Start a Logo"><…

    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 256, Column 121: reference to external entity in attribute value
    …ogoMaker.html?fromSite=&source=&domain=logomaker.com')" title="Start a Logo"><…

    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 256, Column 121: reference to entity "domain" for which no system identifier could be generated
    …ogoMaker.html?fromSite=&source=&domain=logomaker.com')" title="Start a Logo"><…

    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 76, Column 109: entity was defined here
    …r.com/logoMaker.html?fromSite=&source=&domain=logomaker.com')">Start Now</a></…

Visitor Analysis

Daily Visitor
  • 14.000 visits

In Page Analysis