bear411.com

FREE, Bear, profiles, chat, cam. Hottest Gay Bears in London, San Francisco, Bay Area, NYC, New York City, Montreal, Dallas, Chicago, Atlanta, Toronto, Los Angeles, Houston, Fort Lauderdale, Seattle, San Diego, Portland, Austin, ...

Display Widget for this domain on your website. Click Here
This data was last updated from 25-06-2013 09:45:38  (update).

Overview Info

  • Domain Name
    bear411.com
  • Favicon
  • Alexa Rank
    #20776
  • Google Page Rank
    PR 4
  • Ip Address
    69.90.9.175
  • Page Size
    3.6 KB
  • Images
    0 GIF, 0 JPG, 0 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 0 0 0 0 0

Website Meta Analysis



  • Title
    BEAR411.com - The #1 Bear Site !
  • Meta Description
    FREE, Bear, profiles, chat, cam. Hottest Gay Bears in London, San Francisco, Bay Area, NYC, New York City, Montreal, Dallas, Chicago, Atlanta, Toronto, Los Angeles, Houston, Fort Lauderdale, Seattle, San Diego, Portland, Austin, Phoenix, Manchester, Orlando, Columbus, Madrid, Denver, Paris, Berlin, Barcelona, Milan, Philadelphia, Washington D.C., Las Vegas, Palm Springs, Miami, Indianapolis, Vancouver

Technical Analysis



  • Webserver
    Apache/2.2.3 (CentOS)
  • Ip Address
    69.90.9.175
  • Domain Age
    13 Years, 7 Months, 14 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Tue, 25 Jun 2013 21:45:35 GMT
  • server: Apache/2.2.3 (CentOS)
  • x-powered-by: PHP/5.1.6
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • last-modified: Tue, 25 Jun 2013 21:45:35 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • content-encoding: gzip
  • vary: Accept-Encoding
  • content-length: 1445
  • connection: close
  • content-type: text/html; charset=iso-8859-1
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
WebID Consulting
ATTN BEAR411.COM
care of Network Solutions
PO Box 459
Drums, PA. US 18222


Domain Name: BEAR411.COM



Administrative Contact, Technical Contact:
WebID Consulting email
ATTN BEAR411.COM
care of Network Solutions
PO Box 459
Drums, PA 18222
US
570-708-8780


Record expires on 22-Nov-2015.
Record created on 22-Nov-1999.
Database last updated on 2-Dec-2012 20:16:01 EST.

Domain servers in listed order:

DNS1.WEBID-CONSULTING.COM 69.90.9.138
DNS2.WEBID-CONSULTING.COM 69.90.9.139

DNS Analysis


DNS servers
dns1.webid-consulting.com [69.90.9.138]
dns2.webid-consulting.com [69.90.9.139]


DNS Records

Answer records
bear411.com TXT v=spf1 a mx ip4:69.90.9.133 ip4:69.90.9.134 ip4:69.90.9.135 ip4:69.90.9.136 ip4:69.90.9.137 ip4:69.90.9.204 ip4:69.90.9.207 ip4:69.90.9.244 ip4:66.199.152.206 ip4:66.199.152.220 ip4:69.90.80.84 -all 86400s
bear411.com MX
preference: 10
exchange: sitemail.everyone.net
86400s
bear411.com A 69.90.9.175 86400s
bear411.com SOA
server: ns1.bear411.com
email: webmaster@bear411.com
serial: 1033257655
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 86400
86400s
bear411.com NS  ns2.bear411.com 86400s
bear411.com NS  ns1.bear411.com 86400s

Authority records

Additional records
ns1.bear411.com A 69.90.9.138 86400s
ns2.bear411.com A 69.90.9.139 86400s

IP 69.90.9.175 Analysis

  • Country Code
    CA
  • Country Code3
    CAN
  • Country Name
    Canada
  • City
    Vaudreuil
  • Continent Code
    j7v2e6
  • Latitude
  • Longitude
    45.4.
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 69.90.9.175"
    #
    # Use "?" to get help.
    #

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

    Peer 1 Network Inc. PEER1-BINARY-11 (NET-69-90-0-0-1) 69.90.0.0 - 69.90.255.255
    Metro Optic PEER1-METROOPTIC-15 (NET-69-90-9-0-1) 69.90.9.0 - 69.90.9.255


    #
    # ARIN WHOIS data and services are subject to the Terms of Use
    # available at: https://www.arin.net/whois_tou.html
    #

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 84 Errors
  • 7 Warnings
Ratio Text/Html
  • 0.7059791552386177
Message Error
  • Error Line 2, Column 2: Missing xmlns attribute for element html. The value should be: http://www.w3.org/1999/xhtml
     <html><head>

    Many Document Types based on XML need a mandatory xmlns attribute on the root element. For example, the root element for XHTML might look like:
    <html xmlns="http://www.w3.org/1999/xhtml">

  • Error Line 3, Column 8: element "TITLE" undefined
     <TITLE>

    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 5, Column 56: end tag for "link" omitted, but OMITTAG NO was specified
     <link rel="icon" type="image/ico" href="favicon.ico?"> 

    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 5, Column 2: start tag was here
     <link rel="icon" type="image/ico" href="favicon.ico?"> 
  • Error Line 6, Column 47: end tag for "link" omitted, but OMITTAG NO was specified
    <link rel="shortcut icon" href="favicon.ico?"> 

    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 6, Column 1: start tag was here
    <link rel="shortcut icon" href="favicon.ico?"> 
  • Error Line 7, Column 134: end tag for "meta" omitted, but OMITTAG NO was specified
    …ng' />	<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">

    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 7, Column 62: start tag was here
    …-icon' href='apple-touch-icon.png' />	<meta http-equiv="Content-Type" content=…
  • Error Line 8, Column 442: end tag for "meta" omitted, but OMITTAG NO was specified
    …hia, Washington D.C., Las Vegas, Palm Springs, Miami, Indianapolis, Vancouver">

    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 8, Column 2: start tag was here
    	<meta name="Description" content="FREE, Bear, profiles, chat, cam. Hottest Gay…
  • Error Line 9, Column 557: end tag for "meta" omitted, but OMITTAG NO was specified
    …hia, Washington D.C., Las Vegas, Palm Springs, Miami, Indianapolis, Vancouver">

    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 9, Column 2: start tag was here
    	<meta name="Keywords" content="bear, profiles, chat, hairy, musclebear, gay, w…
  • Error Line 21, Column 9: end tag for "head" which is not finished
    		</head>

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Error Line 22, Column 17: there is no attribute "cols"
    	<frameset cols='*,845,*' border=0>

    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 22, Column 34: there is no attribute "border"
    	<frameset cols='*,845,*' border=0>

    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 22, Column 34: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    	<frameset cols='*,845,*' border=0>
  • Error Line 22, Column 35: element "frameset" undefined
    	<frameset cols='*,845,*' border=0>

    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 23, Column 12: there is no attribute "src"
    <frame src='http://www.bear411.com/bgframe.html' scrollbars=no scrolling=no  ma…

    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 23, Column 61: there is no attribute "scrollbars"
    ….bear411.com/bgframe.html' scrollbars=no scrolling=no  marginwidth=0 marginhei…

    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 23, Column 61: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    ….bear411.com/bgframe.html' scrollbars=no scrolling=no  marginwidth=0 marginhei…
  • Error Line 23, Column 74: there is no attribute "scrolling"
    …bgframe.html' scrollbars=no scrolling=no  marginwidth=0 marginheight=0 framesp…

    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 23, Column 74: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …bgframe.html' scrollbars=no scrolling=no  marginwidth=0 marginheight=0 framesp…
  • Error Line 23, Column 90: there is no attribute "marginwidth"
    …rollbars=no scrolling=no  marginwidth=0 marginheight=0 framespacing=0 framebor…

    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 23, Column 90: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rollbars=no scrolling=no  marginwidth=0 marginheight=0 framespacing=0 framebor…
  • Error Line 23, Column 105: there is no attribute "marginheight"
    …olling=no  marginwidth=0 marginheight=0 framespacing=0 frameborder=no border=0…

    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 23, Column 105: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …olling=no  marginwidth=0 marginheight=0 framespacing=0 frameborder=no border=0…
  • Error Line 23, Column 120: there is no attribute "framespacing"
    …olling=no  marginwidth=0 marginheight=0 framespacing=0 frameborder=no border=0>

    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 23, Column 120: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …olling=no  marginwidth=0 marginheight=0 framespacing=0 frameborder=no border=0>
  • Error Line 23, Column 134: there is no attribute "frameborder"
    …olling=no  marginwidth=0 marginheight=0 framespacing=0 frameborder=no border=0>

    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 23, Column 134: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …olling=no  marginwidth=0 marginheight=0 framespacing=0 frameborder=no border=0>
  • Error Line 23, Column 144: there is no attribute "border"
    …olling=no  marginwidth=0 marginheight=0 framespacing=0 frameborder=no border=0>

    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 23, Column 144: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …olling=no  marginwidth=0 marginheight=0 framespacing=0 frameborder=no border=0>
  • Error Line 23, Column 145: element "frame" undefined
    …olling=no  marginwidth=0 marginheight=0 framespacing=0 frameborder=no border=0>

    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 24, Column 16: there is no attribute "rows"
    <frameset rows='101,20,*,10' marginwidth=0 marginheight=0 framespacing=0 frameb…

    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 24, Column 42: there is no attribute "marginwidth"
    …ameset rows='101,20,*,10' marginwidth=0 marginheight=0 framespacing=0 framebor…

    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 24, Column 42: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ameset rows='101,20,*,10' marginwidth=0 marginheight=0 framespacing=0 framebor…
  • Error Line 24, Column 57: there is no attribute "marginheight"
    …1,20,*,10' marginwidth=0 marginheight=0 framespacing=0 frameborder=no border=0…

    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 24, Column 57: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …1,20,*,10' marginwidth=0 marginheight=0 framespacing=0 frameborder=no border=0…
  • Error Line 24, Column 72: there is no attribute "framespacing"
    …1,20,*,10' marginwidth=0 marginheight=0 framespacing=0 frameborder=no border=0>

    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 24, Column 72: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …1,20,*,10' marginwidth=0 marginheight=0 framespacing=0 frameborder=no border=0>
  • Error Line 24, Column 86: there is no attribute "frameborder"
    …1,20,*,10' marginwidth=0 marginheight=0 framespacing=0 frameborder=no border=0>

    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 24, Column 86: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …1,20,*,10' marginwidth=0 marginheight=0 framespacing=0 frameborder=no border=0>
  • Error Line 24, Column 96: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …1,20,*,10' marginwidth=0 marginheight=0 framespacing=0 frameborder=no border=0>
  • Error Line 24, Column 97: element "frameset" undefined
    …1,20,*,10' marginwidth=0 marginheight=0 framespacing=0 frameborder=no border=0>

    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 25, Column 16: there is no attribute "ROWS"
    <frameset ROWS='75,26' marginwidth=0 marginheight=0 framespacing=0 frameborder=…

    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 25, Column 36: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <frameset ROWS='75,26' marginwidth=0 marginheight=0 framespacing=0 frameborder=…
  • Error Line 25, Column 51: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …WS='75,26' marginwidth=0 marginheight=0 framespacing=0 frameborder=no border=0…
  • Error Line 25, Column 66: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …WS='75,26' marginwidth=0 marginheight=0 framespacing=0 frameborder=no border=0>
  • Error Line 25, Column 80: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …WS='75,26' marginwidth=0 marginheight=0 framespacing=0 frameborder=no border=0>
  • Error Line 25, Column 90: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …WS='75,26' marginwidth=0 marginheight=0 framespacing=0 frameborder=no border=0>
  • Error Line 25, Column 91: element "frameset" undefined
    …WS='75,26' marginwidth=0 marginheight=0 framespacing=0 frameborder=no border=0>

    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 26, Column 53: there is no attribute "id"
    …tp://www.bear411.com/topframe.php' id='topFrame' name='topFrame' scrollbars=no…

    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 26, Column 69: there is no attribute "name"
    ….com/topframe.php' id='topFrame' name='topFrame' scrollbars=no scrolling=no  m…

    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 26, Column 91: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …'topFrame' name='topFrame' scrollbars=no scrolling=no  marginwidth=0 marginhei…
  • Error Line 26, Column 104: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …me='topFrame' scrollbars=no scrolling=no  marginwidth=0 marginheight=0 framesp…
  • Error Line 26, Column 120: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rollbars=no scrolling=no  marginwidth=0 marginheight=0 framespacing=0 framebor…
  • Error Line 26, Column 135: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …olling=no  marginwidth=0 marginheight=0 framespacing=0 frameborder=no border=0…
  • Error Line 26, Column 150: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …olling=no  marginwidth=0 marginheight=0 framespacing=0 frameborder=no border=0>
  • Error Line 26, Column 164: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …olling=no  marginwidth=0 marginheight=0 framespacing=0 frameborder=no border=0>
  • Error Line 26, Column 174: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …olling=no  marginwidth=0 marginheight=0 framespacing=0 frameborder=no border=0>
  • Error Line 26, Column 175: element "frame" undefined
    …olling=no  marginwidth=0 marginheight=0 framespacing=0 frameborder=no border=0>

    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 27, Column 100: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …411' name='msgerFrameB411' scrollbars=no scrolling=no  marginwidth=0 marginhei…
  • Error Line 27, Column 113: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …gerFrameB411' scrollbars=no scrolling=no  marginwidth=0 marginheight=0 framesp…
  • Error Line 27, Column 129: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rollbars=no scrolling=no  marginwidth=0 marginheight=0 framespacing=0 framebor…
  • Error Line 27, Column 144: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …olling=no  marginwidth=0 marginheight=0 framespacing=0 frameborder=no border=0…
  • Error Line 27, Column 159: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …olling=no  marginwidth=0 marginheight=0 framespacing=0 frameborder=no border=0>
  • Error Line 27, Column 173: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …olling=no  marginwidth=0 marginheight=0 framespacing=0 frameborder=no border=0>
  • Error Line 27, Column 183: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …olling=no  marginwidth=0 marginheight=0 framespacing=0 frameborder=no border=0>
  • Error Line 27, Column 184: element "frame" undefined
    …olling=no  marginwidth=0 marginheight=0 framespacing=0 frameborder=no border=0>

    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 28, Column 11: end tag for "frame" omitted, but OMITTAG NO was specified
    </frameset>

    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 27, Column 1: start tag was here
    <frame src='http://www.bear411.com/msger.php' id='msgerFrameB411' name='msgerFr…
  • Error Line 28, Column 11: end tag for "frame" omitted, but OMITTAG NO was specified
    </frameset>

    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 26, Column 1: start tag was here
    <frame src='http://www.bear411.com/topframe.php' id='topFrame' name='topFrame' …
  • Error Line 29, Column 81: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …om/bnewsinfo.php' name='videosFrame' scrollbars=no scrolling=no marginheight=0>
  • Error Line 29, Column 94: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …om/bnewsinfo.php' name='videosFrame' scrollbars=no scrolling=no marginheight=0>
  • Error Line 29, Column 110: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …om/bnewsinfo.php' name='videosFrame' scrollbars=no scrolling=no marginheight=0>
  • Error Line 29, Column 111: element "frame" undefined
    …om/bnewsinfo.php' name='videosFrame' scrollbars=no scrolling=no marginheight=0>

    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).
  • Warning Line 30, Column 60: cannot generate system identifier for general entity "autonick"
    …w.bear411.com/mainframe.php3?nopopup=&autonick=' id='contentFrame' name='conte…

    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 30, Column 60: general entity "autonick" not defined and no default entity
    …w.bear411.com/mainframe.php3?nopopup=&autonick=' id='contentFrame' name='conte…

    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 30, Column 68: reference not terminated by REFC delimiter
    …1.com/mainframe.php3?nopopup=&autonick=' id='contentFrame' name='contentFrame'…

    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.

  • Warning Line 30, Column 68: reference to external entity in attribute value
    …1.com/mainframe.php3?nopopup=&autonick=' id='contentFrame' name='contentFrame'…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 30, Column 68: reference to entity "autonick" for which no system identifier could be generated
    …1.com/mainframe.php3?nopopup=&autonick=' id='contentFrame' name='contentFrame'…

    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 30, Column 59: entity was defined here
    …ww.bear411.com/mainframe.php3?nopopup=&autonick=' id='contentFrame' name='cont…
  • Error Line 30, Column 117: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …frame.php3?nopopup=&autonick=' id='contentFrame' name='contentFrame'  border=0>
  • Error Line 30, Column 118: element "frame" undefined
    …frame.php3?nopopup=&autonick=' id='contentFrame' name='contentFrame'  border=0>

    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 31, Column 65: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …r411.com/bgframefoot.html' scrollbars=no scrolling=no  marginwidth=0 marginhei…
  • Error Line 31, Column 78: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …amefoot.html' scrollbars=no scrolling=no  marginwidth=0 marginheight=0 framesp…
  • Error Line 31, Column 94: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rollbars=no scrolling=no  marginwidth=0 marginheight=0 framespacing=0 framebor…
  • Error Line 31, Column 109: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …olling=no  marginwidth=0 marginheight=0 framespacing=0 frameborder=no border=0…
  • Error Line 31, Column 124: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …olling=no  marginwidth=0 marginheight=0 framespacing=0 frameborder=no border=0>
  • Error Line 31, Column 138: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …olling=no  marginwidth=0 marginheight=0 framespacing=0 frameborder=no border=0>
  • Error Line 31, Column 148: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …olling=no  marginwidth=0 marginheight=0 framespacing=0 frameborder=no border=0>
  • Error Line 31, Column 149: element "frame" undefined
    …olling=no  marginwidth=0 marginheight=0 framespacing=0 frameborder=no border=0>

    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 32, Column 11: end tag for "frame" omitted, but OMITTAG NO was specified
    </frameset>

    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 31, Column 1: start tag was here
    <frame src='http://www.bear411.com/bgframefoot.html' scrollbars=no scrolling=no…
  • Error Line 32, Column 11: end tag for "frame" omitted, but OMITTAG NO was specified
    </frameset>

    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 30, Column 1: start tag was here
    <frame src='http://www.bear411.com/mainframe.php3?nopopup=&autonick=' id='conte…
  • Error Line 32, Column 11: end tag for "frame" omitted, but OMITTAG NO was specified
    </frameset>

    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 29, Column 1: start tag was here
    <frame src='http://www.bear411.com/bnewsinfo.php' name='videosFrame' scrollbars…
  • Error Line 33, Column 61: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    ….bear411.com/bgframe.html' scrollbars=no scrolling=no  marginwidth=0 marginhei…
  • Error Line 33, Column 74: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …bgframe.html' scrollbars=no scrolling=no  marginwidth=0 marginheight=0 framesp…
  • Error Line 33, Column 90: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rollbars=no scrolling=no  marginwidth=0 marginheight=0 framespacing=0 framebor…
  • Error Line 33, Column 105: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …olling=no  marginwidth=0 marginheight=0 framespacing=0 frameborder=no border=0…
  • Error Line 33, Column 120: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …olling=no  marginwidth=0 marginheight=0 framespacing=0 frameborder=no border=0>
  • Error Line 33, Column 134: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …olling=no  marginwidth=0 marginheight=0 framespacing=0 frameborder=no border=0>
  • Error Line 33, Column 144: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …olling=no  marginwidth=0 marginheight=0 framespacing=0 frameborder=no border=0>
  • Error Line 33, Column 145: element "frame" undefined
    …olling=no  marginwidth=0 marginheight=0 framespacing=0 frameborder=no border=0>

    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 34, Column 11: end tag for "frame" omitted, but OMITTAG NO was specified
    </frameset>

    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 33, Column 1: start tag was here
    <frame src='http://www.bear411.com/bgframe.html' scrollbars=no scrolling=no  ma…
  • Error Line 34, Column 11: end tag for "frame" omitted, but OMITTAG NO was specified
    </frameset>

    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 23, Column 1: start tag was here
    <frame src='http://www.bear411.com/bgframe.html' scrollbars=no scrolling=no  ma…
  • Error Line 35, Column 11: element "noframes" undefined
    	<noframes>

    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 38, Column 10: character data is not allowed here
             Want to meet Hot Bear, Chubby, Daddy, Older, Hairy, Musclebear, online…

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 41, Column 7: end tag for "html" which is not finished
    </html> 

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

Visitor Analysis

Daily Visitor
  • 4.550 visits
Daily Visitor

In Page Analysis