Yonja: Türkiye’nin En Büyük Arkadaşlık Sitesi. Yeni Arkadaşlarla Tanışmak ve Sohbet Etmek İçin Doğru Yerdesiniz! ...

yonja.com
  • Domain Name
    yonja.com
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #30716
  • Page Size
    22.1 KB
  • Ip Address
    208.69.179.13
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    17 GIF, 0 JPG, 2 PNG

Website Meta Analysis

  • Title
    Yonja: Türkiye’nin En Büyük Arkadaşlık Sitesi. Yeni Arkadaşlarla Tanışmak ve Sohbet Etmek İçin Doğru Yer!
  • Meta Keyword
    yonja, arkadaşlık, arkadaş, arkadas, arkadaşlık arıyorum, arkadaş arıyorum, kız arkadaş, erkek arkadaş, dost, yonca, sevgili, sohbet, tanışma, aşk, arkadaşlık sitesi, bay, bayan, chat, sesli chat, sohbet, çet, oyun, video, sohpet
  • Meta Description
    Yonja: Türkiye’nin En Büyük Arkadaşlık Sitesi. Yeni Arkadaşlarla Tanışmak ve Sohbet Etmek İçin Doğru Yerdesiniz!

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    208.69.179.13
  • Domain Age
    9 Years, 5 Months, 23 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Sat, 02 Mar 2013 08:06:37 GMT
  • server: Apache
  • pragma: no-cache
  • expires: Wed, 31 Dec 1969 23:59:59 GMT
  • cache-control: no-cache
  • content-language: tr-TR
  • vary: Accept-Encoding
  • content-encoding: gzip
  • content-length: 5544
  • content-type: text/html;charset=UTF-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Name: YONJA.COM
Registrar: MONIKER

Registrant:
Yonja Admin email
Yonja, Inc.
582 Market Street
Suite 508
San Francisco
CA
94104
US

Administrative Contact 717303:
Yonja Admin email
Yonja, Inc.
582 Market Street
Suite 508
San Francisco
CA
94104
US
Phone: +1.4159864040

Billing Contact 717303:
Yonja Admin email
Yonja, Inc.
582 Market Street
Suite 508
San Francisco
CA
94104
US
Phone: +1.4159864040

Technical Contact 717303:
Yonja Admin email
Yonja, Inc.
582 Market Street
Suite 508
San Francisco
CA
94104
US
Phone: +1.4159864040

Name Servers:

NS1.MYDYNDNS.ORG
NS2.MYDYNDNS.ORG

Created: 2003-09-28 18:48:54.39
Database Updated: 2010-03-16 13:25:40.37
Expires: 2016-09-28 18:48:54.45

DNS Analysis


DNS servers
ns2.mydyndns.org [208.76.60.2]
ns1.mydyndns.org [208.76.61.4]


DNS Records

Answer records
yonja.com SOA
server: ns1.mydyndns.org
email: zone-admin@dyndns.com
serial: 2008121710
refresh: 10800
retry: 1800
expire: 604800
minimum ttl: 1800
86400s
yonja.com NS  ns3.mydyndns.org 86400s
yonja.com NS  ns2.mydyndns.org 86400s
yonja.com NS  ns5.mydyndns.org 86400s
yonja.com NS  ns1.mydyndns.org 86400s
yonja.com NS  ns4.mydyndns.org 86400s
yonja.com A 208.69.179.13 600s
yonja.com MX
preference: 20
exchange: server529.appriver.com
600s
yonja.com MX
preference: 10
exchange: server528.appriver.com
600s
yonja.com TXT google-site-verification=XalBOM4MFhnizSfjOGFgJup2n1r9Y4lCgf1DJsAbSRA 600s
yonja.com TXT v=spf1 include:sendgrid.net ip4:208.69.179.0/26 ip4:208.117.53.243 mx ~all 600s

Authority records

Additional records

IP 208.69.179.13 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    San Francisco
  • Continent Code
    94114
  • Latitude
    415
  • Longitude
    807
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 208.69.179.13"
    #
    # Use "?" to get help.
    #

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

    Silicon Valley Web Hosting, Inc. SVWH-ALLOCATION-5 (NET-208-69-176-0-1) 208.69.176.0 - 208.69.183.255
    Yonja YONJA (NET-208-69-179-0-1) 208.69.179.0 - 208.69.179.127


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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 46 Errors
  • 28 Warnings
Ratio Text/Html
  • 0.5380324094571859
Message Error
  • Error Line 38, Column 16: there is no attribute "property"
    <meta property="fb:admins" content="510609201" />

    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 114, Column 8: required attribute "type" not specified
    <script>function __getIEVersion() {

    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 137, Column 24: character "&" is the first character of a delimiter but occurred as data
    var __isIENew = __isIE && __IEVersion >= 8;

    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.
  • Warning Line 137, Column 25: character "&" is the first character of a delimiter but occurred as data
    var __isIENew = __isIE && __IEVersion >= 8;

    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.
  • Warning Line 138, Column 24: character "&" is the first character of a delimiter but occurred as data
    var __isIEOld = __isIE && !__isIENew;

    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.
  • Warning Line 138, Column 25: character "&" is the first character of a delimiter but occurred as data
    var __isIEOld = __isIE && !__isIENew;

    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.
  • Warning Line 141, Column 34: character "&" is the first character of a delimiter but occurred as data
    var __isFireFoxOld = __isFireFox && ((__userAgent.match(/firefox\/2./i) != null…

    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.
  • Warning Line 141, Column 35: character "&" is the first character of a delimiter but occurred as data
    var __isFireFoxOld = __isFireFox && ((__userAgent.match(/firefox\/2./i) != null…

    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.
  • Warning Line 143, Column 34: character "&" is the first character of a delimiter but occurred as data
    var __isFireFoxNew = __isFireFox && !__isFireFoxOld;

    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.
  • Warning Line 143, Column 35: character "&" is the first character of a delimiter but occurred as data
    var __isFireFoxNew = __isFireFox && !__isFireFoxOld;

    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.
  • Warning Line 149, Column 30: character "&" is the first character of a delimiter but occurred as data
    var __isOperaOld = __isOpera && (__operaVersion < 10);

    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.
  • Warning Line 149, Column 31: character "&" is the first character of a delimiter but occurred as data
    var __isOperaOld = __isOpera && (__operaVersion < 10);

    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.
  • Warning Line 149, Column 49: character "<" is the first character of a delimiter but occurred as data
    var __isOperaOld = __isOpera && (__operaVersion < 10);

    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.
  • Warning Line 153, Column 35: character "&" is the first character of a delimiter but occurred as data
        if (typeof(width) == "string" && width != null && width != "" ) {

    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.
  • Warning Line 153, Column 36: character "&" is the first character of a delimiter but occurred as data
        if (typeof(width) == "string" && width != null && width != "" ) {

    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.
  • Warning Line 153, Column 52: character "&" is the first character of a delimiter but occurred as data
        if (typeof(width) == "string" && width != null && width != "" ) {

    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.
  • Warning Line 153, Column 53: character "&" is the first character of a delimiter but occurred as data
        if (typeof(width) == "string" && width != null && width != "" ) {

    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.
  • Warning Line 220, Column 20: character "&" is the first character of a delimiter but occurred as data
    				if ((__isIEOld && parentTagName != "table") || 

    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.
  • Warning Line 220, Column 21: character "&" is the first character of a delimiter but occurred as data
    				if ((__isIEOld && parentTagName != "table") || 

    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.
  • Warning Line 221, Column 38: character "&" is the first character of a delimiter but occurred as data
    					((__isFireFoxNew || __isChrome) && 

    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.
  • Warning Line 221, Column 39: character "&" is the first character of a delimiter but occurred as data
    					((__isFireFoxNew || __isChrome) && 

    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.
  • Warning Line 229, Column 39: character "&" is the first character of a delimiter but occurred as data
    				if (offsetParent != document.body && 

    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.
  • Warning Line 229, Column 40: character "&" is the first character of a delimiter but occurred as data
    				if (offsetParent != document.body && 

    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.
  • Warning Line 238, Column 17: character "&" is the first character of a delimiter but occurred as data
    				if (!__isIE && !__isOperaOld || __isIENew) {

    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.
  • Warning Line 238, Column 18: character "&" is the first character of a delimiter but occurred as data
    				if (!__isIE && !__isOperaOld || __isIENew) {

    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.
  • Warning Line 239, Column 40: character "&" is the first character of a delimiter but occurred as data
    					while (offsetParent != parentNode && 

    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.
  • Warning Line 239, Column 41: character "&" is the first character of a delimiter but occurred as data
    					while (offsetParent != parentNode && 

    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.
  • Error Line 264, Column 134: document type does not allow element "div" here
    …;width:690px;height:503px;z-index:999'><table><tr><td width='690px' height='50…

    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 289, Column 11: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <input id=state type="hidden" value="2" name="state" />
  • Error Line 289, Column 55: document type does not allow element "input" here; assuming missing "caption" start-tag
    <input id=state type="hidden" value="2" name="state" />
  • Error Line 292, Column 38: document type does not allow element "td" here
    <td align="left" style="height:30px;">

    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 293, Column 73: there is no attribute "height"
    			<table width="308" cellspacing="0" cellpadding="0" border="0" height="30">

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

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

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

  • Error Line 316, Column 81: end tag for "input" omitted, but OMITTAG NO was specified
    						<input id="Text1" type="text" class="loginInput" name="nickname" value="">

    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 316, Column 7: start tag was here
    						<input id="Text1" type="text" class="loginInput" name="nickname" value="">
  • Error Line 332, Column 79: end tag for "input" omitted, but OMITTAG NO was specified
    						<input id="password" class="loginInput" type="password" name="password">

    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 332, Column 7: start tag was here
    						<input id="password" class="loginInput" type="password" name="password">
  • Error Line 356, Column 59: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …="rememberMe" type="checkbox" checked value="on" name="rememberMe" class="smal…

    "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 389, Column 131: there is no attribute "border"
    …tp://images2.iyonja.com/images/tr/login.png" alt="Üye Giriş" border="0" /></td>

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

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

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

  • Error Line 391, Column 13: "tr" not finished but containing element ended
    		   </table>	 
  • Error Line 391, Column 13: end tag for "tr" omitted, but OMITTAG NO was specified
    		   </table>	 

    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 390, Column 4: start tag was here
    			<tr>
  • Error Line 391, Column 13: end tag for "tr" omitted, but OMITTAG NO was specified
    		   </table>	 

    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 387, Column 4: start tag was here
    			<tr>
  • Error Line 398, Column 20: required attribute "type" not specified
                <script>

    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 403, Column 196: required attribute "alt" not specified
    …/images2.iyonja.com/pics/index/fb_login_tr.gif' onclick='facebook_login()' />";

    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 403, Column 196: document type does not allow element "img" here
    …/images2.iyonja.com/pics/index/fb_login_tr.gif' onclick='facebook_login()' />";

    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 426, Column 36: there is no attribute "v"
                    <fb:login-button v="2" size="medium" length="long" onlogin="fac…

    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 426, Column 45: there is no attribute "size"
    …          <fb:login-button v="2" size="medium" length="long" onlogin="facebook…

    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 426, Column 61: there is no attribute "length"
    …gin-button v="2" size="medium" length="long" onlogin="facebook_login();" scope…

    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 426, Column 76: there is no attribute "onlogin"
    …" size="medium" length="long" onlogin="facebook_login();" scope="publish_strea…

    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 426, Column 102: there is no attribute "scope"
    …ng" onlogin="facebook_login();" scope="publish_stream, email, user_about_me, u…

    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 426, Column 293: element "fb:login-button" undefined
    …location, user_photos, user_relationships, read_friendlists"></fb:login-button>

    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 436, Column 8: document type does not allow element "tr" here
        <tr><td height="20" class="loginFooter">&nbsp;</td></tr>

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

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

  • Error Line 437, Column 8: end tag for "caption" omitted, but OMITTAG NO was specified
    </table>

    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 289, Column 1: start tag was here
    <input id=state type="hidden" value="2" name="state" />
  • Error Line 437, Column 8: end tag for "table" which is not finished
    </table>

    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 438, Column 9: end tag for element "form" which is not open
      </form> 

    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 446, Column 42: there is no attribute "data-href"
    …			<div class="fb-like-box" data-href="http://www.facebook.com/Yonja" data-wid…

    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 446, Column 85: there is no attribute "data-width"
    …://www.facebook.com/Yonja" data-width="292" data-show-faces="true" data-border…

    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 446, Column 107: there is no attribute "data-show-faces"
    …nja" data-width="292" data-show-faces="true" data-border-color="#FFF" data-str…

    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 446, Column 132: there is no attribute "data-border-color"
    …a-show-faces="true" data-border-color="#FFF" data-stream="false" data-header="…

    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 446, Column 151: there is no attribute "data-stream"
    …="true" data-border-color="#FFF" data-stream="false" data-header="false"></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 446, Column 171: there is no attribute "data-header"
    …="true" data-border-color="#FFF" data-stream="false" data-header="false"></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 519, Column 67: required attribute "alt" not specified
    				<img src="http://images2.iyonja.com/images/facebook_icon2.png">

    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 519, Column 68: end tag for "img" omitted, but OMITTAG NO was specified
    				<img src="http://images2.iyonja.com/images/facebook_icon2.png">

    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 519, Column 5: start tag was here
    				<img src="http://images2.iyonja.com/images/facebook_icon2.png">
  • Error Line 523, Column 66: required attribute "alt" not specified
    				<img src="http://images2.iyonja.com/images/twitter_icon2.png">

    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 523, Column 67: end tag for "img" omitted, but OMITTAG NO was specified
    				<img src="http://images2.iyonja.com/images/twitter_icon2.png">

    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 523, Column 5: start tag was here
    				<img src="http://images2.iyonja.com/images/twitter_icon2.png">
  • Error Line 527, Column 66: required attribute "alt" not specified
    				<img src="http://images2.iyonja.com/images/app_store2.png?v2">

    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 527, Column 67: end tag for "img" omitted, but OMITTAG NO was specified
    				<img src="http://images2.iyonja.com/images/app_store2.png?v2">

    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 527, Column 5: start tag was here
    				<img src="http://images2.iyonja.com/images/app_store2.png?v2">
  • Error Line 531, Column 67: required attribute "alt" not specified
    				<img src="http://images2.iyonja.com/images/android_app.png?v2">

    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 531, Column 68: end tag for "img" omitted, but OMITTAG NO was specified
    				<img src="http://images2.iyonja.com/images/android_app.png?v2">

    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 531, Column 5: start tag was here
    				<img src="http://images2.iyonja.com/images/android_app.png?v2">
  • Warning Line 538, Column 268: cannot generate system identifier for general entity "aid"
    …http://www.firsatbufirsat.com/?pid=10&aid=17" target="_blank" >Fırsat Bu Fırsa…

    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 538, Column 268: general entity "aid" not defined and no default entity
    …http://www.firsatbufirsat.com/?pid=10&aid=17" target="_blank" >Fırsat Bu Fırsa…

    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 538, Column 271: reference not terminated by REFC delimiter
    …p://www.firsatbufirsat.com/?pid=10&aid=17" target="_blank" >Fırsat Bu Fırsat</…

    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 538, Column 271: reference to external entity in attribute value
    …p://www.firsatbufirsat.com/?pid=10&aid=17" target="_blank" >Fırsat Bu Fırsat</…

    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 538, Column 271: reference to entity "aid" for which no system identifier could be generated
    …p://www.firsatbufirsat.com/?pid=10&aid=17" target="_blank" >Fırsat Bu Fırsat</…

    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 538, Column 267: entity was defined here
    …"http://www.firsatbufirsat.com/?pid=10&aid=17" target="_blank" >Fırsat Bu Fırs…
  • Error Line 543, Column 7: end tag for "td" omitted, but OMITTAG NO was specified
      </tr>

    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 508, Column 4: start tag was here
       <td align="left" width="80%" style="line-height:20px" valign="middle">

Visitor Analysis

Daily Visitor
  • 2.917 visits
Daily Visitor