americanpregnancy.org

americanpregnancy.org has Alexa Rank 32.186 and Google Page Rank is 6

Display Widget for this domain on your website. Click Here
This data was last updated from 15-09-2013 12:59:32  (update).

Overview Info

  • Domain Name
    americanpregnancy.org
  • Favicon
  • Alexa Rank
    #32186
  • Google Page Rank
    PR 6
  • Ip Address
    50.23.38.93
  • Page Size
    53.6 KB
  • Images
    2 GIF, 0 JPG, 13 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 1 7 2 0 0

Website Meta Analysis



  • Meta Keyword

Technical Analysis



  • Webserver
    Apache/2.0.64 (Unix) mod_ssl/2.0.64 OpenSSL/0.9.8e-fips-rhel5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 PHP/5.3.25
  • Ip Address
    50.23.38.93
  • Domain Age
  • Javascript Library
    jquery, yui
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from americanpregnancy.org.

HTML Analysis

  • date: Sun, 15 Sep 2013 12:20:11 GMT
  • server: Apache/2.0.64 (Unix) mod_ssl/2.0.64 OpenSSL/0.9.8e-fips-rhel5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 PHP/5.3.25
  • x-powered-by: PHP/5.3.25
  • x-pingback: http://americanpregnancy.org/xmlrpc.php
  • x-ua-compatible: IE=edge
  • connection: close
  • content-type: text/html; charset=UTF-8
  • content-length: 59787
  • age: 2358
  • x-google-cache-control: remote-cache-hit
  • via: HTTP/1.1 GWA (remote cache hit)
Domain ID:D96677076-LROR
Domain Domain Name:AMERICANPREGNANCY.ORG
Created:28-Mar-2003 03:52:27 UTC
Updated:20-Dec-2009 05:13:32 UTC
Expires:28-Mar-2018 03:52:27 UTC
Registrar:GoDaddy.com, Inc. (R91-LROR)
Domain Status:CLIENT DELETE PROHIBITED
Domain Status:CLIENT RENEW PROHIBITED
Domain Status:CLIENT TRANSFER PROHIBITED
Domain Status:CLIENT UPDATE PROHIBITED
Registrant ID:CR38612840
Registrant Domain Name:Registration Private
Registrant Organization:Domains By Proxy, LLC
Registrant Street1:DomainsByProxy.com
Registrant Street2:15111 N. Hayden Rd., Ste 160, PMB 353
Registrant Street3:
Registrant City:Scottsdale
Registrant State/Province:Arizona
Registrant Postal Code:85260
Registrant Country:US
Registrant Phone:+1.4806242599
Registrant Phone Ext.:
Registrant FAX:+1.4806242598
Registrant FAX Ext.:
Registrant Email: email
Admin ID:CR38612842
Admin Domain Name:Registration Private
Admin Organization:Domains By Proxy, LLC
Admin Street1:DomainsByProxy.com
Admin Street2:15111 N. Hayden Rd., Ste 160, PMB 353
Admin Street3:
Admin City:Scottsdale
Admin State/Province:Arizona
Admin Postal Code:85260
Admin Country:US
Admin Phone:+1.4806242599
Admin Phone Ext.:
Admin FAX:+1.4806242598
Admin FAX Ext.:
Admin Email: email
Tech ID:CR38612841
Tech Domain Name:Registration Private
Tech Organization:Domains By Proxy, LLC
Tech Street1:DomainsByProxy.com
Tech Street2:15111 N. Hayden Rd., Ste 160, PMB 353
Tech Street3:
Tech City:Scottsdale
Tech State/Province:Arizona
Tech Postal Code:85260
Tech Country:US
Tech Phone:+1.4806242599
Tech Phone Ext.:
Tech FAX:+1.4806242598
Tech FAX Ext.:
Tech Email: email
Name Servers:NS1.THEPLANET.COM
Name Servers:NS2.THEPLANET.COM
Name Servers:
Name Servers:
Name Servers:
Name Servers:
Name Servers:
Name Servers:
Name Servers:
Name Servers:
Name Servers:
Name Servers:
Name Servers:
DNSSEC:Unsigned

0

DNS Analysis


DNS servers
ns1.theplanet.com [207.218.247.135]
ns2.theplanet.com [207.218.223.162]


DNS Records

Answer records
americanpregnancy.org SOA
server: ns1.theplanet.com
email: root@theplanet.com
serial: 2011021702
refresh: 7200
retry: 600
expire: 1728000
minimum ttl: 43200
86400s
americanpregnancy.org NS  ns1.theplanet.com 86400s
americanpregnancy.org NS  ns2.theplanet.com 86400s
americanpregnancy.org A 209.62.118.66 86400s
americanpregnancy.org MX
preference: 10
exchange: mail.americanpregnancy.org
86400s
americanpregnancy.org TXT v=spf1 a mx ~all 86400s

Authority records

Additional records
ns1.theplanet.com A 207.218.247.135 86400s
ns1.theplanet.com 28 [16 bytes] 600s
ns2.theplanet.com A 207.218.223.162 86400s
ns2.theplanet.com 28 [16 bytes] 600s
mail.americanpregnancy.org A 209.62.118.66 86400s

IP 50.23.38.93 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 18 Errors
  • 17 Warnings
Ratio Text/Html
  • 0.792967185052992
Message Error
  • Error Line 13, Column 18: there is no attribute "property"
      <meta property="og:type" content="non_profit" />

    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 55, Column 81: document type does not allow element "div" here
    …Query( '#loopedSlider .pagination' ).wrap( '<div class="pagination-wrap" />' );

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Warning Line 109, Column 49: cannot generate system identifier for general entity "subject"
    …ail.href = "mailto:?body="+location.href+"&subject=American Pregnancy Article";

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 109, Column 49: general entity "subject" not defined and no default entity
    …ail.href = "mailto:?body="+location.href+"&subject=American Pregnancy Article";

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 109, Column 56: reference not terminated by REFC delimiter
    …ail.href = "mailto:?body="+location.href+"&subject=American Pregnancy Article";

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Error Line 109, Column 56: reference to entity "subject" for which no system identifier could be generated
    …ail.href = "mailto:?body="+location.href+"&subject=American Pregnancy Article";

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 109, Column 48: entity was defined here
    …ail.href = "mailto:?body="+location.href+"&subject=American Pregnancy Article";
  • Error Line 113, Column 29: document type does not allow element "br" here
    			tools.innerHTML += '<br /><a href="#" title="Print this article" id="article…

    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 113, Column 87: document type does not allow element "a" here
    …+= '<br /><a href="#" title="Print this article" id="article-print">Print</a>';

    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 149, Column 8: required attribute "type" not specified
    <script>(function(d, s, id) {

    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 153, Column 57: cannot generate system identifier for general entity "appId"
      js.src = "//connect.facebook.net/en_US/all.js#xfbml=1&appId=167247666684444";

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 153, Column 57: general entity "appId" not defined and no default entity
      js.src = "//connect.facebook.net/en_US/all.js#xfbml=1&appId=167247666684444";

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 153, Column 62: reference not terminated by REFC delimiter
      js.src = "//connect.facebook.net/en_US/all.js#xfbml=1&appId=167247666684444";

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Error Line 153, Column 62: reference to entity "appId" for which no system identifier could be generated
      js.src = "//connect.facebook.net/en_US/all.js#xfbml=1&appId=167247666684444";

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 153, Column 56: entity was defined here
      js.src = "//connect.facebook.net/en_US/all.js#xfbml=1&appId=167247666684444";
  • Error Line 160, Column 92: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …pe="hidden" name="redirect" value="http://www.americanpregnancy.org/index.htm">

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 160, Column 93: end tag for "input" omitted, but OMITTAG NO was specified
    …pe="hidden" name="redirect" value="http://www.americanpregnancy.org/index.htm">

    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 160, Column 5: start tag was here
    				<input type="hidden" name="redirect" value="http://www.americanpregnancy.or…
  • Error Line 167, Column 100: end tag for "input" omitted, but OMITTAG NO was specified
    …rname" name="login[username]" type="text" tabindex="1" value="" maxlength="50">

    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 167, Column 7: start tag was here
    						<input id="username" name="login[username]" type="text" tabindex="1" valu…
  • Error Line 172, Column 104: end tag for "input" omitted, but OMITTAG NO was specified
    …d" name="login[password]" type="password" tabindex="2" value="" maxlength="12">

    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 172, Column 7: start tag was here
    						<input id="password" name="login[password]" type="password" tabindex="2" …
  • Error Line 173, Column 82: end tag for "input" omitted, but OMITTAG NO was specified
    …			<input type="submit" value="Login" name="submit" id="submit" class="button">

    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 173, Column 6: start tag was here
    					<input type="submit" value="Login" name="submit" id="submit" class="button…
  • Error Line 212, Column 166: there is no attribute "target"
    …mily;sz=728x90;ord=123456789?" target="_blank" ><img src="http://ad.doubleclic…

    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 212, Column 175: document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …28x90;ord=123456789?" target="_blank" ><img src="http://ad.doubleclick.net/N61…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 212, Column 289: there is no attribute "border"
    …;!c=ae-non-family;sz=728x90;ord=123456789?" border="0" alt="" /></a></noscript>

    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 223, Column 88: there is no attribute "placeholder"
    …fdse_TermsEx" type="text" placeholder="Search" /><input type="hidden" accesske…

    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 492, Column 176: document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …0x250;ord=123456789?" target="_blank" ><img src="http://ad.doubleclick.net/N61…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 505, Column 81: there is no attribute "onClick"
    …rg/getting-pregnant/?ebook=a" onClick="_gaq.push(['_trackEvent', 'MainSiteAD',…

    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 553, Column 170: end tag for "img" omitted, but OMITTAG NO was specified
    …<img src="/images/homelogos/ddc-homepage.gif" alt="DNA Diagnostics Center"></a>

    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 553, Column 92: start tag was here
    …ors/sponsors/dna-diagnostics-center/"><img src="/images/homelogos/ddc-homepage…
  • Error Line 556, Column 152: end tag for "img" omitted, but OMITTAG NO was specified
    …naturals/"><img src="/images/homelogos/NNlogo2.png"  alt="Nordic Naturals"></a>

    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 556, Column 85: start tag was here
    …p-sponsors/sponsors/nordic-naturals/"><img src="/images/homelogos/NNlogo2.png"…
  • Error Line 561, Column 145: end tag for "img" omitted, but OMITTAG NO was specified
    …viacord/"><img src="/images/homelogos/viacord-homepage.png"  alt="Viacord"></a>

    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 561, Column 77: start tag was here
    ….org/corp-sponsors/sponsors/viacord/"><img src="/images/homelogos/viacord-home…
  • Error Line 564, Column 145: end tag for "img" omitted, but OMITTAG NO was specified
    …vitalah/"><img src="/images/homelogos/vitalah-homepage.png"  alt="Vitalah"></a>

    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 564, Column 77: start tag was here
    ….org/corp-sponsors/sponsors/vitalah/"><img src="/images/homelogos/vitalah-home…
  • Error Line 569, Column 158: end tag for "img" omitted, but OMITTAG NO was specified
    …lth/"><img src="/images/homelogos/fh-fertility.png" alt="Fairhaven Health"></a>

    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 569, Column 86: start tag was here
    …-sponsors/sponsors/fairhaven-health/"><img src="/images/homelogos/fh-fertility…
  • Error Line 574, Column 151: end tag for "img" omitted, but OMITTAG NO was specified
    …elly/"><img src="/images/homelogos/dreambelly-butter.png" alt="DreamBelly"></a>

    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 574, Column 80: start tag was here
    …g/corp-sponsors/sponsors/dreambelly/"><img src="/images/homelogos/dreambelly-b…
  • Error Line 579, Column 181: end tag for "img" omitted, but OMITTAG NO was specified
    …melogos/nb-breastfeeding.png" alt="Nursing Blend Breastfeeding Supplement"></a>

    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 579, Column 83: start tag was here
    …orp-sponsors/sponsors/nursing-blend/"><img src="/images/homelogos/nb-breastfee…
  • Error Line 611, Column 55: document type does not allow element "div" here
    	 	$("#wrapper").prepend('<div id="fb-like-positioner"></div>');

    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 612, Column 65: document type does not allow element "div" here
    …).prepend('<div id="fb-like-container"><fb:like href="http://americanpregnancy…

    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 612, Column 80: there is no attribute "href"
    … id="fb-like-container"><fb:like href="http://americanpregnancy.org" send="fal…

    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 612, Column 116: there is no attribute "send"
    …f="http://americanpregnancy.org" send="false" layout="button_count" width="250…

    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 612, Column 131: there is no attribute "layout"
    …canpregnancy.org" send="false" layout="button_count" width="250" show_faces="f…

    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 612, Column 152: there is no attribute "width"
    …d="false" layout="button_count" width="250" show_faces="false"></fb:like></div…

    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 612, Column 169: there is no attribute "show_faces"
    …false" layout="button_count" width="250" show_faces="false"></fb:like></div>');

    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 612, Column 176: element "fb:like" undefined
    …false" layout="button_count" width="250" show_faces="false"></fb:like></div>');

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

Visitor Analysis

Daily Visitor
  • 5.250 visits

In Page Analysis