Смотреть фильмы и сериалы онлайн. Ежедневные обновления, новинки кино и лучшие фильмы смотреть онлайн бесплатно ...

onfillm.ru
  • Domain Name
    onfillm.ru
  • Favicon
  • Google Page Rank
    0
  • Alexa Rank
    #34153
  • Page Size
    66.4 KB
  • Ip Address
    188.138.25.116
  • Heading
    H1: 0, H2: 1, H3: 15, H4: 5, H5: 0, H6: 0
  • Images
    3 GIF, 39 JPG, 5 PNG

Website Meta Analysis

  • Title
    Смотреть фильмы онлайн бесплатно и без регистрации. Только хиты и новинки кино на ONFILLM.RU!
  • Meta Keyword
    Онлайн фильмы, смотреть, фильмы онлайн, сериалы онлайн, онлайн в хорошем качестве, кино, просмотр, смотреть онлайн, кинотеатр online
  • Meta Description
    Смотреть фильмы и сериалы онлайн. Ежедневные обновления, новинки кино и лучшие фильмы смотреть онлайн бесплатно

Technical Analysis

  • Webserver
    nginx
  • Ip Address
    188.138.25.116
  • Domain Age
  • Javascript Library
    jquery, yui
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from onfillm.ru.

HTML Analysis

  • server: nginx
  • date: Sat, 07 Sep 2013 14:52:18 GMT
  • content-type: text/html; charset=UTF-8
  • connection: keep-alive
  • vary: Accept-Encoding
  • x-powered-by: PHP/5.2.17
  • 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
% By submitting a query to RIPN's Whois Service
% you agree to abide by the following terms of use:
% http://www.ripn.net/about/servpol.html#3.2 (in Russian)
% http://www.ripn.net/about/en/servpol.html#3.2 (in English).

domain: ONFILLM.RU
nserver: ns1.onfillm.ru. 85.25.117.142
nserver: ns2.onfillm.ru. 85.25.19.185
state: REGISTERED, DELEGATED, UNVERIFIED
person: Private Person
registrar: REGRU-REG-RIPN
admin-contact: http://www.reg.ru/whois/admin_contact
created: 2011.07.29
paid-till: 2013.07.29
free-date: 2013.08.29
source: TCI

Last updated on 2012.11.03 04:16:33 MSK

DNS Analysis


DNS servers
ns1.onfillm.ru [85.25.117.142]
ns2.onfillm.ru [85.25.19.185]


DNS Records

Answer records
onfillm.ru TXT v=spf1 ip4:85.25.117.142 a mx ~all 3600s
onfillm.ru SOA
server: ns1.vipserver.su
email: root@vipserver.su
serial: 2011080604
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 86400
3600s
onfillm.ru NS  ns1.onfillm.ru 3600s
onfillm.ru NS  ns2.onfillm.ru 3600s
onfillm.ru MX
preference: 10
exchange: mail.onfillm.ru
3600s
onfillm.ru MX
preference: 20
exchange: mail.onfillm.ru
3600s
onfillm.ru A 85.25.19.185 3600s

Authority records

Additional records
ns1.onfillm.ru A 85.25.117.142 3600s
ns2.onfillm.ru A 85.25.19.185 3600s
mail.onfillm.ru A 85.25.19.185 3600s

IP 188.138.25.116 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 2 Errors
  • 3 Warnings
Ratio Text/Html
  • 0.6907412036288247
Message Error
  • Warning Line 227, Column 95: cannot generate system identifier for general entity "f"
    …ipt' src='http://c.am11.ru/code/bn/js.php?u=20303&f=3'></script><!--/noindex-->

    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 227, Column 95: general entity "f" not defined and no default entity
    …ipt' src='http://c.am11.ru/code/bn/js.php?u=20303&f=3'></script><!--/noindex-->

    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 227, Column 96: reference not terminated by REFC delimiter
    …ipt' src='http://c.am11.ru/code/bn/js.php?u=20303&f=3'></script><!--/noindex-->

    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 227, Column 96: reference to external entity in attribute value
    …ipt' src='http://c.am11.ru/code/bn/js.php?u=20303&f=3'></script><!--/noindex-->

    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 227, Column 96: reference to entity "f" for which no system identifier could be generated
    …ipt' src='http://c.am11.ru/code/bn/js.php?u=20303&f=3'></script><!--/noindex-->

    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 227, Column 94: entity was defined here
    …ipt' src='http://c.am11.ru/code/bn/js.php?u=20303&f=3'></script><!--/noindex-->
  • Warning Line 800, Column 49: cannot generate system identifier for general entity "jq"
    ….src="http://am10.ru/code.php?type=cu&jq="+am_jq+"&rand="+am_rand+"&u=20303&lo…

    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 800, Column 49: general entity "jq" not defined and no default entity
    ….src="http://am10.ru/code.php?type=cu&jq="+am_jq+"&rand="+am_rand+"&u=20303&lo…

    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 800, Column 51: reference not terminated by REFC delimiter
    …rc="http://am10.ru/code.php?type=cu&jq="+am_jq+"&rand="+am_rand+"&u=20303&loc=…

    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.

  • Error Line 800, Column 51: reference to entity "jq" for which no system identifier could be generated
    …rc="http://am10.ru/code.php?type=cu&jq="+am_jq+"&rand="+am_rand+"&u=20303&loc=…

    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 800, Column 48: entity was defined here
    …u.src="http://am10.ru/code.php?type=cu&jq="+am_jq+"&rand="+am_rand+"&u=20303&l…
  • Warning Line 800, Column 62: cannot generate system identifier for general entity "rand"
    …am10.ru/code.php?type=cu&jq="+am_jq+"&rand="+am_rand+"&u=20303&loc="+am_loc+"&…

    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 800, Column 62: general entity "rand" not defined and no default entity
    …am10.ru/code.php?type=cu&jq="+am_jq+"&rand="+am_rand+"&u=20303&loc="+am_loc+"&…

    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 800, Column 66: reference not terminated by REFC delimiter
    ….ru/code.php?type=cu&jq="+am_jq+"&rand="+am_rand+"&u=20303&loc="+am_loc+"&ref=…

    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.

  • Error Line 800, Column 66: reference to entity "rand" for which no system identifier could be generated
    ….ru/code.php?type=cu&jq="+am_jq+"&rand="+am_rand+"&u=20303&loc="+am_loc+"&ref=…

    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 800, Column 61: entity was defined here
    …/am10.ru/code.php?type=cu&jq="+am_jq+"&rand="+am_rand+"&u=20303&loc="+am_loc+"…
  • Warning Line 800, Column 79: cannot generate system identifier for general entity "u"
    …type=cu&jq="+am_jq+"&rand="+am_rand+"&u=20303&loc="+am_loc+"&ref="+am_ref+"&ti…

    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 800, Column 79: general entity "u" not defined and no default entity
    …type=cu&jq="+am_jq+"&rand="+am_rand+"&u=20303&loc="+am_loc+"&ref="+am_ref+"&ti…

    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 800, Column 80: reference not terminated by REFC delimiter
    …ype=cu&jq="+am_jq+"&rand="+am_rand+"&u=20303&loc="+am_loc+"&ref="+am_ref+"&tit…

    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.

  • Error Line 800, Column 80: reference to entity "u" for which no system identifier could be generated
    …ype=cu&jq="+am_jq+"&rand="+am_rand+"&u=20303&loc="+am_loc+"&ref="+am_ref+"&tit…

    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 800, Column 78: entity was defined here
    …?type=cu&jq="+am_jq+"&rand="+am_rand+"&u=20303&loc="+am_loc+"&ref="+am_ref+"&t…
  • Warning Line 800, Column 87: cannot generate system identifier for general entity "loc"
    …jq="+am_jq+"&rand="+am_rand+"&u=20303&loc="+am_loc+"&ref="+am_ref+"&title="+am…

    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 800, Column 87: general entity "loc" not defined and no default entity
    …jq="+am_jq+"&rand="+am_rand+"&u=20303&loc="+am_loc+"&ref="+am_ref+"&title="+am…

    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 800, Column 90: reference not terminated by REFC delimiter
    …"+am_jq+"&rand="+am_rand+"&u=20303&loc="+am_loc+"&ref="+am_ref+"&title="+am_ti…

    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.

  • Error Line 800, Column 90: reference to entity "loc" for which no system identifier could be generated
    …"+am_jq+"&rand="+am_rand+"&u=20303&loc="+am_loc+"&ref="+am_ref+"&title="+am_ti…

    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 800, Column 86: entity was defined here
    …&jq="+am_jq+"&rand="+am_rand+"&u=20303&loc="+am_loc+"&ref="+am_ref+"&title="+a…
  • Warning Line 800, Column 102: cannot generate system identifier for general entity "ref"
    …m_jq+"&rand="+am_rand+"&u=20303&loc="+am_loc+"&ref="+am_ref+"&title="+am_title;

    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 800, Column 102: general entity "ref" not defined and no default entity
    …m_jq+"&rand="+am_rand+"&u=20303&loc="+am_loc+"&ref="+am_ref+"&title="+am_title;

    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 800, Column 105: reference not terminated by REFC delimiter
    …m_jq+"&rand="+am_rand+"&u=20303&loc="+am_loc+"&ref="+am_ref+"&title="+am_title;

    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.

  • Error Line 800, Column 105: reference to entity "ref" for which no system identifier could be generated
    …m_jq+"&rand="+am_rand+"&u=20303&loc="+am_loc+"&ref="+am_ref+"&title="+am_title;

    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 800, Column 101: entity was defined here
    …m_jq+"&rand="+am_rand+"&u=20303&loc="+am_loc+"&ref="+am_ref+"&title="+am_title;
  • Warning Line 800, Column 117: cannot generate system identifier for general entity "title"
    …m_jq+"&rand="+am_rand+"&u=20303&loc="+am_loc+"&ref="+am_ref+"&title="+am_title;

    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 800, Column 117: general entity "title" not defined and no default entity
    …m_jq+"&rand="+am_rand+"&u=20303&loc="+am_loc+"&ref="+am_ref+"&title="+am_title;

    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 800, Column 122: reference not terminated by REFC delimiter
    …m_jq+"&rand="+am_rand+"&u=20303&loc="+am_loc+"&ref="+am_ref+"&title="+am_title;

    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.

  • Error Line 800, Column 122: reference to entity "title" for which no system identifier could be generated
    …m_jq+"&rand="+am_rand+"&u=20303&loc="+am_loc+"&ref="+am_ref+"&title="+am_title;

    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 800, Column 116: entity was defined here
    …m_jq+"&rand="+am_rand+"&u=20303&loc="+am_loc+"&ref="+am_ref+"&title="+am_title;
  • Warning Line 803, Column 51: reference not terminated by REFC delimiter
    …rc="http://am10.ru/code.php?type=sb&jq="+am_jq+"&rand="+am_rand+"&u=20303&loc=…

    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.

  • Error Line 803, Column 51: reference to entity "jq" for which no system identifier could be generated
    …rc="http://am10.ru/code.php?type=sb&jq="+am_jq+"&rand="+am_rand+"&u=20303&loc=…

    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 800, Column 48: entity was defined here
    …u.src="http://am10.ru/code.php?type=cu&jq="+am_jq+"&rand="+am_rand+"&u=20303&l…
  • Warning Line 803, Column 66: reference not terminated by REFC delimiter
    ….ru/code.php?type=sb&jq="+am_jq+"&rand="+am_rand+"&u=20303&loc="+am_loc+"&ref=…

    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.

  • Error Line 803, Column 66: reference to entity "rand" for which no system identifier could be generated
    ….ru/code.php?type=sb&jq="+am_jq+"&rand="+am_rand+"&u=20303&loc="+am_loc+"&ref=…

    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 800, Column 61: entity was defined here
    …/am10.ru/code.php?type=cu&jq="+am_jq+"&rand="+am_rand+"&u=20303&loc="+am_loc+"…
  • Warning Line 803, Column 80: reference not terminated by REFC delimiter
    …ype=sb&jq="+am_jq+"&rand="+am_rand+"&u=20303&loc="+am_loc+"&ref="+am_ref+"&tit…

    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.

  • Error Line 803, Column 80: reference to entity "u" for which no system identifier could be generated
    …ype=sb&jq="+am_jq+"&rand="+am_rand+"&u=20303&loc="+am_loc+"&ref="+am_ref+"&tit…

    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 800, Column 78: entity was defined here
    …?type=cu&jq="+am_jq+"&rand="+am_rand+"&u=20303&loc="+am_loc+"&ref="+am_ref+"&t…
  • Warning Line 803, Column 90: reference not terminated by REFC delimiter
    …"+am_jq+"&rand="+am_rand+"&u=20303&loc="+am_loc+"&ref="+am_ref+"&title="+am_ti…

    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.

  • Error Line 803, Column 90: reference to entity "loc" for which no system identifier could be generated
    …"+am_jq+"&rand="+am_rand+"&u=20303&loc="+am_loc+"&ref="+am_ref+"&title="+am_ti…

    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 800, Column 86: entity was defined here
    …&jq="+am_jq+"&rand="+am_rand+"&u=20303&loc="+am_loc+"&ref="+am_ref+"&title="+a…
  • Warning Line 803, Column 105: reference not terminated by REFC delimiter
    …m_jq+"&rand="+am_rand+"&u=20303&loc="+am_loc+"&ref="+am_ref+"&title="+am_title;

    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.

  • Error Line 803, Column 105: reference to entity "ref" for which no system identifier could be generated
    …m_jq+"&rand="+am_rand+"&u=20303&loc="+am_loc+"&ref="+am_ref+"&title="+am_title;

    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 800, Column 101: entity was defined here
    …m_jq+"&rand="+am_rand+"&u=20303&loc="+am_loc+"&ref="+am_ref+"&title="+am_title;
  • Warning Line 803, Column 122: reference not terminated by REFC delimiter
    …m_jq+"&rand="+am_rand+"&u=20303&loc="+am_loc+"&ref="+am_ref+"&title="+am_title;

    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.

  • Error Line 803, Column 122: reference to entity "title" for which no system identifier could be generated
    …m_jq+"&rand="+am_rand+"&u=20303&loc="+am_loc+"&ref="+am_ref+"&title="+am_title;

    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 800, Column 116: entity was defined here
    …m_jq+"&rand="+am_rand+"&u=20303&loc="+am_loc+"&ref="+am_ref+"&title="+am_title;

Visitor Analysis

Daily Visitor
  • 3.150 visits