Phim tâm lý và xem phim hay khác, phim HD miễn phí, xem phim hành động, phim tâm lý tình cảm, xem phim 18+, phim nhanh nhất mới nhất, phim bộ nhiều tập ...

phim16.com
  • Domain Name
    phim16.com
  • Favicon
  • Google Page Rank
    0
  • Alexa Rank
    #42847
  • Page Size
    79.2 KB
  • Ip Address
    118.139.162.222
  • Heading
    H1: 1, H2: 33, H3: 6, H4: 2, H5: 0, H6: 0
  • Images
    0 GIF, 1 JPG, 0 PNG

Website Meta Analysis

  • Title
    PHIM TÂM LÝ | XEM PHIM TÌNH CẢM | PHIM HD MIỄN PHÍ
  • Meta Keyword
    phim tam ly, xem phim tâm lý
  • Meta Description
    Phim tâm lý và xem phim hay khác, phim HD miễn phí, xem phim hành động, phim tâm lý tình cảm, xem phim 18+, phim nhanh nhất mới nhất, phim bộ nhiều tập

Technical Analysis

  • Webserver
  • Ip Address
    118.139.162.222
  • Domain Age
    1 Years, 10 Months, 27 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • content-type: text/html; charset=UTF-8
  • last-modified: Wed, 11 Sep 2013 11:40:23 GMT
  • expires: Wed, 11 Sep 2013 13:40:23 GMT
  • pragma: public
  • cache-control: max-age=7200, public, must-revalidate, proxy-revalidate
  • etag: 5de05243436b68f6d0d969f26f71c725
  • vary: , Accept-Encoding
  • x-pingback: http://phim16.com/xmlrpc.php
  • content-encoding: gzip
  • content-length: 17021
  • accept-ranges: bytes
  • date: Wed, 11 Sep 2013 14:49:46 GMT
  • connection: keep-alive
  • x-cache: HIT
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for phim16.com

DNS Analysis


DNS servers
ns2.phim16.com [208.109.255.50]
ns1.phim16.com [216.69.185.50]

DNS Records

Answer records
phim16.com A 118.139.162.222 3600s
phim16.com MX
preference: 0
exchange: smtp.secureserver.net
3600s
phim16.com MX
preference: 10
exchange: mailstore1.secureserver.net
3600s
phim16.com NS  ns1.phim16.com 3600s
phim16.com NS  ns2.phim16.com 3600s
phim16.com SOA
server: pdns01.domaincontrol.com
email: dns@jomax.net
serial: 2012102007
refresh: 28800
retry: 7200
expire: 604800
minimum ttl: 3600
3600s

Authority records

Additional records
ns2.phim16.com A 208.109.255.50 3600s
ns1.phim16.com A 216.69.185.50 3600s

IP 118.139.162.222 Analysis

  • Country Code
    SG
  • Country Code3
    SGP
  • Country Name
    Singapore
  • City
    AS
  • Continent Code
    1°36'67" North
  • Latitude
    103.8.
  • Longitude
  • % [whois.apnic.net node-7]
    % Whois data copyright terms http://www.apnic.net/db/dbcopyright.html

    inetnum: 118.139.160.0 - 118.139.191.255
    netname: GODADDY-NET-AS-AP
    descr: Godaddy.com
    descr: 8 Cross Street
    descr: #11-00 PWC Building
    country: SG
    admin-c: GNA32-AP
    tech-c: GNA32-AP
    mnt-by: APNIC-HM
    mnt-lower: MAINT-GODADDY-NET-SG
    mnt-routes: MAINT-GODADDY-NET-SG
    mnt-irt: IRT-GODADDY-NET-SG
    status: ALLOCATED PORTABLE
    remarks: -+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    remarks: This object can only be updated by APNIC hostmasters.
    remarks: To update this object, please contact APNIC
    remarks: hostmasters and include your organisation's account
    remarks: name in the subject line.
    remarks: -+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    changed: hm-changed@apnic.net 20110128
    source: APNIC

    role: GODADDYCOM - network administrator
    address: 8 Cross Street, #11-00 PWC Building
    country: SG
    phone: +011-1-480-505-8877
    e-mail: gschwimer@godaddy.com
    admin-c: GNA32-AP
    tech-c: GNA32-AP
    nic-hdl: GNA32-AP
    mnt-by: MAINT-GODADDY-NET-SG
    changed: hm-changed@apnic.net 20100226
    source: APNIC


In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 176 Errors
  • 7 Warnings
Ratio Text/Html
  • 0.6117718102608974
Message Error
  • Error Line 12, Column 119: end tag for "link" omitted, but OMITTAG NO was specified
    …im16.com/wp-content/themes/marx/static/c/m.css" type="text/css" media="screen">

    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 12, Column 2: start tag was here
    	<link rel="stylesheet" href="http://phim16.com/wp-content/themes/marx/static/c…
  • Error Line 114, Column 127: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …-12174/" title=""><div class="overlay"></div><img src="https://images2-focus-o…

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

  • Warning Line 114, Column 229: cannot generate system identifier for general entity "gadget"
    …ent.com/gadgets/proxy?container=focus&gadget=a&rewriteMime=image/*&url=http://…

    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 114, Column 229: general entity "gadget" not defined and no default entity
    …ent.com/gadgets/proxy?container=focus&gadget=a&rewriteMime=image/*&url=http://…

    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 114, Column 235: reference not terminated by REFC delimiter
    …m/gadgets/proxy?container=focus&gadget=a&rewriteMime=image/*&url=http://lh4.go…

    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.

Visitor Analysis

Daily Visitor
  • 2.450 visits