maxphim.com

MaxPhim.com Xem Phim XXX, Phim HD Sắc NÉT Nhất, Phim Sex Online (Cực Hay). ...

This data was last updated from 22-08-2013 08:48:02  (update).

Overview Info



  • Domain Name
    maxphim.com
  • Favicon
  • Alexa Rank
    #0
  • Google Page Rank
    0
  • Ip Address
    123.30.187.214
  • Page Size
    5.1 KB
  • Images
    0 GIF, 0 JPG, 0 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 0 0 0 0 0

Website Meta Analysis



  • Title
    Xem Phim Sex, Phim Cấp 3, Phim HD Hay 18+ 2013
  • Meta Keyword
    Phim XXX,Phim Sex,Phim HD,Phim Bộ,Phim Lẻ
  • Meta Description
    MaxPhim.com Xem Phim XXX, Phim HD Sắc NÉT Nhất, Phim Sex Online (Cực Hay).

Technical Analysis



  • Webserver
  • Ip Address
    123.30.187.214
  • Domain Age
    2 Years, 5 Months, 29 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Thu, 22 Aug 2013 20:50:18 GMT
  • last-modified: Fri, 05 Jul 2013 10:47:00 GMT
  • etag: "28634-1375-6a165100"
  • accept-ranges: bytes
  • vary: Accept-Encoding,User-Agent
  • content-encoding: gzip
  • content-length: 2041
  • content-type: text/html; charset=UTF-8
  • connection: close
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for maxphim.com

DNS Analysis


DNS servers
mdns1.nhanhoa.com [50.23.136.229]
mdns2.nhanhoa.com [50.23.75.96]
mdns3.nhanhoa.com [67.15.47.188]
mdns4.nhanhoa.com [184.173.150.57]


DNS Records

Answer records
maxphim.com SOA
server: nhanhoa.mercury.orderbox-dns.com
email: [email protected]
serial: 2012082803
refresh: 7200
retry: 7200
expire: 172800
minimum ttl: 7200
14400s
maxphim.com NS  nhanhoa.venus.orderbox-dns.com 38400s
maxphim.com NS  nhanhoa.mars.orderbox-dns.com 38400s
maxphim.com NS  nhanhoa.mercury.orderbox-dns.com 38400s
maxphim.com A 123.30.187.214 28800s
maxphim.com MX
preference: 10
exchange: mail.maxphim.com
28800s
maxphim.com NS  nhanhoa.earth.orderbox-dns.com 38400s

Authority records

Additional records
mail.maxphim.com A 210.245.85.76 28800s

IP 123.30.187.214 Analysis

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

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 14 Errors
  • 5 Warnings
Ratio Text/Html
  • 0.7614696363982486
Message Error
  • Error Line 9, Column 16: there is no attribute "property"
    <meta property="og:title" content="Xem Phim Sex, Phim Cấp 3, Phim HD Hay 18+ 20…

    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 26, Column 45: document type does not allow element "td" here; assuming missing "tr" start-tag
    <td height="20px" colspan="1" align="center">
  • Error Line 33, Column 13: end tag for "tr" omitted, but OMITTAG NO was specified
    </td></table>

    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 26, Column 1: start tag was here
    <td height="20px" colspan="1" align="center">
  • Error Line 34, Column 18: there is no attribute "language"
    <SCRIPT language="Javascript">

    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 34, Column 30: element "SCRIPT" undefined
    <SCRIPT language="Javascript">

    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 37, Column 23: an attribute specification must start with a name or name token
    document.writeln("<SCR"+"IPT language='Javascript' src='//server.cpmstar.com/vi…

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 37, Column 23: element "SCR" undefined
    document.writeln("<SCR"+"IPT language='Javascript' src='//server.cpmstar.com/vi…

    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).
  • Warning Line 37, Column 111: cannot generate system identifier for general entity "script"
    ….com/view.aspx?poolid="+cpmstar_pid+"&script=1&rnd="+cpmstar_rnd+"'></SCR"+"IP…

    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 111: general entity "script" not defined and no default entity
    ….com/view.aspx?poolid="+cpmstar_pid+"&script=1&rnd="+cpmstar_rnd+"'></SCR"+"IP…

    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 117: reference not terminated by REFC delimiter
    …/view.aspx?poolid="+cpmstar_pid+"&script=1&rnd="+cpmstar_rnd+"'></SCR"+"IPT>");

    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 117: reference to entity "script" for which no system identifier could be generated
    …/view.aspx?poolid="+cpmstar_pid+"&script=1&rnd="+cpmstar_rnd+"'></SCR"+"IPT>");

    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 110: entity was defined here
    …r.com/view.aspx?poolid="+cpmstar_pid+"&script=1&rnd="+cpmstar_rnd+"'></SCR"+"I…
  • Warning Line 37, Column 120: cannot generate system identifier for general entity "rnd"
    …/view.aspx?poolid="+cpmstar_pid+"&script=1&rnd="+cpmstar_rnd+"'></SCR"+"IPT>");

    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 120: general entity "rnd" not defined and no default entity
    …/view.aspx?poolid="+cpmstar_pid+"&script=1&rnd="+cpmstar_rnd+"'></SCR"+"IPT>");

    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 123: reference not terminated by REFC delimiter
    …/view.aspx?poolid="+cpmstar_pid+"&script=1&rnd="+cpmstar_rnd+"'></SCR"+"IPT>");

    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 123: reference to entity "rnd" for which no system identifier could be generated
    …/view.aspx?poolid="+cpmstar_pid+"&script=1&rnd="+cpmstar_rnd+"'></SCR"+"IPT>");

    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 119: entity was defined here
    …/view.aspx?poolid="+cpmstar_pid+"&script=1&rnd="+cpmstar_rnd+"'></SCR"+"IPT>");
  • Error Line 37, Column 146: delimiter """ invalid: only S separators and TAGC allowed here
    …/view.aspx?poolid="+cpmstar_pid+"&script=1&rnd="+cpmstar_rnd+"'></SCR"+"IPT>");
  • Error Line 39, Column 100: there is no attribute "allowfullscreen"
    …BWtY" height="400" width="720" allowfullscreen="" frameborder="0"></iframe></p>

    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 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>.

Visitor Analysis

Daily Visitor
  • 13 visits

In Page Analysis