- ...

mycinemas.net
  • Domain Name
    mycinemas.net
  • Favicon
  • Google Page Rank
    1
  • Alexa Rank
    #39874
  • Page Size
    8.4 KB
  • Ip Address
    188.165.238.111
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    11 GIF, 0 JPG, 0 PNG

Website Meta Analysis

  • Title
    Latest Mobile Movies | MyCinemas.net | Free Download Latest Bollywood Mobile Movies, Dubbed Movies, Hollywood Movies, Tamil Movies, Animation Movies, Malayalam Movies, Indian TV Shows, 3gp Mobile Movies, mp4 Mobile Movies !!
  • Meta Keyword
  • Meta Description
    -

Technical Analysis

  • Webserver
    Apache/2.0.64 (Unix) mod_ssl/2.0.64 OpenSSL/0.9.8e-fips-rhel5 mod_bwlimited/1.4
  • Ip Address
    188.165.238.111
  • Domain Age
    2 Years, 2 Months, 0 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from mycinemas.net.

HTML Analysis

  • date: Sat, 05 Oct 2013 10:39:49 GMT
  • server: Apache/2.0.64 (Unix) mod_ssl/2.0.64 OpenSSL/0.9.8e-fips-rhel5 mod_bwlimited/1.4
  • x-powered-by: PHP/5.2.9
  • x-frame-options: DENY
  • connection: close
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Name: mycinemas.net
Registrar: Name.com LLC

Expiration Date: 2013-07-18 06:16:18
Creation Date: 2011-07-18 06:16:18

Name Servers:
dns1.mycinemas.net
dns2.mycinemas.net

REGISTRANT CONTACT INFO
Whois Privacy Protection Service, Inc.
Whois Agent
PMB 368, 14150 NE 20th St - F1
Bellevue
WA
98007
US
Phone: +1.4252740657
Fax: +1.4259744730
Email Address: email

ADMINISTRATIVE CONTACT INFO
Whois Privacy Protection Service, Inc.
Whois Agent
PMB 368, 14150 NE 20th St - F1
Bellevue
WA
98007
US
Phone: +1.4252740657
Fax: +1.4259744730
Email Address: email

TECHNICAL CONTACT INFO
Whois Privacy Protection Service, Inc.
Whois Agent
PMB 368, 14150 NE 20th St - F1
Bellevue
WA
98007
US
Phone: +1.4252740657
Fax: +1.4259744730
Email Address: email

BILLING CONTACT INFO
Whois Privacy Protection Service, Inc.
Whois Agent
PMB 368, 14150 NE 20th St - F1
Bellevue
WA
98007
US
Phone: +1.4252740657
Fax: +1.4259744730
Email Address: email

DNS Analysis


DNS servers
dns1.mycinemas.net [188.165.238.111]
dns2.mycinemas.net [188.165.238.111]


DNS Records

Answer records
mycinemas.net MX
preference: 10
exchange: aspmx3.googlemail.com
14400s
mycinemas.net MX
preference: 1
exchange: aspmx.l.google.com
14400s
mycinemas.net MX
preference: 5
exchange: alt1.aspmx.l.google.com
14400s
mycinemas.net MX
preference: 5
exchange: alt2.aspmx.l.google.com
14400s
mycinemas.net MX
preference: 10
exchange: aspmx2.googlemail.com
14400s
mycinemas.net SOA
server: dns1.mycinemas.net
email: classicchins@gmail.com
serial: 2012073009
refresh: 86400
retry: 7200
expire: 3600000
minimum ttl: 86400
86400s
mycinemas.net NS  dns1.mycinemas.net 86400s
mycinemas.net NS  dns2.mycinemas.net 86400s
mycinemas.net A 188.165.238.111 14400s

Authority records

Additional records
dns1.mycinemas.net A 188.165.238.111 14400s
dns2.mycinemas.net A 188.165.238.111 14400s

IP 188.165.238.111 Analysis

  • Country Code
    FR
  • Country Code3
    FRA
  • Country Name
    France
  • City
    EU
  • Continent Code
    46° North
  • Latitude
    2.
  • Longitude
  • No whois ip data for 188.165.238.111

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 33 Errors
  • 1 Warnings
Ratio Text/Html
  • 0.6658172130198077
Message Error
  • Error Line 7, Column 16: there is no attribute "property"
    <meta property="og:title" 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 33, Column 8: required attribute "type" not specified
    <script>(function(d, s, id) {

    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 37, Column 57: cannot generate system identifier for general entity "appId"
      js.src = "//connect.facebook.net/en_US/all.js#xfbml=1&appId=138329146265213";

    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 37, Column 57: general entity "appId" not defined and no default entity
      js.src = "//connect.facebook.net/en_US/all.js#xfbml=1&appId=138329146265213";

    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 37, Column 62: reference not terminated by REFC delimiter
      js.src = "//connect.facebook.net/en_US/all.js#xfbml=1&appId=138329146265213";

    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 37, Column 62: reference to entity "appId" for which no system identifier could be generated
      js.src = "//connect.facebook.net/en_US/all.js#xfbml=1&appId=138329146265213";

    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 37, Column 56: entity was defined here
      js.src = "//connect.facebook.net/en_US/all.js#xfbml=1&appId=138329146265213";
  • Error Line 41, Column 32: there is no attribute "data-href"
    <div class="fb-like" data-href="https://www.facebook.com/MyCinemas" data-send="…

    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 41, Column 79: there is no attribute "data-send"
    …www.facebook.com/MyCinemas" data-send="true" data-width="450" data-show-faces=…

    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 41, Column 97: there is no attribute "data-width"
    …yCinemas" data-send="true" data-width="450" data-show-faces="false" data-font=…

    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 41, Column 119: there is no attribute "data-show-faces"
    …"true" data-width="450" data-show-faces="false" data-font="trebuchet ms"></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 41, Column 137: there is no attribute "data-font"
    …"true" data-width="450" data-show-faces="false" data-font="trebuchet ms"></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 56, Column 61: end tag for "center" omitted, but OMITTAG NO was specified
    <div class="cs violet"><center>Movie Categories<center></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 56, Column 48: start tag was here
    <div class="cs violet"><center>Movie Categories<center></div>
  • Error Line 56, Column 61: end tag for "center" omitted, but OMITTAG NO was specified
    <div class="cs violet"><center>Movie Categories<center></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 56, Column 24: start tag was here
    <div class="cs violet"><center>Movie Categories<center></div>
  • Error Line 101, Column 63: required attribute "alt" not specified
    <img src="http://c.wen.ru/1925425.wbmp?" height="0" width="0"/></body>

    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 101, Column 70: end tag for "div" omitted, but OMITTAG NO was specified
    <img src="http://c.wen.ru/1925425.wbmp?" height="0" width="0"/></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 93, Column 1: start tag was here
    <div class="left">

Visitor Analysis

Daily Visitor
  • 5.133 visits