WARNING! - GAY PORN - QUEER ME NOW - ADULT BLOG - GAY SEX - NAKED MEN Queer Me Now is intended for individuals 18 years of age and older and contains ...

queermenow.net
  • Domain Name
    queermenow.net
  • Favicon
  • Google Page Rank
    3
  • Alexa Rank
    #49747
  • Page Size
    3.9 KB
  • Ip Address
    216.201.83.249
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    1 GIF, 1 JPG, 0 PNG

Website Meta Analysis

  • Title
    WARNING! | QUEER ME NOW : The Hardcore Gay Porn Blog
  • Meta Keyword
  • Meta Description
      WARNING! - GAY PORN - QUEER ME NOW - ADULT BLOG - GAY SEX - NAKED MEN Queer Me Now is intended for individuals 18 years of age and older and contains materials of sexually explicit nature. If you are not of legal age or if it is illegal for ...

Technical Analysis

  • Webserver
    Apache/1.3.41 (Unix)
  • Ip Address
    216.201.83.249
  • Domain Age
    5 Years, 2 Months, 6 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Sat, 16 Feb 2013 03:33:01 GMT
  • server: Apache/1.3.41 (Unix)
  • content-type: text/html
  • content-length: 3387
  • age: 9
  • x-google-cache-control: remote-cache-hit
  • via: HTTP/1.1 GWA (remote cache hit)
No data whois for queermenow.net

DNS Analysis


DNS servers
ns1.nationalnet.com [216.201.81.254]
ns2.nationalnet.com [216.201.87.28]


DNS Records

Answer records
queermenow.net A 216.201.83.249 900s
queermenow.net SOA
server: ns1.nationalnet.com
email: dnsadmin@nationalnet.com
serial: 2012022801
refresh: 28800
retry: 7200
expire: 604800
minimum ttl: 86400
900s
queermenow.net NS  ns1.nationalnet.com 900s
queermenow.net NS  ns2.nationalnet.com 900s
queermenow.net MX
preference: 20
exchange: mailstore1.secureserver.net
900s
queermenow.net MX
preference: 10
exchange: smtp.secureserver.net
900s

Authority records

Additional records
ns2.nationalnet.com A 216.201.87.28 900s
ns1.nationalnet.com A 216.201.81.254 900s

IP 216.201.83.249 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Kennesaw
  • Continent Code
    30152
  • Latitude
    770
  • Longitude
    524
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 216.201.83.249"
    #
    # Use "?" to get help.
    #

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

    NationalNet, Inc. NATIONALNET-2 (NET-216-201-80-0-1) 216.201.80.0 - 216.201.95.255
    NationalNet, Managed Services NATNET-MANAGED-VL82 (NET-216-201-82-0-1) 216.201.82.0 - 216.201.83.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
  • 16 Errors
  • 6 Warnings
Ratio Text/Html
  • 0.5159267619764234
Message Error
  • Error Line 1, Column 1: no document type declaration; implying "<!DOCTYPE HTML SYSTEM>"
    <HTML>

    The checked page did not contain a document type ("DOCTYPE") declaration. The Validator has tried to validate with a fallback DTD, but this is quite likely to be incorrect and will generate a large number of incorrect error messages. It is highly recommended that you insert the proper DOCTYPE declaration in your document -- instructions for doing this are given above -- and it is necessary to have this declaration before the page can be declared to be valid.

  • Warning Line 6, Column 79: NET-enabling start-tag requires SHORTTAG YES
    <meta name="verify-v1" content="s4cn4oxU+9R/gKBEfe44QZ6yhJ5OHCkJyjMbfy9wsn4=" />

    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 6, Column 80: character data is not allowed here
    <meta name="verify-v1" content="s4cn4oxU+9R/gKBEfe44QZ6yhJ5OHCkJyjMbfy9wsn4=" />

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 12, Column 100: there is no attribute "MARGINHEIGHT"
    …#FFFFFF" ALINK="#000000" MARGINHEIGHT="0" MARGINWIDTH="0" LEFTMARGIN="0" TOPMA…

    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 12, Column 116: there is no attribute "MARGINWIDTH"
    … ALINK="#000000" MARGINHEIGHT="0" MARGINWIDTH="0" LEFTMARGIN="0" TOPMARGIN="0">

    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 12, Column 131: there is no attribute "LEFTMARGIN"
    … ALINK="#000000" MARGINHEIGHT="0" MARGINWIDTH="0" LEFTMARGIN="0" TOPMARGIN="0">

    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 12, Column 145: there is no attribute "TOPMARGIN"
    … ALINK="#000000" MARGINHEIGHT="0" MARGINWIDTH="0" LEFTMARGIN="0" TOPMARGIN="0">

    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 16, Column 27: there is no attribute "HEIGHT"
    <TABLE WIDTH="750" HEIGHT="15" CELLPADDING="0" CELLSPACING="0" BORDER="0"><TR><…

    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 24, Column 49: value of attribute "VALIGN" cannot be "CENTER"; must be one of "TOP", "MIDDLE", "BOTTOM", "BASELINE"
    <TD WIDTH="508" BGCOLOR="#222222" VALIGN="CENTER"><SPAN CLASS="NF">

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 25, Column 8: document type does not allow element "CENTER" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <CENTER><IMG SRC="blog/wp-content/gallery/queermenow.gif" WIDTH="300" HEIGHT="6…

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

  • Error Line 25, Column 136: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    … WIDTH="300" HEIGHT="60" BORDER="0" ALT="Queer Me Now Blog Banner"></CENTER><P>

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

  • Error Line 27, Column 248: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …t is illegal for you to view such material, please <B>EXIT</B> immediately! <P>

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

  • Error Line 29, Column 209: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …rs of this website will not be held liable for your choice to move forward. <P>

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

  • Error Line 31, Column 235: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …, you may <B>NOT</B> continue and must click on the <B>EXIT</B> button now! <P>

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

  • Error Line 33, Column 103: document type does not allow element "P" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    …, you certify having read, understood and agreed to all of the above.</font><P>

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

  • Error Line 35, Column 8: document type does not allow element "CENTER" here; missing one of "APPLET", "OBJECT", "MAP", "IFRAME", "BUTTON" start-tag
    <CENTER><FONT SIZE="+3"><A HREF="http://www.google.com">EXIT</A> &nbsp;&nbsp;&n…

    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 49, Column 296: NET-enabling start-tag requires SHORTTAG YES
    …nter.com/3264234/0/90fe1108/0/" alt="web site analytic" /></a></div></noscript>

    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 62, Column 7: end tag for "CENTER" omitted, but its declaration does not permit this
    </BODY>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 14, Column 1: start tag was here
    <CENTER>

Visitor Analysis

Daily Visitor
  • 4.200 visits
Daily Visitor