Jacquie et Michel, JACQUIE ET MICHEL, jackie et Michel, jakie et michel, SEXE AMATEUR GRATUIT,EXHIBITION AMATEUR VOTRE SITE DE SEXE GRATUIT ET AMATEUR ...

jacquieetmichel.net
  • Domain Name
    jacquieetmichel.net
  • Favicon
  • Google Page Rank
    3
  • Alexa Rank
    #22027
  • Page Size
    10.1 KB
  • Ip Address
    88.190.236.86
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    1 GIF, 0 JPG, 0 PNG

Website Meta Analysis

  • Title
    Exhibition Amateur, Jacquie et Michel
  • Meta Keyword
    Jacquie et Michel, JACQUIE ET MICHEL, jackie et michel, jakie et michel, couple �changiste fran�ais pr�sentent 1800 pages persos de contribution exhib de v�ritables amatrices et couples de France et du monde entier.sexe amateur gratuit,sexe,amateur,gratuit,SEXE GRATUIT,SEXE AMATEUR,SEXE AMATEUR GRATUIT,sexe amateur,sexe,amateur,sexe gratuit,sexe,gratuit,
  • Meta Description
    Jacquie et Michel, JACQUIE ET MICHEL, jackie et Michel, jakie et michel, SEXE AMATEUR GRATUIT,EXHIBITION AMATEUR VOTRE SITE DE SEXE GRATUIT ET AMATEUR

Technical Analysis

  • Webserver
    nginx
  • Ip Address
    88.190.236.86
  • Domain Age
    11 Years, 6 Months, 18 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: nginx
  • date: Fri, 09 Aug 2013 14:02:06 GMT
  • content-type: text/html
  • last-modified: Mon, 24 Jun 2013 15:50:05 GMT
  • connection: keep-alive
  • content-encoding: gzip
  • content-length: 2767
  • age: 26
  • x-google-cache-control: remote-cache-hit
  • via: HTTP/1.1 GWA (remote cache hit)
domain: jacquieetmichel.net
reg_created: 2002-01-21 14:58:04
expires: 2021-01-21 19:58:04
created: 2002-01-21 20:58:06
changed: 2011-10-04 12:09:36
transfer-prohibited: yes
ns0: ns0.jacquieetmichel.net 62.210.228.65
ns1: ns1.jacquieetmichel.net 62.210.228.67
ns2: ns2.jacquieetmichel.net 62.210.227.65
owner-c:
nic-hdl: PA522-GANDI
organisation: ~
person: PIRON Araceli
obfuscated: Obfuscated by Gandi
address: (Gandi) 63-65 boulevard Massena
zipcode: (Gandi) 75013
city: (Gandi) Paris
country: (Gandi) France
phone: (Gandi) +33.170377666
fax: (Gandi) +33.143730576
email: email
lastupdated: 2012-12-13 11:54:53
admin-c:
nic-hdl: PA522-GANDI
organisation: ~
person: PIRON Araceli
obfuscated: Obfuscated by Gandi
address: (Gandi) 63-65 boulevard Massena
zipcode: (Gandi) 75013
city: (Gandi) Paris
country: (Gandi) France
phone: (Gandi) +33.170377666
fax: (Gandi) +33.143730576
email: email
lastupdated: 2012-12-13 11:54:53
tech-c:
nic-hdl: PT1358-GANDI
organisation: SI7V
person: Pierre Tourbeaux
address: 29 rue d'Hesdin
zipcode: 62770
city: Blangy sur Ternoise
country: France
phone: +33.321064288
fax: +33.959745298
email: email
lastupdated: 2012-07-13 11:16:39
bill-c:
nic-hdl: PA522-GANDI
organisation: ~
person: PIRON Araceli
obfuscated: Obfuscated by Gandi
address: (Gandi) 63-65 boulevard Massena
zipcode: (Gandi) 75013
city: (Gandi) Paris
country: (Gandi) France
phone: (Gandi) +33.170377666
fax: (Gandi) +33.143730576
email: email
lastupdated: 2012-12-13 11:54:53

DNS Analysis


DNS servers
ns1.jacquieetmichel.net [62.210.228.67]
ns0.jacquieetmichel.net [62.210.228.65]
ns2.jacquieetmichel.net [62.210.227.65]


DNS Records

Answer records
jacquieetmichel.net SOA
server: ns0.jacquieetmichel.net
email: contact@si7v.fr
serial: 2011081901
refresh: 21600
retry: 3600
expire: 2419200
minimum ttl: 86400
3600s
jacquieetmichel.net NS  ns2.jacquieetmichel.net 3600s
jacquieetmichel.net NS  ns1.jacquieetmichel.net 3600s
jacquieetmichel.net NS  ns0.jacquieetmichel.net 3600s
jacquieetmichel.net A 88.190.236.86 3600s
jacquieetmichel.net MX
preference: 5
exchange: mail.jacquieetmichel.net
3600s

Authority records

Additional records
ns0.jacquieetmichel.net A 62.210.228.65 3600s
ns1.jacquieetmichel.net A 62.210.228.67 3600s
ns2.jacquieetmichel.net A 62.210.227.65 3600s
mail.jacquieetmichel.net A 88.190.222.15 3600s

IP 88.190.236.86 Analysis

  • Country Code
  • Country Code3
  • Country Name
  • City
  • Continent Code
  • Latitude
  • Longitude
  • No whois ip data for 88.190.236.86

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 26 Errors
  • 5 Warnings
Ratio Text/Html
  • 0.6899622495402188
Message Error
  • Error Line 2, Column 1: no document type declaration; implying "<!DOCTYPE HTML SYSTEM>"
    <HTML><HEAD><SCRIPT language="javascript"><!--

    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.

  • Error Line 2, Column 42: required attribute "TYPE" not specified
    <HTML><HEAD><SCRIPT language="javascript"><!--

    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 16, Column 21: an attribute value must be a literal unless it contains only name characters
    <META content=follow,index,all name=robots>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 18, Column 50: an attribute value must be a literal unless it contains only name characters
    <META http-equiv=reply-to content=jacquieetmichel@cvfrance.net>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 21, Column 12: an attribute value must be a literal unless it contains only name characters
    <BODY text=#ffff00 bgColor=#000000>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 21, Column 28: an attribute value must be a literal unless it contains only name characters
    <BODY text=#ffff00 bgColor=#000000>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 26, Column 31: required attribute "TYPE" not specified
    <SCRIPT language=JavaScript1.1>

    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 36, Column 99: end tag for element "A" which is not open
    …=' + hsd.referrer.replace('&', '$') + '" title="Mesurez votre audience"></a>');

    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 41, Column 9: required attribute "ALT" not specified
    border=0></A> </NOSCRIPT>

    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 42, Column 48: an attribute value must be a literal unless it contains only name characters
    <P align=center><FONT face="Arial Black" color=#ff3300 size=6><B>AVERTISSEMENT 

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 77, Column 27: an attribute value must be a literal unless it contains only name characters
    <P align=left><FONT color=#000000>s, anal, enculer, <BR></FONT></P>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 79, Column 75: there is no attribute "BORDERCOLOR"
    …llspacing="9" width="95%" bordercolor="#000000" bordercolorlight="#000000" bor…

    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 79, Column 102: there is no attribute "BORDERCOLORLIGHT"
    …ordercolor="#000000" bordercolorlight="#000000" bordercolordark="#000000" heig…

    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 79, Column 128: there is no attribute "BORDERCOLORDARK"
    …or="#000000" bordercolorlight="#000000" bordercolordark="#000000" height="190">

    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 79, Column 145: there is no attribute "HEIGHT"
    …or="#000000" bordercolorlight="#000000" bordercolordark="#000000" height="190">

    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 84, Column 9: end tag for "TABLE" omitted, but its declaration does not permit this
    </center>
    • 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 79, Column 1: start tag was here
    <table border="1" cellpadding="2" cellspacing="9" width="95%" bordercolor="#000…
  • Error Line 85, Column 6: document type does not allow element "TR" here
      <tr>

    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 94, Column 32: document type does not allow element "TD" here
        <td width="20%" height="31">

    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 97, Column 47: document type does not allow element "TD" here
        <td width="20%" height="31" align="center">

    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 100, Column 47: document type does not allow element "TD" here
    …width="20%" height="31" align="center"><font size="2">&nbsp;<a href="http://ww…

    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 102, Column 7: end tag for element "TR" which is not open
      </tr>

    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 103, Column 6: document type does not allow element "TR" here
      <tr>

    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 124, Column 6: document type does not allow element "TR" here
      <tr>

    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 142, Column 6: document type does not allow element "TR" here
      <tr>

    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 163, Column 6: document type does not allow element "TR" here
      <tr>

    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 177, Column 8: end tag for element "TABLE" which is not open
    </table>

    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
  • 3.033 visits