Selamat Datang pengunjung DownloadFilem.com , di web ini anda bisa Men download Film Gratis atau mencari Film Terbaru Yang Baru dirilis lainnya sesuai keinginan anda ...

downloadfilem.com
  • Domain Name
    downloadfilem.com
  • Favicon
  • Google Page Rank
    1
  • Alexa Rank
    #25974
  • Page Size
    27.5 KB
  • Ip Address
    192.157.245.201
  • Heading
    H1: 1, H2: 10, H3: 12, H4: 0, H5: 0, H6: 0
  • Images
    6 GIF, 10 JPG, 5 PNG

Website Meta Analysis

  • Title
    Download Film Gratis | Subtitle Indonesia
  • Meta Keyword
    download film gratis, download film terbaru , download filem ,subtitle indonesia, film terbaru , iron man 3
  • Meta Description
    Selamat Datang pengunjung DownloadFilem.com , di web ini anda bisa Men download Film Gratis atau mencari Film Terbaru Yang Baru dirilis lainnya sesuai keinginan anda

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    192.157.245.201
  • Domain Age
    3 Years, 3 Months, 12 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Fri, 06 Sep 2013 02:49:03 GMT
  • server: Apache
  • vary: Accept-Encoding,Cookie
  • last-modified: Fri, 06 Sep 2013 02:38:38 GMT
  • accept-ranges: bytes
  • content-length: 5699
  • cache-control: max-age=2975, public, must-revalidate, proxy-revalidate
  • expires: Fri, 06 Sep 2013 03:38:38 GMT
  • x-powered-by: W3 Total Cache/0.9.2.11
  • pragma: public
  • connection: close
  • content-type: text/html; charset=UTF-8
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
Domains By Proxy, LLC
DomainsByProxy.com
14747 N Northsight Blvd Suite 111, PMB 309
Scottsdale, Arizona 85260
United States

Registered through: NameAdmin.com
Domain Name: DOWNLOADFILEM.COM
Created on: 12-May-10
Expires on: 12-May-13
Last Updated on: 07-Mar-12

Administrative Contact:
Private, Registration email
Domains By Proxy, LLC
DomainsByProxy.com
14747 N Northsight Blvd Suite 111, PMB 309
Scottsdale, Arizona 85260
United States
(480) 624-2599 Fax -- (480) 624-2598

Technical Contact:
Private, Registration email
Domains By Proxy, LLC
DomainsByProxy.com
14747 N Northsight Blvd Suite 111, PMB 309
Scottsdale, Arizona 85260
United States
(480) 624-2599 Fax -- (480) 624-2598

Domain servers in listed order:
NS1.DOWNLOADFILEM.COM
NS2.DOWNLOADFILEM.COM

DNS Analysis


DNS servers
ns1.downloadfilem.com [192.157.245.201]
ns2.downloadfilem.com [192.157.245.202]


DNS Records

Answer records
downloadfilem.com MX
preference: 0
exchange: downloadfilem.com
14400s
downloadfilem.com SOA
server: ns1.downloadfilem.com
email: [email protected]
serial: 2013031303
refresh: 86400
retry: 7200
expire: 3600000
minimum ttl: 86400
86400s
downloadfilem.com NS  ns1.downloadfilem.com 86400s
downloadfilem.com NS  ns2.downloadfilem.com 86400s
downloadfilem.com A 192.157.245.201 14400s

Authority records

Additional records
downloadfilem.com A 192.157.245.201 14400s
ns1.downloadfilem.com A 192.157.245.201 14400s
ns2.downloadfilem.com A 192.157.245.202 14400s

IP 192.157.245.201 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 38 Errors
  • 11 Warnings
Ratio Text/Html
  • 0.7358416826547289
Message Error
  • Error Line 9, Column 16: there is no attribute "property"
    <meta property="fb:admins" content=""/>

    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 102, Column 24: end tag for "br" omitted, but OMITTAG NO was specified
    <div id="wrapper">	<br><center>

    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 102, Column 20: start tag was here
    <div id="wrapper">	<br><center>
  • Error Line 115, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><marquee><span style="color: #ff0000;"><strong> SEMUA FILM YANG ADA DI AKUN…

    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 115, Column 1: start tag was here
    <br><marquee><span style="color: #ff0000;"><strong> SEMUA FILM YANG ADA DI AKUN…
  • Error Line 115, Column 13: element "marquee" undefined
    <br><marquee><span style="color: #ff0000;"><strong> SEMUA FILM YANG ADA DI AKUN…

    You have used the element named above in your document, but the document type you are using does not define an element of that name. 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 "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 250, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

    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 250, Column 1: start tag was here
    <br>
  • Error Line 260, Column 7: invalid comment declaration: found name start character outside comment but inside comment declaration
    <!----TLVMedia----http://www.downloadfilem.com - http://www.downloadfilem.com (…
  • Info Line 260, Column 1: comment declaration started here
    <!----TLVMedia----http://www.downloadfilem.com - http://www.downloadfilem.com (…
  • Warning Line 261, Column 86: cannot generate system identifier for general entity "ad_type"
    …tlvmedia.com/tags.js?id=101989_125218&ad_type=banner&ad_size=300x250"></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 261, Column 86: general entity "ad_type" not defined and no default entity
    …tlvmedia.com/tags.js?id=101989_125218&ad_type=banner&ad_size=300x250"></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 261, Column 93: reference not terminated by REFC delimiter
    …tlvmedia.com/tags.js?id=101989_125218&ad_type=banner&ad_size=300x250"></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 261, Column 93: reference to external entity in attribute value
    …tlvmedia.com/tags.js?id=101989_125218&ad_type=banner&ad_size=300x250"></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 261, Column 93: reference to entity "ad_type" for which no system identifier could be generated
    …tlvmedia.com/tags.js?id=101989_125218&ad_type=banner&ad_size=300x250"></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 261, Column 85: entity was defined here
    ….tlvmedia.com/tags.js?id=101989_125218&ad_type=banner&ad_size=300x250"></scrip…
  • Warning Line 261, Column 101: cannot generate system identifier for general entity "ad_size"
    …tlvmedia.com/tags.js?id=101989_125218&ad_type=banner&ad_size=300x250"></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 261, Column 101: general entity "ad_size" not defined and no default entity
    …tlvmedia.com/tags.js?id=101989_125218&ad_type=banner&ad_size=300x250"></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 261, Column 108: reference not terminated by REFC delimiter
    …tlvmedia.com/tags.js?id=101989_125218&ad_type=banner&ad_size=300x250"></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 261, Column 108: reference to external entity in attribute value
    …tlvmedia.com/tags.js?id=101989_125218&ad_type=banner&ad_size=300x250"></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 261, Column 108: reference to entity "ad_size" for which no system identifier could be generated
    …tlvmedia.com/tags.js?id=101989_125218&ad_type=banner&ad_size=300x250"></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 261, Column 100: entity was defined here
    …tlvmedia.com/tags.js?id=101989_125218&ad_type=banner&ad_size=300x250"></script>
  • Error Line 262, Column 7: invalid comment declaration: found name start character outside comment but inside comment declaration
    <!----TLVMedia------------------------------------------->
  • Info Line 262, Column 1: comment declaration started here
    <!----TLVMedia------------------------------------------->
  • Error Line 268, Column 20: end tag for element "br" which is not open
    </div></center></br> </div>

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

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

  • Error Line 277, Column 59: there is no attribute "role"
    …2>Pencarian Judul Film</h2><form role="search" method="get" id="searchform" ac…

    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 288, Column 8: document type does not allow element "center" here; assuming missing "li" start-tag
    <center>
  • Error Line 290, Column 227: required attribute "alt" not specified
    …1/The-Twilight-Saga-Breaking-Dawn-Part-2-2012.jpg" width="90" height="125"></a>

    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 290, Column 231: end tag for "img" omitted, but OMITTAG NO was specified
    …1/The-Twilight-Saga-Breaking-Dawn-Part-2-2012.jpg" width="90" height="125"></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 290, Column 89: start tag was here
    …light-saga-breaking-dawn-part-2.html"><img src="http://www.downloadfilem.com/w…
  • Error Line 293, Column 215: required attribute "alt" not specified
    …2012/06/Madagascar-3-Europes-Most-Wanted-2012.jpg" width="90" height="125"></a>

    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 293, Column 219: end tag for "img" omitted, but OMITTAG NO was specified
    …2012/06/Madagascar-3-Europes-Most-Wanted-2012.jpg" width="90" height="125"></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 293, Column 83: start tag was here
    …adagascar-3-europes-most-wanted.html"><img src="http://www.downloadfilem.com/w…
  • Error Line 296, Column 161: required attribute "alt" not specified
    …lem.com/wp-content/uploads/2012/06/Brave-2012.jpg" width="90" height="125"></a>

    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 296, Column 165: end tag for "img" omitted, but OMITTAG NO was specified
    …lem.com/wp-content/uploads/2012/06/Brave-2012.jpg" width="90" height="125"></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 296, Column 56: start tag was here
    …ww.downloadfilem.com/film-brave.html"><img src="http://www.downloadfilem.com/w…
  • Error Line 299, Column 211: required attribute "alt" not specified
    …s/2012/06/Abraham-Lincoln-Vampire-Hunter-2012.jpg" width="90" height="125"></a>

    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 299, Column 215: end tag for "img" omitted, but OMITTAG NO was specified
    …s/2012/06/Abraham-Lincoln-Vampire-Hunter-2012.jpg" width="90" height="125"></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 299, Column 81: start tag was here
    …-abraham-lincoln-vampire-hunter.html"><img src="http://www.downloadfilem.com/w…
  • Error Line 302, Column 183: required attribute "alt" not specified
    …content/uploads/2012/05/Men-in-Black-III-2012.jpg" width="90" height="125"></a>

    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 302, Column 187: end tag for "img" omitted, but OMITTAG NO was specified
    …content/uploads/2012/05/Men-in-Black-III-2012.jpg" width="90" height="125"></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 302, Column 67: start tag was here
    …filem.com/film-men-in-black-iii.html"><img src="http://www.downloadfilem.com/w…
  • Error Line 305, Column 171: required attribute "alt" not specified
    …om/wp-content/uploads/2012/06/Prometheus-2012.jpg" width="90" height="125"></a>

    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 305, Column 175: end tag for "img" omitted, but OMITTAG NO was specified
    …om/wp-content/uploads/2012/06/Prometheus-2012.jpg" width="90" height="125"></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 305, Column 61: start tag was here
    …wnloadfilem.com/film-prometheus.html"><img src="http://www.downloadfilem.com/w…
  • Error Line 313, Column 14: end tag for "li" omitted, but OMITTAG NO was specified
    </center></ul>

    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 288, Column 1: start tag was here
    <center>
  • Error Line 316, Column 94: document type does not allow element "center" here; assuming missing "li" start-tag
    …ass="box"><h2>Iklan</h2>			<div class="textwidget"><ul class="popular"><center>
  • Error Line 319, Column 167: required attribute "alt" not specified
    …nloadfilem.com/wp-content/uploads/2013/12/banner-iklan-triplewings3.gif" /></a>

    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 322, Column 128: required attribute "alt" not specified
    …"http://www.downloadfilem.com/wp-content/uploads/2012/12/bannermini.gif" /></a>

    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 325, Column 133: required attribute "alt" not specified
    …ww.downloadfilem.com/wp-content/uploads/2012/12/JAMTOKYOFLASH-125PX.gif" /></a>

    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 328, Column 138: required attribute "alt" not specified
    …://www.downloadfilem.com/wp-content/uploads/2013/12/IKLAN-125PX-GIF.gif" /></a>

    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 331, Column 113: required attribute "alt" not specified
    …"http://www.downloadfilem.com/wp-content/uploads/2012/12/Banner-168.gif" /></a>

    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 334, Column 145: required attribute "alt" not specified
    …oadfilem.com/wp-content/uploads/2011/12/pasang-iklan-disini-125x125.gif" /></a>

    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 338, Column 5: end tag for "center" omitted, but OMITTAG NO was specified
    </ul></center>

    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 316, Column 87: start tag was here
    …ass="box"><h2>Iklan</h2>			<div class="textwidget"><ul class="popular"><center>
  • Error Line 338, Column 5: end tag for "li" omitted, but OMITTAG NO was specified
    </ul></center>

    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 316, Column 87: start tag was here
    …ass="box"><h2>Iklan</h2>			<div class="textwidget"><ul class="popular"><center>
  • Error Line 338, Column 14: end tag for element "center" which is not open
    </ul></center>

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

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

  • Error Line 340, Column 79: end tag for "br" omitted, but OMITTAG NO was specified
    …ok</h2>			<div class="textwidget"><br><center><iframe src="http://www.facebook…

    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 340, Column 75: start tag was here
    …cebook</h2>			<div class="textwidget"><br><center><iframe src="http://www.face…
  • Error Line 340, Column 359: there is no attribute "allowTransparency"
    …dth:300px; height:287px;" allowTransparency="true"></iframe></center><br></div>

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

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

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

  • Error Line 340, Column 393: end tag for "br" omitted, but OMITTAG NO was specified
    …dth:300px; height:287px;" allowTransparency="true"></iframe></center><br></div>

    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 340, Column 384: start tag was here
    …dth:300px; height:287px;" allowTransparency="true"></iframe></center><br></div>
  • Error Line 349, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br>

    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 349, Column 1: start tag was here
    <br><br>
  • Error Line 349, Column 9: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br>

    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 349, Column 5: start tag was here
    <br><br>
  • Error Line 351, Column 204: required attribute "alt" not specified
    ….co.id/wp-content/uploads/2012/03/fix-logo.png" width="125" height="125" /></a>

    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 444, Column 314: end tag for "br" omitted, but OMITTAG NO was specified
    …"http://free-download-filme.info/site-map/" title="">filme</a> &raquo; </p><br>

    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 444, Column 310: start tag was here
    …"http://free-download-filme.info/site-map/" title="">filme</a> &raquo; </p><br>
  • Warning Line 464, Column 112: character "&" is the first character of a delimiter but occurred as data
    …p://sstatic1.histats.com/0.gif?1122526&101" alt="cool hit counter" border="0">…

    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 155: end tag for "img" omitted, but OMITTAG NO was specified
    …istats.com/0.gif?1122526&101" alt="cool hit counter" border="0"></a></noscript>

    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 464, Column 60: start tag was here
    …tp://www.histats.com" target="_blank"><img  src="http://sstatic1.histats.com/0…

Visitor Analysis

Daily Visitor
  • 4.083 visits