thumbzilla.com

Thumbzilla - free porn bookmark ...

thumbzilla.com
Domain Name thumbzilla.com
Favicon thumbzilla.com
Google Page Rank 3
Alexa Rank #106593
Page Size 4.6 KB
Ip Address 64.88.249.35
Heading H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
Images 0 GIF, 2 JPG, 0 PNG

Website Meta Analysis

Title Free Porn Quality Matters at Thumbzilla.com full free xxx videos
Meta Keyword thumbzilla.com, quality, porn, free porn, hardcore, pics, gallery, archives, galleries, xxx, adult, free, thumbnail
Meta Description Thumbzilla - free porn bookmark

Technical Analysis

Webserver Apache
Ip Address 64.88.249.35
Domain Age
Javascript Library
Language used HTML, CSS, Javascript

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

HTML Analysis

  • date: Wed, 21 Aug 2013 18:00:53 GMT
  • server: Apache
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA

No data whois for thumbzilla.com

Technical Analysis


DNS servers
ns1.swiftwill.com [66.28.176.37]
ns2.swiftwill.com [146.82.201.184]
ns3.swiftwill.com [146.82.201.162]


DNS Records

Answer records
thumbzilla.com MX
preference: 10
exchange: mail.thumbzilla.com
300s
thumbzilla.com A 64.88.249.35 300s
thumbzilla.com NS  ns3.swiftwill.com 300s
thumbzilla.com NS  ns1.swiftwill.com 300s
thumbzilla.com NS  ns2.swiftwill.com 300s
thumbzilla.com SOA
server: ns1.swiftwill.com
email: swiftwill@swiftwill.com
serial: 2010050405
refresh: 300
retry: 7200
expire: 1209600
minimum ttl: 300
300s

Authority records

Additional records

IP 64.88.249.35 Analysis

Country Code : US
Country Code3 : USA
Country Name : United States
City : Waltham
Continent Code : 02451
Latitude : 781
Longitude : 506

#
# Query terms are ambiguous. The query is assumed to be:
# "n 64.88.249.35"
#
# Use "?" to get help.
#

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

NetRange: 64.88.240.0 - 64.88.255.255
CIDR: 64.88.240.0/20
OriginAS: AS26486, AS30361
NetName: SWIFTWILL-INC
NetHandle: NET-64-88-240-0-1
Parent: NET-64-0-0-0-0
NetType: Direct Allocation
Comment: http://www.swiftwill.com
RegDate: 2008-03-13
Updated: 2012-03-02
Ref: http://whois.arin.net/rest/net/NET-64-88-240-0-1

OrgName: Swiftwill, Inc.
OrgId: SWIFT-19
Address: 738 Main St. PMB 140
City: Waltham
StateProv: MA
PostalCode: 02451
Country: US
RegDate: 2007-03-06
Updated: 2011-09-24
Ref: http://whois.arin.net/rest/org/SWIFT-19

OrgAbuseHandle: PAULE-ARIN
OrgAbuseName: Paulete, Michael
OrgAbusePhone: +1-877-890-0518
OrgAbuseEmail: mp@swiftwill.com
OrgAbuseRef: http://whois.arin.net/rest/poc/PAULE-ARIN

OrgTechHandle: PAULE-ARIN
OrgTechName: Paulete, Michael
OrgTechPhone: +1-877-890-0518
OrgTechEmail: mp@swiftwill.com
OrgTechRef: http://whois.arin.net/rest/poc/PAULE-ARIN

RNOCHandle: PAULE-ARIN
RNOCName: Paulete, Michael
RNOCPhone: +1-877-890-0518
RNOCEmail: mp@swiftwill.com
RNOCRef: http://whois.arin.net/rest/poc/PAULE-ARIN

RAbuseHandle: PAULE-ARIN
RAbuseName: Paulete, Michael
RAbusePhone: +1-877-890-0518
RAbuseEmail: mp@swiftwill.com
RAbuseRef: http://whois.arin.net/rest/poc/PAULE-ARIN

RTechHandle: PAULE-ARIN
RTechName: Paulete, Michael
RTechPhone: +1-877-890-0518
RTechEmail: mp@swiftwill.com
RTechRef: http://whois.arin.net/rest/poc/PAULE-ARIN

#
# 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
  • 7 Errors
  • 15 Warnings
Ratio Text/Html

0.7113727138953121

Message Error
  • Warning Line 8, Column 93: NET-enabling start-tag requires SHORTTAG YES
    …gle-site-verification" content="Yh-d8G8r1-ul1FHsECWtbRYNMf727bW6ZZ54Kixjbvw" />

    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 10, Column 91: document type does not allow element "LINK" here
    …text/css" rel="stylesheet" href="http://www.thumbzilla.com/src/thumbzilla.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 11, Column 58: document type does not allow element "META" here
    <meta name="RATING" content="RTA-5042-1996-1400-1577-RTA">

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

  • Warning Line 12, Column 109: NET-enabling start-tag requires SHORTTAG YES
    …ww.thumbzilla.com/labels.rdf" type="application/rdf+xml" title="ICRA labels" />

    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 12, Column 109: document type does not allow element "LINK" here
    …ww.thumbzilla.com/labels.rdf" type="application/rdf+xml" title="ICRA labels" />

    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 13, Column 301: document type does not allow element "META" here
    …mbzilla.com" r (n 3 s 3 v 0 l 2 oa 0 ob 0 oc 0 od 0 oe 0 of 0 og 0 oh 0 c 3))'>

    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 20, Column 7: end tag for element "HEAD" which is not open
    </head>

    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 21, Column 6: document type does not allow element "BODY" here
    <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).

  • Warning Line 26, Column 129: NET-enabling start-tag requires SHORTTAG YES
    …e="Thumbzilla" alt="thumbzilla logo slice top" width="600" height="200" /></td>

    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.

  • Warning Line 29, Column 116: NET-enabling start-tag requires SHORTTAG YES
    …bottom.jpg" alt="thumbzilla logo slice bottom" width="600" height="104" /></td>

    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.

  • Warning Line 33, Column 7: NET-enabling start-tag requires SHORTTAG YES
    		<br />

    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.

  • Warning Line 35, Column 7: NET-enabling start-tag requires SHORTTAG YES
    		<br />

    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.

  • Warning Line 37, Column 7: NET-enabling start-tag requires SHORTTAG YES
    		<br />

    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.

  • Warning Line 39, Column 7: NET-enabling start-tag requires SHORTTAG YES
    		<br />

    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.

  • Warning Line 41, Column 7: NET-enabling start-tag requires SHORTTAG YES
    		<br />

    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.

  • Warning Line 43, Column 7: NET-enabling start-tag requires SHORTTAG YES
    		<br />

    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.

  • Warning Line 44, Column 7: NET-enabling start-tag requires SHORTTAG YES
    		<br />

    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.

  • Warning Line 49, Column 7: NET-enabling start-tag requires SHORTTAG YES
    		<br />

    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.

  • Warning Line 50, Column 7: NET-enabling start-tag requires SHORTTAG YES
    		<br />

    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.

  • Warning Line 52, Column 7: NET-enabling start-tag requires SHORTTAG YES
    		<br />

    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.

  • Warning Line 54, Column 7: NET-enabling start-tag requires SHORTTAG YES
    		<br />

    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 58, Column 14: end tag for element "DIV" which is not open
            </div>

    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.

Visitor Analysis

Daily Visitor

1.983 visits