世界中のアダルト動画が集まる無料動画サイトならアダルトクラウドムービー。皆で話題のアダルト動画を投稿! ...

cloud-movie.net
  • Domain Name
    cloud-movie.net
  • Favicon
  • Google Page Rank
    2
  • Alexa Rank
    #15102
  • Page Size
    49.6 KB
  • Ip Address
    209.236.75.146
  • Heading
    H1: 1, H2: 4, H3: 3, H4: 0, H5: 0, H6: 0
  • Images
    29 GIF, 36 JPG, 6 PNG

Website Meta Analysis

  • Title
    世界中のアダルト動画が集まるアダルトクラウドムービー
  • Meta Keyword
    アダルト,無料動画,アダルト動画,TOP
  • Meta Description
    世界中のアダルト動画が集まる無料動画サイトならアダルトクラウドムービー。皆で話題のアダルト動画を投稿!

Technical Analysis

  • Webserver
    Apache/2.2.15 (CentOS)
  • Ip Address
    209.236.75.146
  • Domain Age
    10 Months, 24 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from cloud-movie.net.

HTML Analysis

  • date: Mon, 12 Aug 2013 06:52:48 GMT
  • server: Apache/2.2.15 (CentOS)
  • x-powered-by: PHP/5.3.3
  • p3p: CP="NOI ADM DEV PSAi COM NAV OUR OTRo STP IND DEM"
  • connection: close
  • content-type: text/html; charset=UTF-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain name: cloud-movie.net

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:
NS1.SERVICE-DNS.COM
NS2.SERVICE-DNS.COM

Creation date: 22 Sep 2012 00:58:00
Expiration date: 21 Sep 2013 16:58:00

IP 209.236.75.146 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 41 Errors
  • 55 Warnings
Ratio Text/Html
  • 0.7117085179714426
Message Error
  • Error Line 6, Column 54: end tag for "meta" omitted, but OMITTAG NO was specified
    <meta name="keywords" content="アダルト,無料動画,アダルト動画,TOP">

    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 6, Column 1: start tag was here
    <meta name="keywords" content="アダルト,無料動画,アダルト動画,TOP">
  • Error Line 7, Column 88: end tag for "meta" omitted, but OMITTAG NO was specified
    …me="description" content="世界中のアダルト動画が集まる無料動画サイトならアダルトクラウドムービー。皆で話題のアダルト動画を投稿!">

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

  • Info Line 7, Column 1: start tag was here
    <meta name="description" content="世界中のアダルト動画が集まる無料動画サイトならアダルトクラウドムービー。皆で話題のアダルト…
  • Error Line 111, Column 94: there is no attribute "onFocus"
    …s="text_search" value="フリーワードを入力" onFocus="cText(this)" onBlur="sText(this)" />

    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 111, Column 115: there is no attribute "onBlur"
    …s="text_search" value="フリーワードを入力" onFocus="cText(this)" onBlur="sText(this)" />

    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 113, Column 18: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    			<option value=null selected="selected">▼カテゴリーを選択する</option>
  • Warning Line 279, Column 47: character "&" is the first character of a delimiter but occurred as data
    …ment.referrer.indexOf('iphone') == -1 && ((navigator.userAgent.indexOf('iPhone…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 279, Column 48: character "&" is the first character of a delimiter but occurred as data
    …ent.referrer.indexOf('iphone') == -1 && ((navigator.userAgent.indexOf('iPhone'…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 279, Column 94: character "&" is the first character of a delimiter but occurred as data
    …gator.userAgent.indexOf('iPhone') > 0 && navigator.userAgent.indexOf('iPad') =…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 279, Column 95: character "&" is the first character of a delimiter but occurred as data
    …ator.userAgent.indexOf('iPhone') > 0 && navigator.userAgent.indexOf('iPad') ==…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 320, Column 50: cannot generate system identifier for general entity "_article"
    …ef="http://ad.dmm.com/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" re…

    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 320, Column 50: general entity "_article" not defined and no default entity
    …ef="http://ad.dmm.com/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" re…

    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 320, Column 58: reference not terminated by REFC delimiter
    …://ad.dmm.com/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofol…

    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 320, Column 58: reference to external entity in attribute value
    …://ad.dmm.com/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofol…

    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 320, Column 58: reference to entity "_article" for which no system identifier could be generated
    …://ad.dmm.com/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofol…

    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 320, Column 49: entity was defined here
    …ref="http://ad.dmm.com/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" r…
  • Warning Line 320, Column 64: cannot generate system identifier for general entity "_link"
    …dmm.com/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofollow" t…

    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 320, Column 64: general entity "_link" not defined and no default entity
    …dmm.com/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofollow" t…

    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 320, Column 69: reference not terminated by REFC delimiter
    …om/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target…

    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 320, Column 69: reference to external entity in attribute value
    …om/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target…

    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 320, Column 69: reference to entity "_link" for which no system identifier could be generated
    …om/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target…

    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 320, Column 63: entity was defined here
    ….dmm.com/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofollow" …
  • Warning Line 320, Column 75: cannot generate system identifier for general entity "_image"
    …p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target="_bla…

    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 320, Column 75: general entity "_image" not defined and no default entity
    …p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target="_bla…

    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 320, Column 81: reference not terminated by REFC delimiter
    …ite=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target="_blank"><i…

    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 320, Column 81: reference to external entity in attribute value
    …ite=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target="_blank"><i…

    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 320, Column 81: reference to entity "_image" for which no system identifier could be generated
    …ite=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target="_blank"><i…

    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 320, Column 74: entity was defined here
    …/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target="_bl…
  • Warning Line 325, Column 80: reference not terminated by REFC delimiter
    …://ad.dmm.com/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofol…

    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 325, Column 80: reference to external entity in attribute value
    …://ad.dmm.com/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofol…

    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 325, Column 80: reference to entity "_article" for which no system identifier could be generated
    …://ad.dmm.com/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofol…

    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 320, Column 49: entity was defined here
    …ref="http://ad.dmm.com/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" r…
  • Warning Line 325, Column 91: reference not terminated by REFC delimiter
    …om/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target…

    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 325, Column 91: reference to external entity in attribute value
    …om/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target…

    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 325, Column 91: reference to entity "_link" for which no system identifier could be generated
    …om/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target…

    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 320, Column 63: entity was defined here
    ….dmm.com/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofollow" …
  • Warning Line 325, Column 103: reference not terminated by REFC delimiter
    …ite=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target="_blank">⇒チ…

    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 325, Column 103: reference to external entity in attribute value
    …ite=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target="_blank">⇒チ…

    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 325, Column 103: reference to entity "_image" for which no system identifier could be generated
    …ite=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target="_blank">⇒チ…

    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 320, Column 74: entity was defined here
    …/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target="_bl…
  • Warning Line 331, Column 58: reference not terminated by REFC delimiter
    …://ad.dmm.com/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofol…

    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 331, Column 58: reference to external entity in attribute value
    …://ad.dmm.com/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofol…

    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 331, Column 58: reference to entity "_article" for which no system identifier could be generated
    …://ad.dmm.com/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofol…

    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 320, Column 49: entity was defined here
    …ref="http://ad.dmm.com/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" r…
  • Warning Line 331, Column 69: reference not terminated by REFC delimiter
    …om/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target…

    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 331, Column 69: reference to external entity in attribute value
    …om/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target…

    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 331, Column 69: reference to entity "_link" for which no system identifier could be generated
    …om/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target…

    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 320, Column 63: entity was defined here
    ….dmm.com/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofollow" …
  • Warning Line 331, Column 81: reference not terminated by REFC delimiter
    …ite=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target="_blank"><i…

    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 331, Column 81: reference to external entity in attribute value
    …ite=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target="_blank"><i…

    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 331, Column 81: reference to entity "_image" for which no system identifier could be generated
    …ite=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target="_blank"><i…

    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 320, Column 74: entity was defined here
    …/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target="_bl…
  • Warning Line 336, Column 80: reference not terminated by REFC delimiter
    …://ad.dmm.com/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofol…

    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 336, Column 80: reference to external entity in attribute value
    …://ad.dmm.com/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofol…

    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 336, Column 80: reference to entity "_article" for which no system identifier could be generated
    …://ad.dmm.com/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofol…

    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 320, Column 49: entity was defined here
    …ref="http://ad.dmm.com/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" r…
  • Warning Line 336, Column 91: reference not terminated by REFC delimiter
    …om/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target…

    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 336, Column 91: reference to external entity in attribute value
    …om/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target…

    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 336, Column 91: reference to entity "_link" for which no system identifier could be generated
    …om/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target…

    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 320, Column 63: entity was defined here
    ….dmm.com/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofollow" …
  • Warning Line 336, Column 103: reference not terminated by REFC delimiter
    …ite=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target="_blank">⇒チ…

    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 336, Column 103: reference to external entity in attribute value
    …ite=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target="_blank">⇒チ…

    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 336, Column 103: reference to entity "_image" for which no system identifier could be generated
    …ite=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target="_blank">⇒チ…

    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 320, Column 74: entity was defined here
    …/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target="_bl…
  • Warning Line 342, Column 58: reference not terminated by REFC delimiter
    …://ad.dmm.com/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofol…

    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 342, Column 58: reference to external entity in attribute value
    …://ad.dmm.com/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofol…

    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 342, Column 58: reference to entity "_article" for which no system identifier could be generated
    …://ad.dmm.com/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofol…

    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 320, Column 49: entity was defined here
    …ref="http://ad.dmm.com/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" r…
  • Warning Line 342, Column 69: reference not terminated by REFC delimiter
    …om/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target…

    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 342, Column 69: reference to external entity in attribute value
    …om/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target…

    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 342, Column 69: reference to entity "_link" for which no system identifier could be generated
    …om/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target…

    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 320, Column 63: entity was defined here
    ….dmm.com/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofollow" …
  • Warning Line 342, Column 81: reference not terminated by REFC delimiter
    …ite=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target="_blank"><i…

    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 342, Column 81: reference to external entity in attribute value
    …ite=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target="_blank"><i…

    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 342, Column 81: reference to entity "_image" for which no system identifier could be generated
    …ite=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target="_blank"><i…

    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 320, Column 74: entity was defined here
    …/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target="_bl…
  • Warning Line 347, Column 80: reference not terminated by REFC delimiter
    …://ad.dmm.com/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofol…

    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 347, Column 80: reference to external entity in attribute value
    …://ad.dmm.com/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofol…

    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 347, Column 80: reference to entity "_article" for which no system identifier could be generated
    …://ad.dmm.com/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofol…

    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 320, Column 49: entity was defined here
    …ref="http://ad.dmm.com/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" r…
  • Warning Line 347, Column 91: reference not terminated by REFC delimiter
    …om/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target…

    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 347, Column 91: reference to external entity in attribute value
    …om/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target…

    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 347, Column 91: reference to entity "_link" for which no system identifier could be generated
    …om/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target…

    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 320, Column 63: entity was defined here
    ….dmm.com/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofollow" …
  • Warning Line 347, Column 103: reference not terminated by REFC delimiter
    …ite=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target="_blank">⇒チ…

    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 347, Column 103: reference to external entity in attribute value
    …ite=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target="_blank">⇒チ…

    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 347, Column 103: reference to entity "_image" for which no system identifier could be generated
    …ite=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target="_blank">⇒チ…

    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 320, Column 74: entity was defined here
    …/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target="_bl…
  • Warning Line 353, Column 58: reference not terminated by REFC delimiter
    …://ad.dmm.com/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofol…

    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 58: reference to external entity in attribute value
    …://ad.dmm.com/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofol…

    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 58: reference to entity "_article" for which no system identifier could be generated
    …://ad.dmm.com/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofol…

    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 320, Column 49: entity was defined here
    …ref="http://ad.dmm.com/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" r…
  • Warning Line 353, Column 69: reference not terminated by REFC delimiter
    …om/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target…

    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 69: reference to external entity in attribute value
    …om/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target…

    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 69: reference to entity "_link" for which no system identifier could be generated
    …om/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target…

    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 320, Column 63: entity was defined here
    ….dmm.com/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofollow" …
  • Warning Line 353, Column 81: reference not terminated by REFC delimiter
    …ite=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target="_blank"><i…

    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 81: reference to external entity in attribute value
    …ite=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target="_blank"><i…

    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 81: reference to entity "_image" for which no system identifier could be generated
    …ite=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target="_blank"><i…

    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 320, Column 74: entity was defined here
    …/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target="_bl…
  • Warning Line 358, Column 80: reference not terminated by REFC delimiter
    …://ad.dmm.com/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofol…

    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 358, Column 80: reference to external entity in attribute value
    …://ad.dmm.com/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofol…

    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 358, Column 80: reference to entity "_article" for which no system identifier could be generated
    …://ad.dmm.com/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofol…

    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 320, Column 49: entity was defined here
    …ref="http://ad.dmm.com/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" r…
  • Warning Line 358, Column 91: reference not terminated by REFC delimiter
    …om/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target…

    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 358, Column 91: reference to external entity in attribute value
    …om/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target…

    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 358, Column 91: reference to entity "_link" for which no system identifier could be generated
    …om/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target…

    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 320, Column 63: entity was defined here
    ….dmm.com/ad/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofollow" …
  • Warning Line 358, Column 103: reference not terminated by REFC delimiter
    …ite=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target="_blank">⇒チ…

    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 358, Column 103: reference to external entity in attribute value
    …ite=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target="_blank">⇒チ…

    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 358, Column 103: reference to entity "_image" for which no system identifier could be generated
    …ite=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target="_blank">⇒チ…

    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 320, Column 74: entity was defined here
    …/p/r?_site=79&_article=1049&_link=2339&_image=2345" rel="nofollow" target="_bl…
  • Error Line 451, Column 17: there is no attribute "count"
    					     count="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.

  • Error Line 477, Column 15: value of attribute "id" invalid: "5" cannot start a name
    					<img id="50d7ad415404d"

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

  • Error Line 504, Column 15: value of attribute "id" invalid: "5" cannot start a name
    					<img id="50d7ab61920de"

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

  • Error Line 531, Column 15: value of attribute "id" invalid: "5" cannot start a name
    					<img id="50d148cca22be"

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

  • Error Line 557, Column 15: value of attribute "id" invalid: "5" cannot start a name
    					<img id="50c54a3e93faf"

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

  • Error Line 583, Column 15: value of attribute "id" invalid: "5" cannot start a name
    					<img id="50c18b78d6b7f"

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

  • Error Line 609, Column 15: value of attribute "id" invalid: "5" cannot start a name
    					<img id="507666e812c38"

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

  • Error Line 635, Column 15: value of attribute "id" invalid: "5" cannot start a name
    					<img id="5052f82669e3e"

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

  • Error Line 661, Column 15: value of attribute "id" invalid: "5" cannot start a name
    					<img id="50515dd8cf593"

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

  • Error Line 687, Column 15: value of attribute "id" invalid: "5" cannot start a name
    					<img id="504ac812b3d0f"

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

  • Error Line 713, Column 15: value of attribute "id" invalid: "5" cannot start a name
    					<img id="5020af0190d62"

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

  • Error Line 739, Column 15: value of attribute "id" invalid: "5" cannot start a name
    					<img id="5001a13bef3ec"

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

  • Error Line 765, Column 15: value of attribute "id" invalid: "4" cannot start a name
    					<img id="4fffab6aa664f"

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

  • Error Line 791, Column 15: value of attribute "id" invalid: "4" cannot start a name
    					<img id="4fb4c6252427c"

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

  • Error Line 817, Column 15: value of attribute "id" invalid: "4" cannot start a name
    					<img id="4f3a19cf26ee4"

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

  • Error Line 843, Column 15: value of attribute "id" invalid: "4" cannot start a name
    					<img id="4f2268f7e65e6"

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

  • Error Line 869, Column 15: value of attribute "id" invalid: "4" cannot start a name
    					<img id="4ef2ff1237acc"

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

  • Error Line 895, Column 15: value of attribute "id" invalid: "4" cannot start a name
    					<img id="4ecc55467c8e5"

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

  • Error Line 921, Column 15: value of attribute "id" invalid: "4" cannot start a name
    					<img id="4ec9a66bec689"

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

  • Error Line 1052, Column 15: value of attribute "id" invalid: "5" cannot start a name
    					<img id="50d2ec6f20e27"

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

  • Error Line 1083, Column 15: value of attribute "id" invalid: "5" cannot start a name
    					<img id="508653f978bd6"

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

  • Error Line 1104, Column 15: value of attribute "id" invalid: "0" cannot start a name
    					<img id="0OewsTAk1E"

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

  • Error Line 1125, Column 15: value of attribute "id" invalid: "5" cannot start a name
    					<img id="5oZV6O5Psl"

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

  • Error Line 1487, Column 7: end tag for element "div" which is not open
    	</div>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

Visitor Analysis

Daily Visitor
  • 3.500 visits