Pinoy Lovers - Live Video Chat, Exchange FaceBook, Watch Free Pinoy Movies and Filipino channel Online, Filipino Shows, Dramas, Telenovelas, Asianovela, kdrama, korean drama, Video, Episode Replay, Sports, News, updates, Tagalog Movies Online. ...

pinoylovers.com
  • Domain Name
    pinoylovers.com
  • Favicon
  • Google Page Rank
    0
  • Alexa Rank
    #97826
  • Page Size
    64.2 KB
  • Ip Address
    207.7.80.100
  • Heading
    H1: 1, H2: 1, H3: 32, H4: 0, H5: 2, H6: 0
  • Images
    1 GIF, 33 JPG, 7 PNG

Website Meta Analysis

  • Title
    Pinoy Channel | Pinoy Lovers
  • Meta Keyword
    pinoiylovers, pinoy lovers, pinoy, ofw, pinoy ofw, watch, free, live, live stream, video, pinoy channel, pinoy movies, teleserye, pinoy series, kdrama, korean drama, asianovela, abs-cbn, gma, studio 23, tv5, asap, pinoy tv show, tfc, tagalog shows, Filipino channel, budoy, live, willing willie, 100 days to heaven, secret garden, mula sa puso, mutya, gma show, angelito, showtime, eat bulaga, ikaw ay pag-ibig, hiyas
  • Meta Description
    Pinoy Lovers - Live Video Chat, Exchange FaceBook, Watch Free Pinoy Movies and Filipino channel Online, Filipino Shows, Dramas, Telenovelas, Asianovela, kdrama, korean drama, Video, Episode Replay, Sports, News, updates, Tagalog Movies Online. | Pinoy Lovers

Technical Analysis

  • Webserver
    nginx admin
  • Ip Address
    207.7.80.100
  • 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 pinoylovers.com.

HTML Analysis

  • server: nginx admin
  • date: Sun, 14 Apr 2013 04:35:11 GMT
  • content-type: text/html; charset=UTF-8
  • connection: keep-alive
  • vary: Accept-Encoding
  • last-modified: Sun, 14 Apr 2013 04:32:01 GMT
  • cache-control: max-age=3, must-revalidate
  • expires: Sun, 14 Apr 2013 04:35:14 GMT
  • x-cache: HIT from Backend
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain name: pinoylovers.com

Registrant Contact:
WhoisGuard
WhoisGuard Protected ()

Fax:
11400 W. Olympic Blvd. Suite 200
Los Angeles, CA 90064
US

Administrative Contact:
WhoisGuard
WhoisGuard Protected ( email )
+1.6613102107
Fax: +1.6613102107
11400 W. Olympic Blvd. Suite 200
Los Angeles, CA 90064
US

Technical Contact:
WhoisGuard
WhoisGuard Protected ( email )
+1.6613102107
Fax: +1.6613102107
11400 W. Olympic Blvd. Suite 200
Los Angeles, CA 90064
US

Status: Locked

Name Servers:
ns1.pinoylovers.com
ns2.pinoylovers.com

Creation date: 25 Apr 2011 10:10:00
Expiration date: 25 Apr 2013 05:10:00

DNS Analysis


DNS servers
ns1.bics.info
ns2.bics.info


DNS Records

Answer records
pinoylovers.com MX
preference: 0
exchange: pinoylovers.com
14400s
pinoylovers.com SOA
server: ns1.bics.info
email: jamiltonluiz43@gmail.com
serial: 2012122901
refresh: 86400
retry: 7200
expire: 3600000
minimum ttl: 86400
86400s
pinoylovers.com NS  ns1.bics.info 86400s
pinoylovers.com NS  ns2.bics.info 86400s
pinoylovers.com A 207.7.80.100 14400s

Authority records

Additional records
pinoylovers.com A 207.7.80.100 14400s
ns1.bics.info A 207.7.80.100 14400s
ns2.bics.info A 207.7.81.100 14400s

IP 207.7.80.100 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Leland
  • Continent Code
    28451
  • Latitude
    910
  • Longitude
    550
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 207.7.80.100"
    #
    # Use "?" to get help.
    #

    #
    # The following results may also be obtained via:
    # http://whois.arin.net/rest/nets;q=207.7.80.100?showDetails=true&showARIN=false&ext=netref2
    #

    PrivateSystems Networks TX PRIVATE-TX-3 (NET-207-7-80-0-2) 207.7.80.0 - 207.7.87.255
    PrivateSystems Networks PRIVATE-3 (NET-207-7-80-0-1) 207.7.80.0 - 207.7.95.255


    #
    # ARIN WHOIS data and services are subject to the Terms of Use
    # available at: https://www.arin.net/whois_tou.html
    #

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 140 Errors
  • 22 Warnings
Ratio Text/Html
  • 0.7676675489032886
Message Error
  • Error Line 3, Column 7: required attribute "type" not specified
    <style>

    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 13, Column 12: there is no attribute "name"
    <META name="y_key" content="902c6b0c8e95562f" />

    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 13, Column 28: there is no attribute "content"
    <META name="y_key" content="902c6b0c8e95562f" />

    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 13, Column 48: element "META" undefined
    <META name="y_key" content="902c6b0c8e95562f" />

    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 17, Column 20: there is no attribute "property"
        <meta property="fb:app_id" content="242895839165285">

    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 17, Column 58: end tag for "meta" omitted, but OMITTAG NO was specified
        <meta property="fb:app_id" content="242895839165285">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

Visitor Analysis

Daily Visitor
  • 1.983 visits
Daily Visitor