phim5.net

Xem Phim Download Phim, Xem phim online & download phim tai website phim5.net, full cac phim bo nhieu tap, phim dien anh Viet Nam, quoc te ... ...

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

Overview Info

  • Domain Name
    phim5.net
  • Favicon
  • Alexa Rank
    #165106
  • Google Page Rank
    PR 2
  • Ip Address
    123.30.128.92
  • Page Size
    88.6 KB
  • Images
    3 GIF, 42 JPG, 1 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 14 101 0 0 0

Website Meta Analysis



  • Title
    Xem Phim Online | Xem Phim Nhanh | Xem Phim Truc Tuyen | Phim Hot Nhat
  • Meta Keyword
    Xem Phim Download Phim, Xem Phim Nhanh,xem Phim Hot, Phim Online, Phim Truc Tuyen, Phim Bo, Phim Le, Xem Phim Online, Download Phim, Kiem Hiep, Phim Viet, Coi Phim Online, Coi Phim Truc Tuyen
  • Meta Description
    Xem Phim Download Phim, Xem phim online & download phim tai website phim5.net, full cac phim bo nhieu tap, phim dien anh Viet Nam, quoc te ...

Technical Analysis



  • Webserver
    Apache/2.2.23
  • Ip Address
    123.30.128.92
  • Domain Age
    2 Years, 5 Months, 17 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Sun, 04 Aug 2013 05:08:38 GMT
  • server: Apache/2.2.23
  • x-powered-by: PHP/5.3.19
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • content-encoding: gzip
  • vary: Accept-Encoding,User-Agent
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for phim5.net

DNS Analysis


DNS servers
ns67.domaincontrol.com [216.69.185.44]
ns68.domaincontrol.com [208.109.255.44]

DNS Records

Answer records
phim5.net A 123.30.128.92 3600s
phim5.net NS  ns67.domaincontrol.com 3600s
phim5.net NS  ns68.domaincontrol.com 3600s
phim5.net SOA
server: ns67.domaincontrol.com
email: dns@jomax.net
serial: 2012112102
refresh: 28800
retry: 7200
expire: 604800
minimum ttl: 3600
3600s

Authority records

Additional records

IP 123.30.128.92 Analysis

  • Country Code
    VN
  • Country Code3
    VNM
  • Country Name
    Vietnam
  • City
    Hanoi
  • Continent Code
    AS
  • Latitude
    21.0333
  • Longitude
    105.85
  • % [whois.apnic.net node-4]
    % Whois data copyright terms http://www.apnic.net/db/dbcopyright.html

    inetnum: 123.30.0.0 - 123.31.255.255
    netname: VDC-NET
    country: vn
    descr: VietNam Data Communication Company (VDC)
    admin-c: VIG1-AP
    tech-c: VIG1-AP
    status: ALLOCATED NON-PORTABLE
    changed: hm-changed@vnnic.net.vn 20090325
    mnt-by: MAINT-VN-VNPT
    source: APNIC

    route: 123.30.128.0/18
    descr: VietNam Post and Telecom Corporation (VNPT)
    descr: VNPT-AS-AP
    country: VN
    origin: AS7643
    remarks: mailto: noc@vnn.vn
    notify: hm-changed@vnnic.net.vn
    mnt-by: MAINT-VN-VNPT
    changed: hm-changed@vnnic.net.vn 20100121
    source: APNIC

    role: VDC IPADMIN GROUP
    address: Internet Building, Block II, Thang Long Inter Village
    address: Nguyen Phong Sac str, Cau Giay Dist, Ha Noi
    country: VN
    phone: +84-912-800008
    fax-no: +84-4-9430427
    e-mail: hathm@vdc.com.vn
    remarks: send spam reports to abuse@vdc.com.vn
    remarks: and abuse reports to abuse@vnn.vn
    admin-c: THMH1-AP
    tech-c: THMH1-AP
    nic-hdl: VIG1-AP
    notify: hm-changed@vnnic.net.vn
    mnt-by: MAINT-VN-VNPT
    changed: hm-changed@vnnic.net.vn 20090325
    source: APNIC
    changed: hm-changed@apnic.net 20111114


Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 62 Errors
  • 2 Warnings
Ratio Text/Html
  • 0.7223984841474431
Message Error
  • Error Line 22, Column 16: there is no attribute "property"
    <meta property="fb:app_id" content="114313928681053"/>

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

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

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

    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 68, 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=114313928681053";

    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 68, Column 56: entity was defined here
      js.src = "//connect.facebook.net/en_US/all.js#xfbml=1&appId=114313928681053";
  • Error Line 196, Column 95: end tag for "input" omitted, but OMITTAG NO was specified
    …s="text"><input name="keyword" class="default" type="text" id="keyword"></span>

    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 196, Column 26: start tag was here
    						<span class="text"><input name="keyword" class="default" type="text" id="…
  • Error Line 1155, Column 193: required attribute "alt" not specified
    …mg src="http://mail.opi.yahoo.com/online?u=ntuanhnd&amp;m=g&amp;t=0"></a><br />

    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 1155, Column 197: end tag for "img" omitted, but OMITTAG NO was specified
    …mg src="http://mail.opi.yahoo.com/online?u=ntuanhnd&amp;m=g&amp;t=0"></a><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 1155, Column 123: start tag was here
    …"_blank" href="ymsgr:sendIM?ntuanhnd"><img src="http://mail.opi.yahoo.com/onli…
  • Error Line 1157, Column 31: there is no attribute "href"
    									<div><g:plusone href="http://phim5.net"></g:plusone></div><br />

    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 1157, Column 49: element "g:plusone" undefined
    									<div><g:plusone href="http://phim5.net"></g:plusone></div><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 1158, Column 370: there is no attribute "allowTransparency"
    … overflow:hidden; width:235px; height:62px;" allowTransparency="true"></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 1168, Column 135: required attribute "alt" not specified
    …idth="300" border="0" src="http://easycome.us/ads/sex-viet-dj.very.vn.jpg"></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 1168, Column 139: end tag for "img" omitted, but OMITTAG NO was specified
    …idth="300" border="0" src="http://easycome.us/ads/sex-viet-dj.very.vn.jpg"></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 1168, Column 55: start tag was here
    …="_blank" href="http://bit.ly/HcjeLl"><img width="300" border="0" src="http://…
  • Error Line 1335, Column 147: duplicate specification of attribute "target"
    …phim online, xem phim online chat luong cao" target="_blank">xem phim hd</a> | 

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 1336, Column 135: duplicate specification of attribute "target"
    …em phim online chat luong cao" target="_blank"><b>xem phim online</b></a> | <a…

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Warning Line 1439, Column 19: character "<" is the first character of a delimiter but occurred as data
    			if(windowWidth < 1260){

    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.

Visitor Analysis

Daily Visitor
  • 1.073 visits

In Page Analysis