Gayporn reviews, gayporn blog, gaytube and gay videos on demand at HomoSexBlog ...

homosexblog.com
  • Domain Name
    homosexblog.com
  • Favicon
  • Google Page Rank
    3
  • Alexa Rank
    #2802073
  • Page Size
    84.5 KB
  • Ip Address
    69.163.176.138
  • Heading
    H1: 1, H2: 1, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 14 JPG, 6 PNG

Website Meta Analysis

  • Title
    Homo Sex Blog - daily fresh gay porn blog
  • Meta Keyword
    gaysex, pornblog, gayporn, gaypornblog, gayblog, gayporn, homosexblog, homosex, gaytube, porntube, gay, videos, pictures, photoblog
  • Meta Description
    Gayporn reviews, gayporn blog, gaytube and gay videos on demand at HomoSexBlog

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    69.163.176.138
  • Domain Age
    6 Years, 7 Months, 7 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Sat, 07 Sep 2013 20:58:08 GMT
  • server: Apache
  • x-mod-pagespeed: 1.1.23.1-2169
  • vary: Accept-Encoding
  • content-encoding: gzip
  • cache-control: max-age=0, no-cache
  • content-type: text/html; charset=windows-1250
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Name: homosexblog.com

Registrant Contact:
homosexblog.com Private Registrant email
DreamHost Web Hosting
417 Associated Rd #324
Brea, CA 92821
US
+1.7147064182

Administrative Contact:
homosexblog.com Private Registrant email
DreamHost Web Hosting
417 Associated Rd #324
Brea, CA 92821
US
+1.7147064182

Technical Contact:
homosexblog.com Private Registrant email
DreamHost Web Hosting
417 Associated Rd #324
Brea, CA 92821
US
+1.7147064182

Billing Contact:
homosexblog.com Private Registrant email
DreamHost Web Hosting
417 Associated Rd #324
Brea, CA 92821
US
+1.7147064182

Record created on 2007-02-04 08:53:24.
Record expires on 2014-02-04 08:53:24.

Domain servers in listed order:

ns1.dreamhost.com
ns2.dreamhost.com
ns3.dreamhost.com

DNS Analysis


DNS servers
ns3.dreamhost.com
ns1.dreamhost.com
ns2.dreamhost.com


DNS Records

Answer records
homosexblog.com A 69.163.176.138 14400s
homosexblog.com MX
preference: 0
exchange: mx1.sub4.homie.mail.dreamhost.com
14400s
homosexblog.com NS  ns1.dreamhost.com 14400s
homosexblog.com NS  ns3.dreamhost.com 14400s
homosexblog.com NS  ns2.dreamhost.com 14400s
homosexblog.com MX
preference: 0
exchange: mx2.sub4.homie.mail.dreamhost.com
14400s
homosexblog.com SOA
server: ns1.dreamhost.com
email: hostmaster@dreamhost.com
serial: 2012040700
refresh: 15991
retry: 1800
expire: 1814400
minimum ttl: 14400
14400s

Authority records

Additional records
ns3.dreamhost.com A 66.33.216.216 14400s
mx1.sub4.homie.mail.dreamhost.com A 208.97.132.226 14400s
mx2.sub4.homie.mail.dreamhost.com A 208.97.132.227 14400s
ns1.dreamhost.com A 66.33.206.206 14400s
ns2.dreamhost.com A 208.96.10.221 14400s

IP 69.163.176.138 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Brea
  • Continent Code
    92821
  • Latitude
    714
  • Longitude
    803
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 69.163.176.138"
    #
    # Use "?" to get help.
    #

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

    NetRange: 69.163.128.0 - 69.163.255.255
    CIDR: 69.163.128.0/17
    OriginAS: AS26347
    NetName: DREAMHOST-BLK9
    NetHandle: NET-69-163-128-0-1
    Parent: NET-69-0-0-0-0
    NetType: Direct Allocation
    Comment: ** For abuse issues, please contact abuse@dreamhost.com **
    RegDate: 2009-03-27
    Updated: 2012-03-02
    Ref: http://whois.arin.net/rest/net/NET-69-163-128-0-1

    OrgName: New Dream Network, LLC
    OrgId: NDN
    Address: 417 Associated Rd.
    Address: PMB #257
    City: Brea
    StateProv: CA
    PostalCode: 92821
    Country: US
    RegDate: 2001-04-17
    Updated: 2012-09-27
    Ref: http://whois.arin.net/rest/org/NDN

    OrgNOCHandle: ZD69-ARIN
    OrgNOCName: Network Operations
    OrgNOCPhone: +1-714-706-4182
    OrgNOCEmail: netops@hq.dreamhost.com
    OrgNOCRef: http://whois.arin.net/rest/poc/ZD69-ARIN

    OrgTechHandle: MCRAE6-ARIN
    OrgTechName: McRae, Kenneth
    OrgTechPhone: +1-424-646-4949
    OrgTechEmail: netops@hq.newdream.net
    OrgTechRef: http://whois.arin.net/rest/poc/MCRAE6-ARIN

    OrgAbuseHandle: DAT5-ARIN
    OrgAbuseName: DreamHost Abuse Team
    OrgAbusePhone: +1-714-706-4182
    OrgAbuseEmail: abuse@dreamhost.com
    OrgAbuseRef: http://whois.arin.net/rest/poc/DAT5-ARIN

    RNOCHandle: ZD69-ARIN
    RNOCName: Network Operations
    RNOCPhone: +1-714-706-4182
    RNOCEmail: netops@hq.dreamhost.com
    RNOCRef: http://whois.arin.net/rest/poc/ZD69-ARIN

    RTechHandle: ZD69-ARIN
    RTechName: Network Operations
    RTechPhone: +1-714-706-4182
    RTechEmail: netops@hq.dreamhost.com
    RTechRef: http://whois.arin.net/rest/poc/ZD69-ARIN

    RAbuseHandle: DAT5-ARIN
    RAbuseName: DreamHost Abuse Team
    RAbusePhone: +1-714-706-4182
    RAbuseEmail: abuse@dreamhost.com
    RAbuseRef: http://whois.arin.net/rest/poc/DAT5-ARIN

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

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 119 Errors
  • 17 Warnings
Ratio Text/Html
  • 0.6964588989659755
Message Error
  • Warning Line 13, Column 68: NET-enabling start-tag requires SHORTTAG YES
    <meta name="viewport" content="width=device-width; initial-scale=1"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 14, Column 61: document type does not allow element "LINK" here
    <LINK HREF="basisgreen.css" REL="stylesheet" TYPE="text/css">

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 16, Column 7: end tag for element "HEAD" which is not open
    </head><body>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 16, Column 13: document type does not allow element "BODY" here
    </head><body>

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 75, Column 15: there is no attribute "HEIGHT"
    <table height="42" cellpadding="3" cellspacing="0" width="860" bgcolor="#660205…

    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 146, Column 226: required attribute "ALT" not specified
    …blog.com/content/billy-darius0.jpg" title="Eurocreme" border="0"></a></div><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>.

Visitor Analysis

Daily Visitor
  • 38 visits