christiandatingforfree.com

Christian Dating for Free is the #1 Online Christian Community for meeting Quality Christian Singles. 100% Free Service with no hidden charges. ...

Display Widget for this domain on your website. Click Here
Processing update domain...

Overview Info

  • Domain Name
    christiandatingforfree.com
  • Favicon
  • Alexa Rank
    #41437
  • Google Page Rank
    PR 4
  • Ip Address
    50.56.167.57
  • Page Size
    72.2 KB
  • Images
    29 GIF, 8 JPG, 0 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 0 0 0 0 0

Website Meta Analysis



  • Title
    Christian Dating For Free | 100% Free Service for Christian Singles
  • Meta Keyword
    Christian Dating, Christian Single, Christian Singles, Free Christian Dating, Christian dating Service, 100% Free Service for Christian Singles
  • Meta Description
    Christian Dating for Free is the #1 Online Christian Community for meeting Quality Christian Singles. 100% Free Service with no hidden charges.

Technical Analysis



  • Webserver
    Apache
  • Ip Address
    50.56.167.57
  • Domain Age
    6 Years, 10 Months, 26 days.
  • Javascript Library
    jquery, prototype
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Mon, 08 Jul 2013 13:26:04 GMT
  • server: Apache
  • x-powered-by: PHP/5.3.20
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • vary: Accept-Encoding
  • content-encoding: gzip
  • content-length: 11290
  • content-type: text/html; charset=iso-8859-1
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
E Dating For Free, Inc.
20929 Ventura Blvd.
Suite 47362
Woodland Hills, California 91364
United States

Domain Name: CHRISTIANDATINGFORFREE.COM
Created on: 18-Aug-06
Expires on: 18-Aug-21
Last Updated on: 13-Mar-12

Administrative Contact:
Kim, Doron email
E Dating For Free, Inc.
20929 Ventura Blvd.
Suite 47362
Woodland Hills, California 91364
United States
+1.3233947533

Technical Contact:
Kim, Doron email
E Dating For Free, Inc.
20929 Ventura Blvd.
Suite 47362
Woodland Hills, California 91364
United States
+1.3233947533

Domain servers in listed order:
NS2.RACKSPACE.COM
NS.RACKSPACE.COM

DNS Analysis


DNS servers
ns2.rackspace.com [65.61.188.4]
ns.rackspace.com [69.20.95.4]


DNS Records

Answer records
christiandatingforfree.com SOA
server: ns.rackspace.com
email: hostmaster@rackspace.com
serial: 1357216470
refresh: 86400
retry: 7200
expire: 604800
minimum ttl: 300
300s
christiandatingforfree.com A 50.56.167.57 300s
christiandatingforfree.com MX
preference: 10
exchange: mail.christiandatingforfree.com
300s
christiandatingforfree.com NS  ns2.rackspace.com 300s
christiandatingforfree.com NS  ns.rackspace.com 300s
christiandatingforfree.com TXT v=spf1 a mx ptr include:sendgrid.net ~all 300s
christiandatingforfree.com TXT smtpapi._domainkey.server1.christ =k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDPtW5iwpXVPiH5FzJ7Nrl8USzuY9zqqzjE0D1r04xDN6qwziDnmgcFNNfMewVKN2D1O+2J9N14hRprzByFwfQW76yojh54Xu3uSbQ3JP0A7k8o8GutRF8zbFUA8n0ZH2y0cIEjMliXY4W4LwPA7m4q0ObmvSjhd63O9d8z1X 300s

Authority records

Additional records

IP 50.56.167.57 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    San Antonio
  • Continent Code
    78218
  • Latitude
    210
  • Longitude
    641
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 50.56.167.57"
    #
    # Use "?" to get help.
    #

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

    Rackspace Hosting RACKS-8-NET-4 (NET-50-56-0-0-1) 50.56.0.0 - 50.57.255.255
    Cloud Loadbalancing as a Service-LBaaS (DFW) RACKS-8-1328805973650048 (NET-50-56-166-0-1) 50.56.166.0 - 50.56.167.255


    #
    # 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
  • 212 Errors
  • 2 Warnings
Ratio Text/Html
  • 0.572698369749036
Message Error
  • Error Line 104, Column 17: there is no attribute "width"
          <tr width="100%">

    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 131, Column 90: there is no attribute "addthis:userid"
    …lass="addthis_button_facebook_follow" addthis:userid="FreeChristianDating"></a>

    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 147, Column 157: end tag for "img" omitted, but OMITTAG NO was specified
    …if" width="43px" height="34px" alt=""> 

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 147, Column 41: start tag was here
    <img src="http://pics.christiandatingfor…
  • Error Line 149, Column 120: there is no attribute "width"
    …e.com/" class="home_Image_Link" width="61px" height="34px" ></a>              …

    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 149, Column 134: there is no attribute "height"
    …"home_Image_Link" width="61px" height="34px" ></a>                            …

    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 191, Column 53: value of attribute "valign" cannot be "center"; must be one of "top", "middle", "bottom", "baseline"
            <td colspan="9" align="right" valign="center" height="28px">

    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 192, Column 140: there is no attribute "onSubmit"
    ….com/login_func.php"  class="form" onSubmit="return validate_loginform(this);">

    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 202, Column 170: there is no attribute "width"
    …ff/public/images/login.gif" alt="Login" class="margin_left_5px" width="52px" />

    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 214, Column 61: value of attribute "valign" cannot be "center"; must be one of "top", "middle", "bottom", "baseline"
        <td height="28" colspan="2" align="right" valign="center" >

    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 242, Column 18: document type does not allow element "noscript" here
            <noscript>

    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 243, Column 24: document type does not allow element "tr" here; assuming missing "table" start-tag
            <tr class="bg3"><td height="28" colspan="2" align="center" valign="cent…
  • Error Line 243, Column 82: value of attribute "valign" cannot be "center"; must be one of "top", "middle", "bottom", "baseline"
    …span="2" align="center" valign="center" class="error_bold" >Please enable Java…

    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 243, Column 221: end tag for "table" omitted, but OMITTAG NO was specified
    …does not function properly without JavaScript enabled.</td></tr>    </noscript>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 243, Column 9: start tag was here
            <tr class="bg3"><td height="28" colspan="2" align="center" valign="cent…
  • Error Line 258, Column 16: there is no attribute "src"
        <embed src="http://pics.christiandatingforfree.com/cdff/public/images/home_…

    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 258, Column 103: there is no attribute "quality"
    …ic/images/home_animation.swf" quality="high" pluginspage="http://www.macromedi…

    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 258, Column 122: there is no attribute "pluginspage"
    …ation.swf" quality="high" pluginspage="http://www.macromedia.com/go/getflashpl…

    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 258, Column 173: there is no attribute "type"
    …acromedia.com/go/getflashplayer" type="application/x-shockwave-flash" width="4…

    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 258, Column 211: there is no attribute "width"
    …hplayer" type="application/x-shockwave-flash" width="445" height="325"></embed>

    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 258, Column 224: there is no attribute "height"
    …hplayer" type="application/x-shockwave-flash" width="445" height="325"></embed>

    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 258, Column 229: element "embed" undefined
    …hplayer" type="application/x-shockwave-flash" width="445" height="325"></embed>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. 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 "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 283, Column 59: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
                                        <td width="76" nowrap class="iam">

    "VI delimiter" is a technical term for the equal sign. This error message means that the name of an attribute and the equal sign cannot be omitted when specifying an attribute. A common cause for this error message is the use of "Attribute Minimization" in document types where it is not allowed, in XHTML for instance.

    How to fix: For attributes such as compact, checked or selected, do not write e.g <option selected ... but rather <option selected="selected" ...

  • Error Line 286, Column 48: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …                           <select id=u_gender name=u_gender class="txtfleid">…
  • Error Line 286, Column 62: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …             <select id=u_gender name=u_gender class="txtfleid"><option value=…
  • Error Line 294, Column 52: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …                           <select id=age_from name=age_from class="txtfleid w…
  • Error Line 294, Column 66: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …             <select id=age_from name=age_from class="txtfleid width_88px"><op…
  • Error Line 297, Column 52: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …                           <select id=age_to name=age_to class="txtfleid width…
  • Error Line 297, Column 64: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …               <select id=age_to name=age_to class="txtfleid width_88px"><opti…
  • Error Line 305, Column 203: there is no attribute "height"
    …ree.com/cdff/public/images/search_now.gif" alt="" width="96px" height="28px" />

    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 388, Column 172: end tag for "img" omitted, but OMITTAG NO was specified
    …p://pics.christiandatingforfree.com/cdff/public/images/online_today_small.gif">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 388, Column 73: start tag was here
    <img alt="" src="http://pics.christianda…
  • Error Line 414, Column 50: there is no attribute "height"
    …             <table width="90" height="90" border="0" cellpadding="0" cellspac…

    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 418, Column 264: end tag for "img" omitted, but OMITTAG NO was specified
    …28b2605b90.jpg.jpg" alt="" border="0" class="Below_are" width="75" height="75">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 418, Column 41: start tag was here
    <img src= "http://photos.christiandating…
  • Error Line 447, Column 172: end tag for "img" omitted, but OMITTAG NO was specified
    …p://pics.christiandatingforfree.com/cdff/public/images/online_today_small.gif">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 447, Column 73: start tag was here
    <img alt="" src="http://pics.christianda…
  • Warning Line 471, Column 113: unclosed start-tag requires SHORTTAG YES
    …- A follower of &quot;The Way&quot;.<br...                                </td>

    The construct <foo<bar> is valid in HTML (it is an example of the rather obscure “Shorttags” feature) but its use is not recommended. In most cases, this is a typo that you will want to fix. If you really want to use shorttags, be aware that they are not well implemented by browsers.

  • Error Line 471, Column 113: element "br..." undefined
    …- A follower of &quot;The Way&quot;.<br...                                </td>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. 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 "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 471, Column 117: end tag for "br..." omitted, but OMITTAG NO was specified
    …- A follower of &quot;The Way&quot;.<br...                                </td>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 471, Column 75: start tag was here
    …d - A follower of &quot;The Way&quot;.<br...                                </…
  • Error Line 480, Column 264: end tag for "img" omitted, but OMITTAG NO was specified
    …0dcd72e3f3.jpg.jpg" alt="" border="0" class="Below_are" width="75" height="75">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 480, Column 41: start tag was here
    <img src= "http://photos.christiandating…
  • Error Line 509, Column 172: end tag for "img" omitted, but OMITTAG NO was specified
    …p://pics.christiandatingforfree.com/cdff/public/images/online_today_small.gif">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 509, Column 73: start tag was here
    <img alt="" src="http://pics.christianda…
  • Error Line 537, Column 264: end tag for "img" omitted, but OMITTAG NO was specified
    …538c6526f1.jpg.jpg" alt="" border="0" class="Below_are" width="75" height="75">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 537, Column 41: start tag was here
    <img src= "http://photos.christiandating…
  • Error Line 566, Column 172: end tag for "img" omitted, but OMITTAG NO was specified
    …p://pics.christiandatingforfree.com/cdff/public/images/online_today_small.gif">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 566, Column 73: start tag was here
    <img alt="" src="http://pics.christianda…
  • Error Line 594, Column 264: end tag for "img" omitted, but OMITTAG NO was specified
    …84d8e49489.jpg.jpg" alt="" border="0" class="Below_are" width="75" height="75">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 594, Column 41: start tag was here
    <img src= "http://photos.christiandating…
  • Error Line 650, Column 264: end tag for "img" omitted, but OMITTAG NO was specified
    …0792606f74.jpg.jpg" alt="" border="0" class="Below_are" width="75" height="75">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 650, Column 41: start tag was here
    <img src= "http://photos.christiandating…
  • Error Line 706, Column 264: end tag for "img" omitted, but OMITTAG NO was specified
    …9c0b96502f.jpg.jpg" alt="" border="0" class="Below_are" width="75" height="75">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 706, Column 41: start tag was here
    <img src= "http://photos.christiandating…
  • Error Line 753, Column 133: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ic/images/smilies/icon_12.gif" border=0>  Just a sweet gal looking for love, l…
  • Error Line 753, Column 134: required attribute "alt" not specified
    …c/images/smilies/icon_12.gif" border=0>  Just a sweet gal looking for love, lo…

    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 753, Column 135: end tag for "img" omitted, but OMITTAG NO was specified
    …/images/smilies/icon_12.gif" border=0>  Just a sweet gal looking for love, lol…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 753, Column 37: start tag was here
                                        <img src="http://pics.christiandatingforfre…
  • Error Line 764, Column 264: end tag for "img" omitted, but OMITTAG NO was specified
    …2d81907c97.jpg.jpg" alt="" border="0" class="Below_are" width="75" height="75">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 764, Column 41: start tag was here
    <img src= "http://photos.christiandating…
  • Error Line 822, Column 266: end tag for "img" omitted, but OMITTAG NO was specified
    …bab9fd67.jpeg.jpeg" alt="" border="0" class="Below_are" width="75" height="75">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 822, Column 41: start tag was here
    <img src= "http://photos.christiandating…
  • Error Line 869, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …          <a class='arrow_link' href =http://www.christiandatingforfree.com/se…
  • Error Line 869, Column 76: NET-enabling start-tag not immediately followed by null end-tag
    …    <a class='arrow_link' href =http://www.christiandatingforfree.com/search/A…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 869, Column 138: end tag for element "a" which is not open
    …ree.com/search/Alabama.html>Alabama</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 871, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …          <a class='arrow_link' href =http://www.christiandatingforfree.com/se…
  • Error Line 871, Column 76: NET-enabling start-tag not immediately followed by null end-tag
    …    <a class='arrow_link' href =http://www.christiandatingforfree.com/search/A…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 871, Column 136: end tag for element "a" which is not open
    …rfree.com/search/Alaska.html>Alaska</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 873, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …          <a class='arrow_link' href =http://www.christiandatingforfree.com/se…
  • Error Line 873, Column 76: NET-enabling start-tag not immediately followed by null end-tag
    …    <a class='arrow_link' href =http://www.christiandatingforfree.com/search/A…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 873, Column 138: end tag for element "a" which is not open
    …ree.com/search/Arizona.html>Arizona</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 875, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …          <a class='arrow_link' href =http://www.christiandatingforfree.com/se…
  • Error Line 875, Column 76: NET-enabling start-tag not immediately followed by null end-tag
    …    <a class='arrow_link' href =http://www.christiandatingforfree.com/search/A…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 875, Column 140: end tag for element "a" which is not open
    …e.com/search/Arkansas.html>Arkansas</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 877, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …          <a class='arrow_link' href =http://www.christiandatingforfree.com/se…
  • Error Line 877, Column 76: NET-enabling start-tag not immediately followed by null end-tag
    …    <a class='arrow_link' href =http://www.christiandatingforfree.com/search/C…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 877, Column 144: end tag for element "a" which is not open
    …m/search/California.html>California</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 879, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …          <a class='arrow_link' href =http://www.christiandatingforfree.com/se…
  • Error Line 879, Column 76: NET-enabling start-tag not immediately followed by null end-tag
    …    <a class='arrow_link' href =http://www.christiandatingforfree.com/search/C…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 879, Column 140: end tag for element "a" which is not open
    …e.com/search/Colorado.html>Colorado</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 881, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …          <a class='arrow_link' href =http://www.christiandatingforfree.com/se…
  • Error Line 881, Column 76: NET-enabling start-tag not immediately followed by null end-tag
    …    <a class='arrow_link' href =http://www.christiandatingforfree.com/search/C…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 881, Column 146: end tag for element "a" which is not open
    …search/Connecticut.html>Connecticut</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 883, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …          <a class='arrow_link' href =http://www.christiandatingforfree.com/se…
  • Error Line 883, Column 76: NET-enabling start-tag not immediately followed by null end-tag
    …    <a class='arrow_link' href =http://www.christiandatingforfree.com/search/D…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 883, Column 140: end tag for element "a" which is not open
    …e.com/search/Delaware.html>Delaware</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 885, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …          <a class='arrow_link' href =http://www.christiandatingforfree.com/se…
  • Error Line 885, Column 76: NET-enabling start-tag not immediately followed by null end-tag
    …    <a class='arrow_link' href =http://www.christiandatingforfree.com/search/D…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 885, Column 164: end tag for element "a" which is not open
    …-Columbia.html>District of Columbia</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 887, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …          <a class='arrow_link' href =http://www.christiandatingforfree.com/se…
  • Error Line 887, Column 76: NET-enabling start-tag not immediately followed by null end-tag
    …    <a class='arrow_link' href =http://www.christiandatingforfree.com/search/F…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 887, Column 138: end tag for element "a" which is not open
    …ree.com/search/Florida.html>Florida</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 889, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …          <a class='arrow_link' href =http://www.christiandatingforfree.com/se…
  • Error Line 889, Column 76: NET-enabling start-tag not immediately followed by null end-tag
    …    <a class='arrow_link' href =http://www.christiandatingforfree.com/search/G…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 889, Column 138: end tag for element "a" which is not open
    …ree.com/search/Georgia.html>Georgia</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 891, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …          <a class='arrow_link' href =http://www.christiandatingforfree.com/se…
  • Error Line 891, Column 76: NET-enabling start-tag not immediately followed by null end-tag
    …    <a class='arrow_link' href =http://www.christiandatingforfree.com/search/H…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 891, Column 136: end tag for element "a" which is not open
    …rfree.com/search/Hawaii.html>Hawaii</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 893, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …          <a class='arrow_link' href =http://www.christiandatingforfree.com/se…
  • Error Line 893, Column 76: NET-enabling start-tag not immediately followed by null end-tag
    …    <a class='arrow_link' href =http://www.christiandatingforfree.com/search/I…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 893, Column 134: end tag for element "a" which is not open
    …forfree.com/search/Idaho.html>Idaho</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 895, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …          <a class='arrow_link' href =http://www.christiandatingforfree.com/se…
  • Error Line 895, Column 76: NET-enabling start-tag not immediately followed by null end-tag
    …    <a class='arrow_link' href =http://www.christiandatingforfree.com/search/I…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 895, Column 140: end tag for element "a" which is not open
    …e.com/search/Illinois.html>Illinois</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 897, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …          <a class='arrow_link' href =http://www.christiandatingforfree.com/se…
  • Error Line 897, Column 76: NET-enabling start-tag not immediately followed by null end-tag
    …    <a class='arrow_link' href =http://www.christiandatingforfree.com/search/I…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 897, Column 138: end tag for element "a" which is not open
    …ree.com/search/Indiana.html>Indiana</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 899, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …          <a class='arrow_link' href =http://www.christiandatingforfree.com/se…
  • Error Line 899, Column 76: NET-enabling start-tag not immediately followed by null end-tag
    …    <a class='arrow_link' href =http://www.christiandatingforfree.com/search/I…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 899, Column 132: end tag for element "a" which is not open
    …ngforfree.com/search/Iowa.html>Iowa</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 901, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …          <a class='arrow_link' href =http://www.christiandatingforfree.com/se…
  • Error Line 901, Column 76: NET-enabling start-tag not immediately followed by null end-tag
    …    <a class='arrow_link' href =http://www.christiandatingforfree.com/search/K…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 901, Column 136: end tag for element "a" which is not open
    …rfree.com/search/Kansas.html>Kansas</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 903, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …          <a class='arrow_link' href =http://www.christiandatingforfree.com/se…
  • Error Line 903, Column 76: NET-enabling start-tag not immediately followed by null end-tag
    …    <a class='arrow_link' href =http://www.christiandatingforfree.com/search/K…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 903, Column 140: end tag for element "a" which is not open
    …e.com/search/Kentucky.html>Kentucky</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 905, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …          <a class='arrow_link' href =http://www.christiandatingforfree.com/se…
  • Error Line 905, Column 76: NET-enabling start-tag not immediately followed by null end-tag
    …    <a class='arrow_link' href =http://www.christiandatingforfree.com/search/L…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 905, Column 142: end tag for element "a" which is not open
    …com/search/Louisiana.html>Louisiana</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 907, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …          <a class='arrow_link' href =http://www.christiandatingforfree.com/se…
  • Error Line 907, Column 76: NET-enabling start-tag not immediately followed by null end-tag
    …    <a class='arrow_link' href =http://www.christiandatingforfree.com/search/M…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 907, Column 134: end tag for element "a" which is not open
    …forfree.com/search/Maine.html>Maine</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 909, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …          <a class='arrow_link' href =http://www.christiandatingforfree.com/se…
  • Error Line 909, Column 76: NET-enabling start-tag not immediately followed by null end-tag
    …    <a class='arrow_link' href =http://www.christiandatingforfree.com/search/M…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 909, Column 140: end tag for element "a" which is not open
    …e.com/search/Maryland.html>Maryland</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 911, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …          <a class='arrow_link' href =http://www.christiandatingforfree.com/se…
  • Error Line 911, Column 76: NET-enabling start-tag not immediately followed by null end-tag
    …    <a class='arrow_link' href =http://www.christiandatingforfree.com/search/M…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 911, Column 150: end tag for element "a" which is not open
    …ch/Massachusetts.html>Massachusetts</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 913, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …          <a class='arrow_link' href =http://www.christiandatingforfree.com/se…
  • Error Line 913, Column 76: NET-enabling start-tag not immediately followed by null end-tag
    …    <a class='arrow_link' href =http://www.christiandatingforfree.com/search/M…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 913, Column 140: end tag for element "a" which is not open
    …e.com/search/Michigan.html>Michigan</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 915, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …          <a class='arrow_link' href =http://www.christiandatingforfree.com/se…
  • Error Line 915, Column 76: NET-enabling start-tag not immediately followed by null end-tag
    …    <a class='arrow_link' href =http://www.christiandatingforfree.com/search/M…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 915, Column 142: end tag for element "a" which is not open
    …com/search/Minnesota.html>Minnesota</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 917, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …          <a class='arrow_link' href =http://www.christiandatingforfree.com/se…
  • Error Line 917, Column 76: NET-enabling start-tag not immediately followed by null end-tag
    …    <a class='arrow_link' href =http://www.christiandatingforfree.com/search/M…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 917, Column 146: end tag for element "a" which is not open
    …search/Mississippi.html>Mississippi</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 919, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …          <a class='arrow_link' href =http://www.christiandatingforfree.com/se…
  • Error Line 919, Column 76: NET-enabling start-tag not immediately followed by null end-tag
    …    <a class='arrow_link' href =http://www.christiandatingforfree.com/search/M…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 919, Column 140: end tag for element "a" which is not open
    …e.com/search/Missouri.html>Missouri</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 921, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …          <a class='arrow_link' href =http://www.christiandatingforfree.com/se…
  • Error Line 921, Column 76: NET-enabling start-tag not immediately followed by null end-tag
    …    <a class='arrow_link' href =http://www.christiandatingforfree.com/search/M…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 921, Column 138: end tag for element "a" which is not open
    …ree.com/search/Montana.html>Montana</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 923, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …          <a class='arrow_link' href =http://www.christiandatingforfree.com/se…
  • Error Line 923, Column 76: NET-enabling start-tag not immediately followed by null end-tag
    …    <a class='arrow_link' href =http://www.christiandatingforfree.com/search/N…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 923, Column 140: end tag for element "a" which is not open
    …e.com/search/Nebraska.html>Nebraska</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 925, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …          <a class='arrow_link' href =http://www.christiandatingforfree.com/se…
  • Error Line 925, Column 76: NET-enabling start-tag not immediately followed by null end-tag
    …    <a class='arrow_link' href =http://www.christiandatingforfree.com/search/N…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 925, Column 136: end tag for element "a" which is not open
    …rfree.com/search/Nevada.html>Nevada</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 927, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …          <a class='arrow_link' href =http://www.christiandatingforfree.com/se…
  • Error Line 927, Column 76: NET-enabling start-tag not immediately followed by null end-tag
    …    <a class='arrow_link' href =http://www.christiandatingforfree.com/search/N…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 927, Column 150: end tag for element "a" which is not open
    …ch/New-Hampshire.html>New Hampshire</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 929, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …          <a class='arrow_link' href =http://www.christiandatingforfree.com/se…
  • Error Line 929, Column 76: NET-enabling start-tag not immediately followed by null end-tag
    …    <a class='arrow_link' href =http://www.christiandatingforfree.com/search/N…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 929, Column 144: end tag for element "a" which is not open
    …m/search/New-Jersey.html>New Jersey</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 931, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …          <a class='arrow_link' href =http://www.christiandatingforfree.com/se…
  • Error Line 931, Column 76: NET-enabling start-tag not immediately followed by null end-tag
    …    <a class='arrow_link' href =http://www.christiandatingforfree.com/search/N…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 931, Column 144: end tag for element "a" which is not open
    …m/search/New-Mexico.html>New Mexico</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 933, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …          <a class='arrow_link' href =http://www.christiandatingforfree.com/se…
  • Error Line 933, Column 76: NET-enabling start-tag not immediately followed by null end-tag
    …    <a class='arrow_link' href =http://www.christiandatingforfree.com/search/N…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 933, Column 140: end tag for element "a" which is not open
    …e.com/search/New-York.html>New York</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 935, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …          <a class='arrow_link' href =http://www.christiandatingforfree.com/se…
  • Error Line 935, Column 76: NET-enabling start-tag not immediately followed by null end-tag
    …    <a class='arrow_link' href =http://www.christiandatingforfree.com/search/N…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 935, Column 152: end tag for element "a" which is not open
    …/North-Carolina.html>North Carolina</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 937, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …          <a class='arrow_link' href =http://www.christiandatingforfree.com/se…
  • Error Line 937, Column 76: NET-enabling start-tag not immediately followed by null end-tag
    …    <a class='arrow_link' href =http://www.christiandatingforfree.com/search/N…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 937, Column 148: end tag for element "a" which is not open
    …arch/North-Dakota.html>North Dakota</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 939, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …          <a class='arrow_link' href =http://www.christiandatingforfree.com/se…
  • Error Line 939, Column 76: NET-enabling start-tag not immediately followed by null end-tag
    …    <a class='arrow_link' href =http://www.christiandatingforfree.com/search/O…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 939, Column 132: end tag for element "a" which is not open
    …ngforfree.com/search/Ohio.html>Ohio</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 941, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …          <a class='arrow_link' href =http://www.christiandatingforfree.com/se…
  • Error Line 941, Column 76: NET-enabling start-tag not immediately followed by null end-tag
    …    <a class='arrow_link' href =http://www.christiandatingforfree.com/search/O…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 941, Column 140: end tag for element "a" which is not open
    …e.com/search/Oklahoma.html>Oklahoma</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 943, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …          <a class='arrow_link' href =http://www.christiandatingforfree.com/se…
  • Error Line 943, Column 76: NET-enabling start-tag not immediately followed by null end-tag
    …    <a class='arrow_link' href =http://www.christiandatingforfree.com/search/O…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 943, Column 136: end tag for element "a" which is not open
    …rfree.com/search/Oregon.html>Oregon</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 945, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …          <a class='arrow_link' href =http://www.christiandatingforfree.com/se…
  • Error Line 945, Column 76: NET-enabling start-tag not immediately followed by null end-tag
    …    <a class='arrow_link' href =http://www.christiandatingforfree.com/search/P…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 945, Column 148: end tag for element "a" which is not open
    …arch/Pennsylvania.html>Pennsylvania</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 947, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …          <a class='arrow_link' href =http://www.christiandatingforfree.com/se…
  • Error Line 947, Column 76: NET-enabling start-tag not immediately followed by null end-tag
    …    <a class='arrow_link' href =http://www.christiandatingforfree.com/search/R…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 947, Column 148: end tag for element "a" which is not open
    …arch/Rhode-Island.html>Rhode Island</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 949, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …          <a class='arrow_link' href =http://www.christiandatingforfree.com/se…
  • Error Line 949, Column 76: NET-enabling start-tag not immediately followed by null end-tag
    …    <a class='arrow_link' href =http://www.christiandatingforfree.com/search/S…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 949, Column 152: end tag for element "a" which is not open
    …/South-Carolina.html>South Carolina</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 951, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …          <a class='arrow_link' href =http://www.christiandatingforfree.com/se…
  • Error Line 951, Column 76: NET-enabling start-tag not immediately followed by null end-tag
    …    <a class='arrow_link' href =http://www.christiandatingforfree.com/search/S…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 951, Column 148: end tag for element "a" which is not open
    …arch/South-Dakota.html>South Dakota</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 953, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …          <a class='arrow_link' href =http://www.christiandatingforfree.com/se…
  • Error Line 953, Column 76: NET-enabling start-tag not immediately followed by null end-tag
    …    <a class='arrow_link' href =http://www.christiandatingforfree.com/search/T…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 953, Column 142: end tag for element "a" which is not open
    …com/search/Tennessee.html>Tennessee</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 955, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …          <a class='arrow_link' href =http://www.christiandatingforfree.com/se…
  • Error Line 955, Column 76: NET-enabling start-tag not immediately followed by null end-tag
    …    <a class='arrow_link' href =http://www.christiandatingforfree.com/search/T…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 955, Column 134: end tag for element "a" which is not open
    …forfree.com/search/Texas.html>Texas</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 957, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …          <a class='arrow_link' href =http://www.christiandatingforfree.com/se…
  • Error Line 957, Column 76: NET-enabling start-tag not immediately followed by null end-tag
    …    <a class='arrow_link' href =http://www.christiandatingforfree.com/search/U…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 957, Column 132: end tag for element "a" which is not open
    …ngforfree.com/search/Utah.html>Utah</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 959, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …          <a class='arrow_link' href =http://www.christiandatingforfree.com/se…
  • Error Line 959, Column 76: NET-enabling start-tag not immediately followed by null end-tag
    …    <a class='arrow_link' href =http://www.christiandatingforfree.com/search/V…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 959, Column 138: end tag for element "a" which is not open
    …ree.com/search/Vermont.html>Vermont</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 961, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …          <a class='arrow_link' href =http://www.christiandatingforfree.com/se…
  • Error Line 961, Column 76: NET-enabling start-tag not immediately followed by null end-tag
    …    <a class='arrow_link' href =http://www.christiandatingforfree.com/search/V…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 961, Column 140: end tag for element "a" which is not open
    …e.com/search/Virginia.html>Virginia</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 963, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …          <a class='arrow_link' href =http://www.christiandatingforfree.com/se…
  • Error Line 963, Column 76: NET-enabling start-tag not immediately followed by null end-tag
    …    <a class='arrow_link' href =http://www.christiandatingforfree.com/search/W…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 963, Column 144: end tag for element "a" which is not open
    …m/search/Washington.html>Washington</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 965, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …          <a class='arrow_link' href =http://www.christiandatingforfree.com/se…
  • Error Line 965, Column 76: NET-enabling start-tag not immediately followed by null end-tag
    …    <a class='arrow_link' href =http://www.christiandatingforfree.com/search/W…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 965, Column 150: end tag for element "a" which is not open
    …ch/West-Virginia.html>West Virginia</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 967, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …          <a class='arrow_link' href =http://www.christiandatingforfree.com/se…
  • Error Line 967, Column 76: NET-enabling start-tag not immediately followed by null end-tag
    …    <a class='arrow_link' href =http://www.christiandatingforfree.com/search/W…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 967, Column 142: end tag for element "a" which is not open
    …com/search/Wisconsin.html>Wisconsin</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 969, Column 70: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …          <a class='arrow_link' href =http://www.christiandatingforfree.com/se…
  • Error Line 969, Column 76: NET-enabling start-tag not immediately followed by null end-tag
    …    <a class='arrow_link' href =http://www.christiandatingforfree.com/search/W…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 969, Column 138: end tag for element "a" which is not open
    …ree.com/search/Wyoming.html>Wyoming</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 1005, Column 173: required attribute "alt" not specified
    …tingforfree.com/cdff/public/images/spacer.gif" width="1px" height="1px" /></td>

    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 1011, Column 81: document type does not allow element "script" here
    …                          <script type="text/javascript" language="javascript">

    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 1052, Column 31: required attribute "type" not specified
    <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>.

  • Warning Line 1056, Column 15: character "<" is the first character of a delimiter but occurred as data
    	for(i = 0; i < str.length; i++){

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.

Visitor Analysis

Daily Visitor
  • 2.917 visits

In Page Analysis