jetfilmizle.com

Jetfilmizle.Com Jet hızında online film izleme sitesi... ...

Display Widget for this domain on your website. Click Here
This data was last updated from 05-08-2013 02:50:09  (update).

Overview Info

  • Domain Name
    jetfilmizle.com
  • Favicon
  • Alexa Rank
    #10132
  • Google Page Rank
    PR 4
  • Ip Address
    31.210.156.12
  • Page Size
    46.5 KB
  • Images
    1 GIF, 46 JPG, 76 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 4 0 0 1 0

Website Meta Analysis



  • Title
    JetFilmizle.Com, Film izle, Jet Film izle, Full izle, Türkçe Dublaj izle, Filmini izle, Hd Film izle, Full Hd izle
  • Meta Keyword
    JetFilmizle.Com, Film izle, Jet Film izle, Full izle, Türkçe Dublaj izle, Filmini izle, Hd Film izle, Full Hd izle
  • Meta Description
    Jetfilmizle.Com Jet hızında online film izleme sitesi...

Technical Analysis



  • Webserver
    LiteSpeed
  • Ip Address
    31.210.156.12
  • Domain Age
    1 Years, 11 Months, 29 days.
  • Javascript Library
    jquery, yui
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • content-encoding: gzip
  • vary: Accept-Encoding
  • date: Mon, 05 Aug 2013 02:50:04 GMT
  • server: LiteSpeed
  • connection: Keep-Alive
  • x-powered-by: PHP/5.2.17
  • content-type: text/html
  • content-length: 8022
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
sadik karabulut

Domain Name: JETFILMIZLE.COM

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

For complete domain details go to:
http://who.godaddy.com/whoischeck.aspx?domain=JETFILMIZLE.COM

DNS Analysis


DNS servers
ns1.birdns.com [89.107.227.203]
ns2.birdns.com [89.107.227.206]


DNS Records

Answer records
jetfilmizle.com SOA
server: ns1.birdns.com
email: nobody@invalid
serial: 2013032406
refresh: 10800
retry: 3600
expire: 777600
minimum ttl: 3600
10800s
jetfilmizle.com A 31.210.156.12 10800s
jetfilmizle.com A 31.210.156.13 10800s
jetfilmizle.com A 31.210.156.10 10800s
jetfilmizle.com A 31.210.156.135 10800s
jetfilmizle.com A 37.247.96.4 10800s
jetfilmizle.com A 31.210.156.14 10800s
jetfilmizle.com A 31.210.156.126 10800s
jetfilmizle.com A 31.210.156.11 10800s
jetfilmizle.com NS  ns1.birdns.com 10800s
jetfilmizle.com MX
preference: 10
exchange: mail.jetfilmizle.com
10800s

Authority records

Additional records

IP 31.210.156.12 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 43 Errors
  • 5 Warnings
Ratio Text/Html
  • 0.8490201432502258
Message Error
  • Error Line 73, Column 74: there is no attribute "target"
    …ec.com/?referer=[jetfilmizle.com]" target="_blank" rel="nofollow external"><img

    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 74, Column 106: there is no attribute "border"
    …photos-ak-prn1/150752_554538787909217_442403200_n.jpg" alt="" border="0" /></a>

    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 133, Column 68: document type does not allow element "form" here; assuming missing "li" start-tag
    <form method="get" id="searchform" action="http://jetfilmizle.com/">
  • Error Line 134, Column 70: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …e="s" id="s" size="10" class="arama" /><input type="submit" id="searchsubmit" …

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 134, Column 149: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …t type="submit" id="searchsubmit" value="BUL" alt="ara bul" class="bul" />	    

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 136, Column 5: end tag for "li" omitted, but OMITTAG NO was specified
    </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 133, Column 1: start tag was here
    <form method="get" id="searchform" action="http://jetfilmizle.com/">
  • Error Line 140, Column 88: document type does not allow element "a" here; assuming missing "li" start-tag
    …edik-yolculuk-turkce-dublaj-izle.html"> <img src="http://resim3.jetfilmizle.co…
  • Error Line 141, Column 148: required attribute "alt" not specified
    …65228896_744868711_n.jpg" width="135px" height="203px" class="guncover" /> </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 142, Column 5: end tag for "li" omitted, but OMITTAG NO was specified
    </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 140, Column 4: start tag was here
       <a href="http://jetfilmizle.com/hobbit-beklenmedik-yolculuk-turkce-dublaj-iz…
  • Error Line 146, Column 13: there is no attribute "src"
    <iframe src="http://run.admost.com/adx/frame.ashx?k=14063&preredir={amClickThru…

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

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

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

  • Warning Line 146, Column 59: cannot generate system identifier for general entity "preredir"
    …run.admost.com/adx/frame.ashx?k=14063&preredir={amClickThru}" width="160"heigh…

    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 146, Column 59: general entity "preredir" not defined and no default entity
    …run.admost.com/adx/frame.ashx?k=14063&preredir={amClickThru}" width="160"heigh…

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

  • Warning Line 146, Column 67: reference not terminated by REFC delimiter
    …st.com/adx/frame.ashx?k=14063&preredir={amClickThru}" width="160"height="600" …

    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 146, Column 67: reference to external entity in attribute value
    …st.com/adx/frame.ashx?k=14063&preredir={amClickThru}" width="160"height="600" …

    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 146, Column 67: reference to entity "preredir" for which no system identifier could be generated
    …st.com/adx/frame.ashx?k=14063&preredir={amClickThru}" width="160"height="600" …

    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 146, Column 58: entity was defined here
    …/run.admost.com/adx/frame.ashx?k=14063&preredir={amClickThru}" width="160"heig…
  • Error Line 146, Column 89: there is no attribute "width"
    …k=14063&preredir={amClickThru}" width="160"height="600" frameborder="0" margin…

    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 146, Column 101: there is no attribute "height"
    …edir={amClickThru}" width="160"height="600" frameborder="0" marginwidth="0" ma…

    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 146, Column 119: there is no attribute "frameborder"
    …" width="160"height="600" frameborder="0" marginwidth="0" marginheight="0" scr…

    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 146, Column 135: there is no attribute "marginwidth"
    …ght="600" frameborder="0" marginwidth="0" marginheight="0" scrolling="no"></if…

    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 146, Column 152: there is no attribute "marginheight"
    …"600" frameborder="0" marginwidth="0" marginheight="0" scrolling="no"></iframe>

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

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

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

  • Error Line 146, Column 166: there is no attribute "scrolling"
    …"600" frameborder="0" marginwidth="0" marginheight="0" scrolling="no"></iframe>

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

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

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

  • Error Line 146, Column 170: element "iframe" undefined
    …"600" frameborder="0" marginwidth="0" marginheight="0" scrolling="no"></iframe>

    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 147, Column 5: end tag for "ul" which is not finished
    </ul>

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Error Line 404, Column 8: element "center" undefined
    <center>Copyright © 2010 JetFilmizle.Com<br />

    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 436, Column 52: document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …href="http://www.sayyac.com/" title=""><img src="http://srv.sayyac.net/sa.gif?…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 442, Column 7: end tag for "div" omitted, but OMITTAG NO was specified
    </body>

    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 81, Column 1: start tag was here
    <div id="zemin">
  • Error Line 442, Column 7: end tag for "div" omitted, but OMITTAG NO was specified
    </body>

    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 77, Column 1: start tag was here
    <div id="wrapper">

Visitor Analysis

Daily Visitor
  • 9.217 visits

In Page Analysis