pideo.net

pideo.net

Pideo動画検索。動画共有サイトを横断検索します。Yuutube,ニコニコ動画,Veoh,Dailymotion,Tudou,Daum,Megavideo,Saymove。 ...

Domain Name pideo.net
Favicon pideo.net
Google Page Rank 3
Alexa Rank #2813
Page Size 5.5 KB
Ip Address 49.212.80.160
Heading H1: 1, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
Images 2 GIF, 0 JPG, 2 PNG

Website Meta Analysis

Title Pideo 動画検索
Meta Keyword Pideo,ピデオ,ぴでお,動画,検索エンジン,動画検索,動画共有,横断検索,Youtube,Nicovideo,Veoh,Dailymotion,Youku,Daum,Himado,Saymove
Meta Description Pideo動画検索。動画共有サイトを横断検索します。Yuutube,ニコニコ動画,Veoh,Dailymotion,Tudou,Daum,Megavideo,Saymove。

Technical Analysis

Webserver nginx
Ip Address 49.212.80.160
Domain Age
Javascript Library jquery
Language used HTML, CSS, Javascript

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

HTML Analysis

  • server: nginx
  • date: Wed, 17 Jul 2013 16:55:55 GMT
  • content-type: text/html; charset=UTF-8
  • connection: close
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA

Domain Handle: None
Domain Domain Name: pideo.net
Created: 2011-02-01 19:05:35.0
Updated: 2012-01-19 05:29:26.0
Expires: 2013-02-01 19:05:35.0
Domain Status: ACTIVE
Registrant Domain Name: Whois Privacy Protection Service
Registrant Organization: paperboy and co.
Registrant Street1: 2-7-21 Tenjin Chuo-ku
Registrant Street2: Tenjin Prime 8F
Registrant City: Fukuoka-shi
Registrant State: Fukuoka
Registrant Postal Code: 8100001
Registrant Country: JP
Registrant Phone: 81-927137999
Registrant Fax: 81-927137944
Registrant Email: email
Admin Domain Name: Whois Privacy Protection Service
Admin Organization: paperboy and co.
Admin Street1: 2-7-21 Tenjin Chuo-ku
Admin Street2: Tenjin Prime 8F
Admin City: Fukuoka-shi
Admin State: Fukuoka
Admin Postal Code: 8100001
Admin Country: JP
Admin Phone: 81-927137999
Admin Fax: 81-927137944
Admin Email: email
Billing Domain Name: Whois Privacy Protection Service
Billing Organization: paperboy and co.
Billing Street1: 2-7-21 Tenjin Chuo-ku
Billing Street2: Tenjin Prime 8F
Billing City: Fukuoka-shi
Billing State: Fukuoka
Billing Postal Code: 8100001
Billing Country: JP
Billing Phone: 81-927137999
Billing Fax: 81-927137944
Billing Email: email
Tech Domain Name: Whois Privacy Protection Service
Tech Organization: paperboy and co.
Tech Street1: 2-7-21 Tenjin Chuo-ku
Tech Street2: Tenjin Prime 8F
Tech City: Fukuoka-shi
Tech State: Fukuoka
Tech Postal Code: 8100001
Tech Country: JP
Tech Phone: 81-927137999
Tech Fax: 81-927137944
Tech Email: email
Name Servers: dns01.muumuu-domain.com
Name Servers: dns02.muumuu-domain.com

Technical Analysis


DNS servers
dns01.muumuu-domain.com [59.106.124.43]
dns02.muumuu-domain.com [210.188.212.227]


DNS Records

Answer records
pideo.net NS  dns02.muumuu-domain.com 3600s
pideo.net A 49.212.80.160 3600s
pideo.net SOA
server: pideo.net
email: postmaster@pideo.net
serial: 1359959659
refresh: 3600
retry: 1800
expire: 604800
minimum ttl: 3600
3600s
pideo.net NS  dns01.muumuu-domain.com 3600s
pideo.net MX
preference: 50
exchange: pideo.net
3600s
pideo.net TXT v=spf1 ip4:49.212.80.160 ~all 3600s
pideo.net MX
preference: 50
exchange: mail.pideo.net
3600s

Authority records

Additional records
mail.pideo.net A 49.212.80.160 3600s

IP 49.212.80.160 Analysis

Country Code : JP
Country Code3 : JPN
Country Name : Japan
City : AS
Continent Code : 36° North
Latitude : 138.
Longitude :

% [whois.apnic.net node-2]
% Whois data copyright terms http://www.apnic.net/db/dbcopyright.html

inetnum: 49.212.0.0 - 49.212.255.255
netname: SAKURA-OSAKA
descr: SAKURA Internet Inc.
descr: 1-8-14, Minami Honmachi, Chuo-ku, Osaka 541-0054, Japan
country: JP
admin-c: JNIC1-AP
tech-c: JNIC1-AP
status: ALLOCATED PORTABLE
remarks: Email address for spam or abuse complaints : abuse@sakura.ad.jp
changed: hm-changed@apnic.net 20101207
mnt-irt: IRT-JPNIC-JP
mnt-by: MAINT-JPNIC
mnt-lower: MAINT-JPNIC
source: APNIC

role: Japan Network Information Center
address: Urbannet-Kanda Bldg 4F
address: 3-6-2 Uchi-Kanda
address: Chiyoda-ku, Tokyo 101-0047,Japan
country: JP
phone: +81-3-5297-2311
fax-no: +81-3-5297-2312
e-mail: hostmaster@nic.ad.jp
admin-c: JI13-AP
tech-c: JE53-AP
nic-hdl: JNIC1-AP
mnt-by: MAINT-JPNIC
changed: hm-changed@apnic.net 20041222
changed: hm-changed@apnic.net 20050324
changed: ip-apnic@nic.ad.jp 20051027
changed: ip-apnic@nic.ad.jp 20120828
source: APNIC

inetnum: 49.212.80.0 - 49.212.80.255
netname: SAKURA-NET
descr: SAKURA Internet Inc.
country: JP
admin-c: KT749JP
tech-c: KW419JP
remarks: This information has been partially mirrored by APNIC from
remarks: JPNIC. To obtain more specific information, please use the
remarks: JPNIC WHOIS Gateway at
remarks: http://www.nic.ad.jp/en/db/whois/en-gateway.html or
remarks: whois.nic.ad.jp for WHOIS client. (The WHOIS client
remarks: defaults to Japanese output, use the /e switch for English
remarks: output)
changed: apnic-ftp@nic.ad.jp 20110217
source: JPNIC


In Page Analysis

Traffic Analysis

Magestic Backlinks

Daily Ranks

Rank Trend

Visitor Trend

Bounce Trend

HTML Analysis

HTML validation
  • 30 Errors
  • 28 Warnings
Ratio Text/Html

0.8003186404673394

Message Error
  • Warning Line 24, Column 101: cannot generate system identifier for general entity "v"
    …"http://platform.twitter.com/anywhere.js?id=zbTLfzThEzS5z0i8rroQ&v=1"></script>

    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 24, Column 101: general entity "v" not defined and no default entity
    …"http://platform.twitter.com/anywhere.js?id=zbTLfzThEzS5z0i8rroQ&v=1"></script>

    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 24, Column 102: reference not terminated by REFC delimiter
    …"http://platform.twitter.com/anywhere.js?id=zbTLfzThEzS5z0i8rroQ&v=1"></script>

    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 24, Column 102: reference to external entity in attribute value
    …"http://platform.twitter.com/anywhere.js?id=zbTLfzThEzS5z0i8rroQ&v=1"></script>

    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 24, Column 102: reference to entity "v" for which no system identifier could be generated
    …"http://platform.twitter.com/anywhere.js?id=zbTLfzThEzS5z0i8rroQ&v=1"></script>

    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 24, Column 100: entity was defined here
    …"http://platform.twitter.com/anywhere.js?id=zbTLfzThEzS5z0i8rroQ&v=1"></script>
  • Error Line 53, Column 92: required attribute "alt" not specified
    …rc="/images/title-index.png" width="460" height="150" title="Pideo 動画検索"/></h1>

    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 57, Column 95: there is no attribute "placeholder"
    …d ="q" name="q" value="" class="search-input" placeholder="検索キーワードを入力してください" />

    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 79, Column 24: there is no attribute "role"
        <div id="nav" role="navigation">

    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 82, Column 106: required attribute "alt" not specified
    …mg src="/images/icon/1311558131_2x2_grid.png" width="14" height="14"/></a></li>

    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 95, Column 99: there is no attribute "data-hatena-bookmark-layout"
    …k-button" data-hatena-bookmark-layout="standard" title="このエントリーをはてなブックマークに追加">…

    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 95, Column 391: there is no attribute "async"
    …/b.st-hatena.com/js/bookmark_button.js" charset="utf-8" async="async"></script>

    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 99, Column 77: there is no attribute "data-count"
    …ass="twitter-share-button" data-count="horizontal" data-via="haroxy" data-lang…

    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 99, Column 99: there is no attribute "data-via"
    …ton" data-count="horizontal" data-via="haroxy" data-lang="en">Tweet</a><script…

    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 99, Column 118: there is no attribute "data-lang"
    …rizontal" data-via="haroxy" data-lang="en">Tweet</a><script type="text/javascr…

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

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

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

  • Warning Line 102, Column 90: cannot generate system identifier for general entity "send"
    …hp?href=http%3A%2F%2Fwww.pideo.net%2F&send=false&layout=button_count&width=100…

    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 102, Column 90: general entity "send" not defined and no default entity
    …hp?href=http%3A%2F%2Fwww.pideo.net%2F&send=false&layout=button_count&width=100…

    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 102, Column 94: reference not terminated by REFC delimiter
    …ref=http%3A%2F%2Fwww.pideo.net%2F&send=false&layout=button_count&width=100&sho…

    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 102, Column 94: reference to external entity in attribute value
    …ref=http%3A%2F%2Fwww.pideo.net%2F&send=false&layout=button_count&width=100&sho…

    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 102, Column 94: reference to entity "send" for which no system identifier could be generated
    …ref=http%3A%2F%2Fwww.pideo.net%2F&send=false&layout=button_count&width=100&sho…

    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 102, Column 89: entity was defined here
    …php?href=http%3A%2F%2Fwww.pideo.net%2F&send=false&layout=button_count&width=10…
  • Warning Line 102, Column 101: cannot generate system identifier for general entity "layout"
    …p%3A%2F%2Fwww.pideo.net%2F&send=false&layout=button_count&width=100&show_faces…

    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 102, Column 101: general entity "layout" not defined and no default entity
    …p%3A%2F%2Fwww.pideo.net%2F&send=false&layout=button_count&width=100&show_faces…

    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 102, Column 107: reference not terminated by REFC delimiter
    …F%2Fwww.pideo.net%2F&send=false&layout=button_count&width=100&show_faces=false…

    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 102, Column 107: reference to external entity in attribute value
    …F%2Fwww.pideo.net%2F&send=false&layout=button_count&width=100&show_faces=false…

    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 102, Column 107: reference to entity "layout" for which no system identifier could be generated
    …F%2Fwww.pideo.net%2F&send=false&layout=button_count&width=100&show_faces=false…

    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 102, Column 100: entity was defined here
    …tp%3A%2F%2Fwww.pideo.net%2F&send=false&layout=button_count&width=100&show_face…
  • Warning Line 102, Column 121: cannot generate system identifier for general entity "width"
    …net%2F&send=false&layout=button_count&width=100&show_faces=false&action=like&c…

    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 102, Column 121: general entity "width" not defined and no default entity
    …net%2F&send=false&layout=button_count&width=100&show_faces=false&action=like&c…

    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 102, Column 126: reference not terminated by REFC delimiter
    …F&send=false&layout=button_count&width=100&show_faces=false&action=like&colors…

    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 102, Column 126: reference to external entity in attribute value
    …F&send=false&layout=button_count&width=100&show_faces=false&action=like&colors…

    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 102, Column 126: reference to entity "width" for which no system identifier could be generated
    …F&send=false&layout=button_count&width=100&show_faces=false&action=like&colors…

    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 102, Column 120: entity was defined here
    ….net%2F&send=false&layout=button_count&width=100&show_faces=false&action=like&…
  • Warning Line 102, Column 131: cannot generate system identifier for general entity "show_faces"
    …d=false&layout=button_count&width=100&show_faces=false&action=like&colorscheme…

    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 102, Column 131: general entity "show_faces" not defined and no default entity
    …d=false&layout=button_count&width=100&show_faces=false&action=like&colorscheme…

    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 102, Column 141: reference not terminated by REFC delimiter
    …yout=button_count&width=100&show_faces=false&action=like&colorscheme=light&fon…

    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 102, Column 141: reference to external entity in attribute value
    …yout=button_count&width=100&show_faces=false&action=like&colorscheme=light&fon…

    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 102, Column 141: reference to entity "show_faces" for which no system identifier could be generated
    …yout=button_count&width=100&show_faces=false&action=like&colorscheme=light&fon…

    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 102, Column 130: entity was defined here
    …nd=false&layout=button_count&width=100&show_faces=false&action=like&colorschem…
  • Warning Line 102, Column 148: cannot generate system identifier for general entity "action"
    …tton_count&width=100&show_faces=false&action=like&colorscheme=light&font=arial…

    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 102, Column 148: general entity "action" not defined and no default entity
    …tton_count&width=100&show_faces=false&action=like&colorscheme=light&font=arial…

    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 102, Column 154: reference not terminated by REFC delimiter
    …ount&width=100&show_faces=false&action=like&colorscheme=light&font=arial&heigh…

    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 102, Column 154: reference to external entity in attribute value
    …ount&width=100&show_faces=false&action=like&colorscheme=light&font=arial&heigh…

    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 102, Column 154: reference to entity "action" for which no system identifier could be generated
    …ount&width=100&show_faces=false&action=like&colorscheme=light&font=arial&heigh…

    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 102, Column 147: entity was defined here
    …utton_count&width=100&show_faces=false&action=like&colorscheme=light&font=aria…
  • Warning Line 102, Column 160: cannot generate system identifier for general entity "colorscheme"
    …idth=100&show_faces=false&action=like&colorscheme=light&font=arial&height=21" …

    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 102, Column 160: general entity "colorscheme" not defined and no default entity
    …idth=100&show_faces=false&action=like&colorscheme=light&font=arial&height=21" …

    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 102, Column 171: reference not terminated by REFC delimiter
    …ow_faces=false&action=like&colorscheme=light&font=arial&height=21" scrolling="…

    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 102, Column 171: reference to external entity in attribute value
    …ow_faces=false&action=like&colorscheme=light&font=arial&height=21" scrolling="…

    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 102, Column 171: reference to entity "colorscheme" for which no system identifier could be generated
    …ow_faces=false&action=like&colorscheme=light&font=arial&height=21" scrolling="…

    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 102, Column 159: entity was defined here
    …width=100&show_faces=false&action=like&colorscheme=light&font=arial&height=21"…
  • Warning Line 102, Column 178: cannot generate system identifier for general entity "font"
    …s=false&action=like&colorscheme=light&font=arial&height=21" scrolling="no" fra…

    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 102, Column 178: general entity "font" not defined and no default entity
    …s=false&action=like&colorscheme=light&font=arial&height=21" scrolling="no" fra…

    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 102, Column 182: reference not terminated by REFC delimiter
    …lse&action=like&colorscheme=light&font=arial&height=21" scrolling="no" framebo…

    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 102, Column 182: reference to external entity in attribute value
    …lse&action=like&colorscheme=light&font=arial&height=21" scrolling="no" framebo…

    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 102, Column 182: reference to entity "font" for which no system identifier could be generated
    …lse&action=like&colorscheme=light&font=arial&height=21" scrolling="no" framebo…

    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 102, Column 177: entity was defined here
    …es=false&action=like&colorscheme=light&font=arial&height=21" scrolling="no" fr…
  • Warning Line 102, Column 189: cannot generate system identifier for general entity "height"
    …ion=like&colorscheme=light&font=arial&height=21" scrolling="no" frameborder="0…

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

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

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

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

  • Error Line 102, Column 189: general entity "height" not defined and no default entity
    …ion=like&colorscheme=light&font=arial&height=21" scrolling="no" frameborder="0…

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

  • Warning Line 102, Column 195: reference not terminated by REFC delimiter
    …ke&colorscheme=light&font=arial&height=21" scrolling="no" frameborder="0" styl…

    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 102, Column 195: reference to external entity in attribute value
    …ke&colorscheme=light&font=arial&height=21" scrolling="no" frameborder="0" styl…

    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 102, Column 195: reference to entity "height" for which no system identifier could be generated
    …ke&colorscheme=light&font=arial&height=21" scrolling="no" frameborder="0" styl…

    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 102, Column 188: entity was defined here
    …tion=like&colorscheme=light&font=arial&height=21" scrolling="no" frameborder="…
  • Error Line 102, Column 313: there is no attribute "allowTransparency"
    … overflow:hidden; width:108px; height:21px;" allowTransparency="true"></iframe>

    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 105, Column 34: there is no attribute "data-size"
    <div class="g-plusone" data-size="medium" data-count="true"></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 105, Column 54: there is no attribute "data-count"
    <div class="g-plusone" data-size="medium" data-count="true"></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.

  • Warning Line 125, Column 1: unclosed end-tag requires SHORTTAG YES
    </div>

    The construct </foo<bar> is valid in HTML (it is an example of the rather obscure “Shorttags” feature) but its use is not recommended. In most cases, this is a typo that you will want to fix. If you really want to use shorttags, be aware that they are not well implemented by browsers.

Visitor Analysis

Daily Visitor

61.833 visits