Free Download Latest Bollywood, Hollywood, Other 3gp Mobile Movies !! ...

moviesluv.com
  • Domain Name
    moviesluv.com
  • Favicon
  • Google Page Rank
    2
  • Alexa Rank
    #24619
  • Page Size
    15.2 KB
  • Ip Address
    46.28.48.172
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    8 GIF, 0 JPG, 41 PNG

Website Meta Analysis

  • Title
    MoviesLuv.Com | Free Download Latest Bollywood, Hollywood, Other 3gp Mobile Movies !!
  • Meta Keyword
    Free Download Latest Mobile 3gp Bollywood Hollywood Hindi Dubbed Other Movies
  • Meta Description
    Free Download Latest Bollywood, Hollywood, Other 3gp Mobile Movies !!

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    46.28.48.172
  • Domain Age
    1 Years, 0 Months, 17 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Wed, 28 Aug 2013 01:55:45 GMT
  • server: Apache
  • x-powered-by: PHP/5.3.25
  • connection: close
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Name: moviesluv.com
Registrar: Name.com LLC

Expiration Date: 2013-08-15 05:25:51
Creation Date: 2012-08-15 05:25:51

Name Servers:
ns1.o2videos.com
ns2.o2videos.com

REGISTRANT CONTACT INFO
O2Videos.Com
O2 Videos
32/B
Karol Bagh
New Delhi
New Delhi
100042
IN
Phone: +91.9810645721
Email Address: email

ADMINISTRATIVE CONTACT INFO
O2Videos.Com
O2 Videos
32/B
Karol Bagh
New Delhi
New Delhi
100042
IN
Phone: +91.9810645721
Email Address: email

TECHNICAL CONTACT INFO
O2Videos.Com
O2 Videos
32/B
Karol Bagh
New Delhi
New Delhi
100042
IN
Phone: +91.9810645721
Email Address: email

BILLING CONTACT INFO
O2Videos.Com
O2 Videos
32/B
Karol Bagh
New Delhi
New Delhi
100042
IN
Phone: +91.9810645721
Email Address: email

DNS Analysis


DNS servers
ns1.o2videos.com [184.154.116.186]
ns2.o2videos.com [184.154.116.187]


DNS Records

Answer records
moviesluv.com TXT v=spf1 +a +mx +ip4:184.154.116.186 ?all 14400s
moviesluv.com MX
preference: 0
exchange: moviesluv.com
14400s
moviesluv.com SOA
server: ns1.o2videos.com
email: o2videos@com.gmail.com
serial: 2013032500
refresh: 86400
retry: 7200
expire: 3600000
minimum ttl: 86400
86400s
moviesluv.com NS  ns2.o2videos.com 86400s
moviesluv.com NS  ns1.o2videos.com 86400s
moviesluv.com A 184.154.116.186 14400s

Authority records

Additional records
moviesluv.com A 184.154.116.186 14400s
ns1.o2videos.com A 184.154.116.186 14400s
ns2.o2videos.com A 184.154.116.187 14400s

IP 46.28.48.172 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 30 Errors
  • 27 Warnings
Ratio Text/Html
  • 0.6137223469060596
Message Error
  • Error Line 14, Column 365: required attribute "alt" not specified
    … src="images/wechat2.jpg" border="0" /></a><br /><img src="images/ad.png" alt=…

    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 14, Column 503: required attribute "alt" not specified
    …img src="images/one6.png" border="0" /></a><br /><img src="images/ad.png" alt=…

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

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 29, Column 23: document type does not allow element "style" here
    <style type="text/css">

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Warning Line 53, Column 100: cannot generate system identifier for general entity "width"
    …tp%3A%2F%2Fwww.facebook.com/MoviesLuv&width=100&show_faces=false&layout=button…

    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 53, Column 100: general entity "width" not defined and no default entity
    …tp%3A%2F%2Fwww.facebook.com/MoviesLuv&width=100&show_faces=false&layout=button…

    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 53, Column 105: reference not terminated by REFC delimiter
    …%2F%2Fwww.facebook.com/MoviesLuv&width=100&show_faces=false&layout=button_coun…

    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 53, Column 105: reference to external entity in attribute value
    …%2F%2Fwww.facebook.com/MoviesLuv&width=100&show_faces=false&layout=button_coun…

    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 53, Column 105: reference to entity "width" for which no system identifier could be generated
    …%2F%2Fwww.facebook.com/MoviesLuv&width=100&show_faces=false&layout=button_coun…

    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 53, Column 99: entity was defined here
    …ttp%3A%2F%2Fwww.facebook.com/MoviesLuv&width=100&show_faces=false&layout=butto…
  • Warning Line 53, Column 110: cannot generate system identifier for general entity "show_faces"
    …Fwww.facebook.com/MoviesLuv&width=100&show_faces=false&layout=button_count&act…

    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 53, Column 110: general entity "show_faces" not defined and no default entity
    …Fwww.facebook.com/MoviesLuv&width=100&show_faces=false&layout=button_count&act…

    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 53, Column 120: reference not terminated by REFC delimiter
    …ook.com/MoviesLuv&width=100&show_faces=false&layout=button_count&action=like&c…

    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 53, Column 120: reference to external entity in attribute value
    …ook.com/MoviesLuv&width=100&show_faces=false&layout=button_count&action=like&c…

    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 53, Column 120: reference to entity "show_faces" for which no system identifier could be generated
    …ook.com/MoviesLuv&width=100&show_faces=false&layout=button_count&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.

  • Info Line 53, Column 109: entity was defined here
    …2Fwww.facebook.com/MoviesLuv&width=100&show_faces=false&layout=button_count&ac…
  • Warning Line 53, Column 127: cannot generate system identifier for general entity "layout"
    …/MoviesLuv&width=100&show_faces=false&layout=button_count&action=like&colorsch…

    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 53, Column 127: general entity "layout" not defined and no default entity
    …/MoviesLuv&width=100&show_faces=false&layout=button_count&action=like&colorsch…

    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 53, Column 133: reference not terminated by REFC delimiter
    …sLuv&width=100&show_faces=false&layout=button_count&action=like&colorscheme=li…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 53, Column 133: reference to external entity in attribute value
    …sLuv&width=100&show_faces=false&layout=button_count&action=like&colorscheme=li…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 53, Column 133: reference to entity "layout" for which no system identifier could be generated
    …sLuv&width=100&show_faces=false&layout=button_count&action=like&colorscheme=li…

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

  • Info Line 53, Column 126: entity was defined here
    …m/MoviesLuv&width=100&show_faces=false&layout=button_count&action=like&colorsc…
  • Warning Line 53, Column 147: cannot generate system identifier for general entity "action"
    …&show_faces=false&layout=button_count&action=like&colorscheme=light&height=20"…

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

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

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

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

  • Error Line 53, Column 147: general entity "action" not defined and no default entity
    …&show_faces=false&layout=button_count&action=like&colorscheme=light&height=20"…

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

  • Warning Line 53, Column 153: reference not terminated by REFC delimiter
    …faces=false&layout=button_count&action=like&colorscheme=light&height=20" scrol…

    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 53, Column 153: reference to external entity in attribute value
    …faces=false&layout=button_count&action=like&colorscheme=light&height=20" scrol…

    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 53, Column 153: reference to entity "action" for which no system identifier could be generated
    …faces=false&layout=button_count&action=like&colorscheme=light&height=20" scrol…

    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 53, Column 146: entity was defined here
    …0&show_faces=false&layout=button_count&action=like&colorscheme=light&height=20…
  • Warning Line 53, Column 159: cannot generate system identifier for general entity "colorscheme"
    …false&layout=button_count&action=like&colorscheme=light&height=20" scrolling="…

    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 53, Column 159: general entity "colorscheme" not defined and no default entity
    …false&layout=button_count&action=like&colorscheme=light&height=20" 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.

  • Warning Line 53, Column 170: reference not terminated by REFC delimiter
    …t=button_count&action=like&colorscheme=light&height=20" 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 53, Column 170: reference to external entity in attribute value
    …t=button_count&action=like&colorscheme=light&height=20" 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 53, Column 170: reference to entity "colorscheme" for which no system identifier could be generated
    …t=button_count&action=like&colorscheme=light&height=20" 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 53, Column 158: entity was defined here
    …=false&layout=button_count&action=like&colorscheme=light&height=20" scrolling=…
  • Warning Line 53, Column 177: cannot generate system identifier for general entity "height"
    …n_count&action=like&colorscheme=light&height=20" 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 53, Column 177: general entity "height" not defined and no default entity
    …n_count&action=like&colorscheme=light&height=20" 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 53, Column 183: reference not terminated by REFC delimiter
    …t&action=like&colorscheme=light&height=20" 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 53, Column 183: reference to external entity in attribute value
    …t&action=like&colorscheme=light&height=20" 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 53, Column 183: reference to entity "height" for which no system identifier could be generated
    …t&action=like&colorscheme=light&height=20" 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 53, Column 176: entity was defined here
    …on_count&action=like&colorscheme=light&height=20" scrolling="no" frameborder="…
  • Error Line 53, Column 301: there is no attribute "allowTransparency"
    … overflow:hidden; width:100px; height:20px;" 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 56, Column 91: required attribute "alt" not specified
    …it.ly/One_From_Movieluv"><img src="images/one16.png" border="0" /></a></center>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Warning Line 58, Column 85: cannot generate system identifier for general entity "pub"
    …down3.ucweb.com/ucbrowser/en/?bid=354&pub=qx@o2cinemas&title=moviesluv&url=htt…

    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 58, Column 85: general entity "pub" not defined and no default entity
    …down3.ucweb.com/ucbrowser/en/?bid=354&pub=qx@o2cinemas&title=moviesluv&url=htt…

    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 58, Column 88: reference not terminated by REFC delimiter
    …n3.ucweb.com/ucbrowser/en/?bid=354&pub=qx@o2cinemas&title=moviesluv&url=http:/…

    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 58, Column 88: reference to external entity in attribute value
    …n3.ucweb.com/ucbrowser/en/?bid=354&pub=qx@o2cinemas&title=moviesluv&url=http:/…

    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 58, Column 88: reference to entity "pub" for which no system identifier could be generated
    …n3.ucweb.com/ucbrowser/en/?bid=354&pub=qx@o2cinemas&title=moviesluv&url=http:/…

    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 58, Column 84: entity was defined here
    …/down3.ucweb.com/ucbrowser/en/?bid=354&pub=qx@o2cinemas&title=moviesluv&url=ht…
  • Warning Line 58, Column 102: cannot generate system identifier for general entity "title"
    …cbrowser/en/?bid=354&pub=qx@o2cinemas&title=moviesluv&url=http://moviesluv.com…

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

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

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

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

  • Error Line 58, Column 102: general entity "title" not defined and no default entity
    …cbrowser/en/?bid=354&pub=qx@o2cinemas&title=moviesluv&url=http://moviesluv.com…

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

  • Warning Line 58, Column 107: reference not terminated by REFC delimiter
    …ser/en/?bid=354&pub=qx@o2cinemas&title=moviesluv&url=http://moviesluv.com/">Ho…

    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 58, Column 107: reference to external entity in attribute value
    …ser/en/?bid=354&pub=qx@o2cinemas&title=moviesluv&url=http://moviesluv.com/">Ho…

    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 58, Column 107: reference to entity "title" for which no system identifier could be generated
    …ser/en/?bid=354&pub=qx@o2cinemas&title=moviesluv&url=http://moviesluv.com/">Ho…

    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 58, Column 101: entity was defined here
    …ucbrowser/en/?bid=354&pub=qx@o2cinemas&title=moviesluv&url=http://moviesluv.co…
  • Warning Line 58, Column 118: cannot generate system identifier for general entity "url"
    …=354&pub=qx@o2cinemas&title=moviesluv&url=http://moviesluv.com/">Hot Downloads…

    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 58, Column 118: general entity "url" not defined and no default entity
    …=354&pub=qx@o2cinemas&title=moviesluv&url=http://moviesluv.com/">Hot Downloads…

    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 58, Column 121: reference not terminated by REFC delimiter
    …4&pub=qx@o2cinemas&title=moviesluv&url=http://moviesluv.com/">Hot Downloads ! …

    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 58, Column 121: reference to external entity in attribute value
    …4&pub=qx@o2cinemas&title=moviesluv&url=http://moviesluv.com/">Hot Downloads ! …

    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 58, Column 121: reference to entity "url" for which no system identifier could be generated
    …4&pub=qx@o2cinemas&title=moviesluv&url=http://moviesluv.com/">Hot Downloads ! …

    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 58, Column 117: entity was defined here
    …d=354&pub=qx@o2cinemas&title=moviesluv&url=http://moviesluv.com/">Hot Download…
  • Error Line 59, Column 95: required attribute "alt" not specified
    …y/Wech_From_Moviesluv"><img src="images/wechat3.jpg" border="0" /></a></center>

    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 82, Column 98: required attribute "alt" not specified
    …ames365_from_Moviesluv"><img src="images/games2.jpg" border="0" /></a></center>

    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 85, Column 288: ID "smaatoad" already defined
    …ges/ad.png" alt="&#187;" />&nbsp;<div id="smaatoad" style="padding: 0px"></div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 14, Column 621: ID "smaatoad" first defined here
    …ges/ad.png" alt="&#187;" />&nbsp;<div id="smaatoad" style="padding: 0px"></div>
  • Error Line 86, Column 13: ID "smaatoAdDisplay" already defined
    <script id="smaatoAdDisplay" language="javascript" type="text/javascript"

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 15, Column 13: ID "smaatoAdDisplay" first defined here
    <script id="smaatoAdDisplay" language="javascript" type="text/javascript"
  • Error Line 89, Column 8: required attribute "type" not specified
    <script>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 97, Column 196: required attribute "alt" not specified
    …//bit.ly/One_From_Movieluv"><img src="images/one17.png" border="0" /></a></div>

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

Visitor Analysis

Daily Visitor
  • 6.533 visits