secretsexwith.me has Alexa Rank 391.338 and Google Page Rank is 0

secretsexwith.me
  • Domain Name
    secretsexwith.me
  • Favicon
  • Google Page Rank
    0
  • Alexa Rank
    #391338
  • Page Size
    44 B
  • Ip Address
    141.101.117.151
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 0 JPG, 0 PNG

Website Meta Analysis

  • Title
  • Meta Keyword
  • Meta Description

Technical Analysis

  • Webserver
    cloudflare-nginx
  • Ip Address
    141.101.117.151
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from secretsexwith.me.

HTML Analysis

  • server: cloudflare-nginx
  • date: Wed, 26 Jun 2013 23:40:11 GMT
  • content-type: text/html
  • connection: keep-alive
  • last-modified: Wed, 01 May 2013 04:25:25 GMT
  • cf-ray: 84dbdbc21b1038e
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
WHOIS TERMS & CONDITIONS: Access to .ME WHOIS information is provided to
assist persons in determining the contents of a domain name registration
record in the .ME registry database. The data in this record is provided by
.ME Registry for informational purposes only, and .ME Registry does not
guarantee its accuracy. This service is intended only for query-based
access. You agree that you will use this data only for lawful purposes
and that, under no circumstances will you use this data to: (a) allow,
enable, or otherwise support the transmission by e-mail, telephone,
facsimile, or other electronic processes of mass unsolicited, commercial
advertising or solicitations to entities other than the data recipient's own
existing customers; or (b) enable high volume, automated, electronic
processes that send queries or data to the systems of Registry Operator,
except as reasonably necessary to register domain names or modify existing
registrations. All rights reserved. .ME Registry reserves the right to modify
these terms at any time. By submitting this query, you agree to abide by this
policy.

Domain ID:D4894068-ME
Domain Name:SECRETSEXWITH.ME
Domain Create Date:15-Jul-2012 05:19:19 UTC
Domain Last Updated Date:07-Nov-2012 20:56:03 UTC
Domain Expiration Date:15-Jul-2013 05:19:19 UTC
Last Transferred Date:
Sponsoring Registrar:eNom Inc R32-ME
Created by:eNom Inc R32-ME
Last Updated by Registrar:eNom Inc R32-ME
Domain Status:CLIENT TRANSFER PROHIBITED
Registrant ID:2a624c4a03a5caf1
Registrant Name:WhoisGuard Protected
Registrant Organization:WhoisGuard
Registrant Address:11400 W. Olympic Blvd. Suite 200
Registrant Address2:
Registrant Address3:
Registrant City:Los Angeles
Registrant State/Province:CA
Registrant Country/Economy:US
Registrant Postal Code:90064
Registrant Phone:+1.6613102107
Registrant Phone Ext.:
Registrant FAX:
Registrant FAX Ext.:
Registrant E-mail: email
Admin ID:123b5aa7776a9d0d
Admin Name:WhoisGuard Protected
Admin Organization:WhoisGuard
Admin Address:11400 W. Olympic Blvd. Suite 200
Admin Address2:
Admin Address3:
Admin City:Los Angeles
Admin State/Province:CA
Admin Country/Economy:US
Admin Postal Code:90064
Admin Phone:+1.6613102107
Admin Phone Ext.:
Admin FAX:
Admin FAX Ext.:
Admin E-mail: email
Tech ID:b2673ea7776a9d0d
Tech Name:WhoisGuard Protected
Tech Organization:WhoisGuard
Tech Address:11400 W. Olympic Blvd. Suite 200
Tech Address2:
Tech Address3:
Tech City:Los Angeles
Tech State/Province:CA
Tech Country/Economy:US
Tech Postal Code:90064
Tech Phone:+1.6613102107
Tech Phone Ext.:
Tech FAX:
Tech FAX Ext.:
Tech E-mail: email
Nameservers:NORM.NS.CLOUDFLARE.COM
Nameservers:LOLA.NS.CLOUDFLARE.COM
Nameservers:
Nameservers:
Nameservers:
Nameservers:
Nameservers:
Nameservers:
Nameservers:
Nameservers:
Nameservers:
Nameservers:
Nameservers:


DNS Analysis


DNS servers
norm.ns.cloudflare.com [173.245.59.134]
lola.ns.cloudflare.com [173.245.58.132]


DNS Records

Answer records
secretsexwith.me NS  norm.ns.cloudflare.com 86400s
secretsexwith.me A 141.101.116.151 300s
secretsexwith.me NS  lola.ns.cloudflare.com 86400s
secretsexwith.me SOA
server: lola.ns.cloudflare.com
email: dns@cloudflare.com
serial: 2012110713
refresh: 10000
retry: 2400
expire: 604800
minimum ttl: 3600
86400s
secretsexwith.me A 141.101.117.151 300s

Authority records

Additional records

IP 141.101.117.151 Analysis

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 1 Errors
  • 3 Warnings
Ratio Text/Html
  • 0.8863636363636364
Message Error
  • Error Line 1, Column 1: no document type declaration; will parse without validation
    <br/><br/><br/><br/><br/><center>*** Testing ***</center>

    The document type could not be determined, because the document had no correct DOCTYPE declaration. The document does not look like HTML, therefore automatic fallback could not be performed, and the document was only checked against basic markup syntax.

    Learn how to add a doctype to your document from our FAQ, or use the validator's Document Type option to validate your document against a specific Document Type.

  • Warning Line 1, Column 4: NET-enabling start-tag requires SHORTTAG YES
    <br/><br/><br/><br/><br/><center>*** Testing ***</center>

    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 1, Column 9: NET-enabling start-tag requires SHORTTAG YES
    <br/><br/><br/><br/><br/><center>*** Testing ***</center>

    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 1, Column 14: NET-enabling start-tag requires SHORTTAG YES
    <br/><br/><br/><br/><br/><center>*** Testing ***</center>

    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 1, Column 19: NET-enabling start-tag requires SHORTTAG YES
    <br/><br/><br/><br/><br/><center>*** Testing ***</center>

    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 1, Column 24: NET-enabling start-tag requires SHORTTAG YES
    <br/><br/><br/><br/><br/><center>*** Testing ***</center>

    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.

Visitor Analysis

Daily Visitor
  • 5 visits