maintenance - we will be back soon! New Software, New Design - Stronger, Faster, Better Affliate? Pending payment? Write to: [email protected] ...

flashx.tv
  • Domain Name
    flashx.tv
  • Favicon
  • Google Page Rank
    0
  • Alexa Rank
    #1151
  • Page Size
    6 KB
  • Ip Address
    104.28.8.42
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 0 JPG, 0 PNG

Website Meta Analysis

  • Title
    flashx.tv - we will be back soon!
  • Meta Keyword
  • Meta Description
    maintenance - we will be back soon! New Software, New Design - Stronger, Faster, Better Affliate? Pending payment? Write to: [email protected]

Technical Analysis

  • Webserver
    cloudflare-nginx
  • Ip Address
    104.28.8.42
  • Domain Age
    1 Years, 10 Months, 29 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from flashx.tv.

HTML Analysis

  • date: Sun, 24 Aug 2014 07:26:18 GMT
  • content-type: text/html
  • connection: keep-alive
  • last-modified: Wed, 20 Aug 2014 23:39:10 GMT
  • etag: W/"0e3b9f0cfbccf1:0"
  • vary: Accept-Encoding
  • server: cloudflare-nginx
  • cf-ray: 15edd222460210a5-ORD
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
=-=-=-=

Registration Service Provided By: Namecheap.com
Contact: email
Visit: http://namecheap.com

Domain name: flashx.tv

Registrant Contact:
WhoisGuard
WhoisGuard Protected ()

Fax:
11400 W. Olympic Blvd. Suite 200
Los Angeles, CA 90064
US

Administrative Contact:
WhoisGuard
WhoisGuard Protected ( email )
+1.6613102107
Fax: +1.6613102107
11400 W. Olympic Blvd. Suite 200
Los Angeles, CA 90064
US

Technical Contact:
WhoisGuard
WhoisGuard Protected ( email )
+1.6613102107
Fax: +1.6613102107
11400 W. Olympic Blvd. Suite 200
Los Angeles, CA 90064
US

Status: Locked

Name Servers:
ns1.mgw-dns.de
ns2.mgw-dns.de
ns3.mgw-dns.de

Creation date: 01 Sep 2011 18:16:00
Expiration date: 01 Sep 2014 10:16:00




=-=-=-=
The data in this whois database is provided to you for information
purposes only, that is, to assist you in obtaining information about or
related to a domain name registration record. We make this information
available "as is," and do not guarantee its accuracy. By submitting a
whois query, you agree that you will use this data only for lawful
purposes and that, under no circumstances will you use this data to: (1)
enable high volume, automated, electronic processes that stress or load
this whois database system providing you this information; or (2) allow,
enable, or otherwise support the transmission of mass unsolicited,
commercial advertising or solicitations via direct mail, electronic
mail, or by telephone. The compilation, repackaging, dissemination or
other use of this data is expressly prohibited without prior written
consent from us.

We reserve the right to modify these terms at any time. By submitting
this query, you agree to abide by these terms.
Version 6.3 4/3/2002

DNS Analysis


DNS servers
ns1.mgw-dns.de [217.70.142.66]
ns2.mgw-dns.de [213.239.206.103]
ns3.mgw-dns.de [46.165.212.97]

DNS Records

Answer records
flashx.tv TXT v=spf1 include:ox.registrar-servers.com ip4:64.22.89.133 ip4:64.22.89.134 -all 3600s
flashx.tv A 109.163.229.158 3600s
flashx.tv NS  ns3.mgw-dns.de 86400s
flashx.tv MX
preference: 20
exchange: oxmail.registrar-servers.com
3600s
flashx.tv NS  ns2.mgw-dns.de 86400s
flashx.tv NS  ns1.mgw-dns.de 86400s
flashx.tv SOA
server: ns1.mgw-dns.de
email: hostmaster@mgw-media.de
serial: 2012121004
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 3600
86400s

Authority records

Additional records
ns3.mgw-dns.de A 46.165.212.97 3600s
ns2.mgw-dns.de A 213.239.206.103 3600s
ns2.mgw-dns.de 28 [16 bytes] 3600s
ns3.mgw-dns.de 28 [16 bytes] 3600s
ns1.mgw-dns.de A 217.70.142.66 3600s

IP 104.28.8.42 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 19 Errors
  • 16 Warnings
Ratio Text/Html
  • 0.25329858283108
Message Error
  • Error Line 9, Column 63: end tag for "link" omitted, but OMITTAG NO was specified
    <link rel="shortcut icon" href="http://flashx.tv/favicon.ico">

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

  • Info Line 9, Column 1: start tag was here
    <link rel="shortcut icon" href="http://flashx.tv/favicon.ico">
  • Error Line 43, Column 215: document type does not allow element "noscript" here; assuming missing "object" start-tag
    …lashx.tv"}; atrk ();</script><noscript><img src="https://d5nxst8fruw4z.cloudfr…
  • Error Line 53, 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 57, Column 105: document type does not allow element "link" here
    …f="http://flashx.tv/styles/global/jquery_ui.css" type="text/css" media="all" />

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

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

  • Error Line 88, Column 7: required attribute "type" not specified
    <style>

    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 88, Column 7: document type does not allow element "style" here
    <style>

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

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

  • Error Line 96, Column 100: document type does not allow element "link" here
    …" href="http://flashx.tv/plugins/cb_cinema/css/cb_cinema.css" media="screen" />

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

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

  • Error Line 208, Column 74: document type does not allow element "div" here
    …="float: left; display: inline-block;"><img src="'+imageurl+'/ajax-loader.gif"…

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

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

  • Error Line 208, Column 114: required attribute "alt" not specified
    …img src="'+imageurl+'/ajax-loader.gif"></div><div style="float: left; line-hei…

    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 208, Column 120: end tag for "img" omitted, but OMITTAG NO was specified
    …c="'+imageurl+'/ajax-loader.gif"></div><div style="float: left; line-height: 1…

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

  • Info Line 208, Column 75: start tag was here
    …"float: left; display: inline-block;"><img src="'+imageurl+'/ajax-loader.gif">…
  • Error Line 208, Column 182: document type does not allow element "div" here
    …; line-height: 16px; padding-left:5px">'+lang.remoteUploadFile+'</div><div cla…

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

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

  • Error Line 208, Column 232: document type does not allow element "div" here
    …; padding-left:5px">'+lang.remoteUploadFile+'</div><div class="clear"></div>');

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

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

  • Error Line 233, Column 75: document type does not allow element "span" here
    …		.before('<span id="updateVideoDataLoading" style="margin-right:5px"></span>')

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

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

  • Error Line 237, Column 82: document type does not allow element "input" here
    …		.after('<input type="hidden" name="videoid" value="'+vid+'" id="videoid" />')

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

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

  • Error Line 238, Column 86: document type does not allow element "input" here
    …ter('<input type="hidden" name="updateVideo" value="yes" id="updateVideo" />');

    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 255, Column 51: cannot generate system identifier for general entity "jsoncallback"
    …$.getJSON(result_page+"?file_name="+file_name+"&jsoncallback=?", function(data)

    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 255, Column 51: general entity "jsoncallback" not defined and no default entity
    …$.getJSON(result_page+"?file_name="+file_name+"&jsoncallback=?", function(data)

    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 255, Column 63: reference not terminated by REFC delimiter
    …$.getJSON(result_page+"?file_name="+file_name+"&jsoncallback=?", function(data)

    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 255, Column 63: reference to entity "jsoncallback" for which no system identifier could be generated
    …$.getJSON(result_page+"?file_name="+file_name+"&jsoncallback=?", function(data)

    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 255, Column 50: entity was defined here
    …$.getJSON(result_page+"?file_name="+file_name+"&jsoncallback=?", function(data)
  • Warning Line 288, Column 22: character "<" is the first character of a delimiter but occurred as data
    					if(perc_download<100 && !force_stop)

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 288, Column 27: character "&" is the first character of a delimiter but occurred as data
    					if(perc_download<100 && !force_stop)

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 288, Column 28: character "&" is the first character of a delimiter but occurred as data
    					if(perc_download<100 && !force_stop)

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 291, Column 33: character "&" is the first character of a delimiter but occurred as data
    					else if(perc_download==100 && total>1)

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 291, Column 34: character "&" is the first character of a delimiter but occurred as data
    					else if(perc_download==100 && total>1)

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 324, 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 333, Column 30: required attribute "type" not specified
    <script language="Javascript">

    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 452, Column 25: character "&" is the first character of a delimiter but occurred as data
    	} else if(window.opera && window.print) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 452, Column 26: character "&" is the first character of a delimiter but occurred as data
    	} else if(window.opera && window.print) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 464, Column 7: end tag for "object" omitted, but OMITTAG NO was specified
    </head>

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

  • Info Line 43, Column 206: start tag was here
    …domain:"flashx.tv"}; atrk ();</script><noscript><img src="https://d5nxst8fruw4…
  • Error Line 478, Column 247: end tag for "img" omitted, but OMITTAG NO was specified
    …="logo_icon" title="flashX.tv - A way to broadcast yourself"  class="logo"></a>

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

  • Info Line 478, Column 32: start tag was here
        <a href="http://flashx.tv"><img src="http://flashx.tv/logo.png" alt="flashX…
  • Error Line 526, Column 18: ID "container" already defined
            <div id="container" class="container clearfix" >

    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 472, Column 10: ID "container" first defined here
    <div id="container" class="container clearfix">
  • Error Line 531, Column 37: end tag for "br" omitted, but OMITTAG NO was specified
            <div><div align="right"><br><iframe src="//www.facebook.com/plugins/lik…

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

  • Info Line 531, Column 33: start tag was here
            <div><div align="right"><br><iframe src="//www.facebook.com/plugins/lik…
  • Error Line 531, Column 386: there is no attribute "allowtransparency"
    …50px; height:21px;" allowtransparency="true" frameborder="0" scrolling="no"></…

    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 549, Column 117: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …85;s=129;d=31;w=468;h=60" frameborder=0 marginheight=0 marginwidth=0 scrolling…
  • Error Line 549, Column 132: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=468;h=60" frameborder=0 marginheight=0 marginwidth=0 scrolling="no" allowTran…
  • Error Line 549, Column 146: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …meborder=0 marginheight=0 marginwidth=0 scrolling="no" allowTransparency="true…
  • Error Line 549, Column 181: there is no attribute "allowTransparency"
    …th=0 scrolling="no" allowTransparency="true" width=468 height=60></iframe></di…

    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 549, Column 194: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …h=0 scrolling="no" allowTransparency="true" width=468 height=60></iframe></div>
  • Error Line 549, Column 205: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …h=0 scrolling="no" allowTransparency="true" width=468 height=60></iframe></div>
  • Error Line 559, Column 101: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …86;s=129;d=9;w=300;h=250" frameborder=0 marginheight=0 marginwidth=0 scrolling…
  • Error Line 559, Column 116: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …300;h=250" frameborder=0 marginheight=0 marginwidth=0 scrolling="no" allowTran…
  • Error Line 559, Column 130: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …meborder=0 marginheight=0 marginwidth=0 scrolling="no" allowTransparency="true…
  • Error Line 559, Column 178: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …dth=0 scrolling="no" allowTransparency="true" width=300 height=250></iframe>   
  • Error Line 559, Column 189: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …dth=0 scrolling="no" allowTransparency="true" width=300 height=250></iframe>   
  • Warning Line 588, Column 98: cannot generate system identifier for general entity "ad_type"
    …tlvmedia.com/tags.js?id=101781_124886&ad_type=pop&banned_pop_types=28&pop_time…

    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 588, Column 98: general entity "ad_type" not defined and no default entity
    …tlvmedia.com/tags.js?id=101781_124886&ad_type=pop&banned_pop_types=28&pop_time…

    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 588, Column 105: reference not terminated by REFC delimiter
    …a.com/tags.js?id=101781_124886&ad_type=pop&banned_pop_types=28&pop_times=1&pop…

    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 588, Column 105: reference to external entity in attribute value
    …a.com/tags.js?id=101781_124886&ad_type=pop&banned_pop_types=28&pop_times=1&pop…

    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 588, Column 105: reference to entity "ad_type" for which no system identifier could be generated
    …a.com/tags.js?id=101781_124886&ad_type=pop&banned_pop_types=28&pop_times=1&pop…

    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 588, Column 97: entity was defined here
    ….tlvmedia.com/tags.js?id=101781_124886&ad_type=pop&banned_pop_types=28&pop_tim…
  • Warning Line 588, Column 110: cannot generate system identifier for general entity "banned_pop_types"
    …/tags.js?id=101781_124886&ad_type=pop&banned_pop_types=28&pop_times=1&pop_freq…

    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 588, Column 110: general entity "banned_pop_types" not defined and no default entity
    …/tags.js?id=101781_124886&ad_type=pop&banned_pop_types=28&pop_times=1&pop_freq…

    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 588, Column 126: reference not terminated by REFC delimiter
    …81_124886&ad_type=pop&banned_pop_types=28&pop_times=1&pop_frequency=3600&ad_si…

    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 588, Column 126: reference to external entity in attribute value
    …81_124886&ad_type=pop&banned_pop_types=28&pop_times=1&pop_frequency=3600&ad_si…

    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 588, Column 126: reference to entity "banned_pop_types" for which no system identifier could be generated
    …81_124886&ad_type=pop&banned_pop_types=28&pop_times=1&pop_frequency=3600&ad_si…

    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 588, Column 109: entity was defined here
    …m/tags.js?id=101781_124886&ad_type=pop&banned_pop_types=28&pop_times=1&pop_fre…
  • Warning Line 588, Column 130: cannot generate system identifier for general entity "pop_times"
    …24886&ad_type=pop&banned_pop_types=28&pop_times=1&pop_frequency=3600&ad_size=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 588, Column 130: general entity "pop_times" not defined and no default entity
    …24886&ad_type=pop&banned_pop_types=28&pop_times=1&pop_frequency=3600&ad_size=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 588, Column 139: reference not terminated by REFC delimiter
    …type=pop&banned_pop_types=28&pop_times=1&pop_frequency=3600&ad_size=0x0"></scr…

    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 588, Column 139: reference to external entity in attribute value
    …type=pop&banned_pop_types=28&pop_times=1&pop_frequency=3600&ad_size=0x0"></scr…

    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 588, Column 139: reference to entity "pop_times" for which no system identifier could be generated
    …type=pop&banned_pop_types=28&pop_times=1&pop_frequency=3600&ad_size=0x0"></scr…

    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 588, Column 129: entity was defined here
    …124886&ad_type=pop&banned_pop_types=28&pop_times=1&pop_frequency=3600&ad_size=…
  • Warning Line 588, Column 142: cannot generate system identifier for general entity "pop_frequency"
    …e=pop&banned_pop_types=28&pop_times=1&pop_frequency=3600&ad_size=0x0"></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 588, Column 142: general entity "pop_frequency" not defined and no default entity
    …e=pop&banned_pop_types=28&pop_times=1&pop_frequency=3600&ad_size=0x0"></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 588, Column 155: reference not terminated by REFC delimiter
    …e=pop&banned_pop_types=28&pop_times=1&pop_frequency=3600&ad_size=0x0"></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 588, Column 155: reference to external entity in attribute value
    …e=pop&banned_pop_types=28&pop_times=1&pop_frequency=3600&ad_size=0x0"></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 588, Column 155: reference to entity "pop_frequency" for which no system identifier could be generated
    …e=pop&banned_pop_types=28&pop_times=1&pop_frequency=3600&ad_size=0x0"></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 588, Column 141: entity was defined here
    …pe=pop&banned_pop_types=28&pop_times=1&pop_frequency=3600&ad_size=0x0"></scrip…
  • Warning Line 588, Column 161: cannot generate system identifier for general entity "ad_size"
    …e=pop&banned_pop_types=28&pop_times=1&pop_frequency=3600&ad_size=0x0"></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 588, Column 161: general entity "ad_size" not defined and no default entity
    …e=pop&banned_pop_types=28&pop_times=1&pop_frequency=3600&ad_size=0x0"></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 588, Column 168: reference not terminated by REFC delimiter
    …e=pop&banned_pop_types=28&pop_times=1&pop_frequency=3600&ad_size=0x0"></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 588, Column 168: reference to external entity in attribute value
    …e=pop&banned_pop_types=28&pop_times=1&pop_frequency=3600&ad_size=0x0"></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 588, Column 168: reference to entity "ad_size" for which no system identifier could be generated
    …e=pop&banned_pop_types=28&pop_times=1&pop_frequency=3600&ad_size=0x0"></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 588, Column 160: entity was defined here
    …e=pop&banned_pop_types=28&pop_times=1&pop_frequency=3600&ad_size=0x0"></script>
  • Error Line 590, Column 105: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …83;s=129;d=14;w=728;h=90" frameborder=0 marginheight=0 marginwidth=0 scrolling…
  • Error Line 590, Column 120: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …=728;h=90" frameborder=0 marginheight=0 marginwidth=0 scrolling="no" allowTran…
  • Error Line 590, Column 134: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …meborder=0 marginheight=0 marginwidth=0 scrolling="no" allowTransparency="true…
  • Error Line 590, Column 182: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … scrolling="no" allowTransparency="true" width=728 height=90></iframe></center>
  • Error Line 590, Column 193: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … scrolling="no" allowTransparency="true" width=728 height=90></iframe></center>
  • Warning Line 604, Column 75: cannot generate system identifier for general entity "catid"
    …  <li><a href="http://flashx.tv/support/index.php?a=add&catid=1">ABUSE</a></li>

    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 604, Column 75: general entity "catid" not defined and no default entity
    …  <li><a href="http://flashx.tv/support/index.php?a=add&catid=1">ABUSE</a></li>

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

  • Warning Line 604, Column 80: reference not terminated by REFC delimiter
    …  <li><a href="http://flashx.tv/support/index.php?a=add&catid=1">ABUSE</a></li>

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

  • Warning Line 604, Column 80: reference to external entity in attribute value
    …  <li><a href="http://flashx.tv/support/index.php?a=add&catid=1">ABUSE</a></li>

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

  • Error Line 604, Column 80: reference to entity "catid" for which no system identifier could be generated
    …  <li><a href="http://flashx.tv/support/index.php?a=add&catid=1">ABUSE</a></li>

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

  • Info Line 604, Column 74: entity was defined here
    …  <li><a href="http://flashx.tv/support/index.php?a=add&catid=1">ABUSE</a></li>

Visitor Analysis

Daily Visitor
  • 47.833 visits