مدونة مختصة في أخبار الآيفون ، الآيبود و الآيباد .وبرامج الجيلبريك والسيديا وشروحات حصرية بالفيديو وبرامج واستعراضات يومية مفيدة لجهازك. ...

iphonedevar.com
  • Domain Name
    iphonedevar.com
  • Favicon
  • Google Page Rank
    2
  • Alexa Rank
    #27935
  • Page Size
    87.8 KB
  • Ip Address
    176.9.101.139
  • Heading
    H1: 1, H2: 16, H3: 15, H4: 13, H5: 0, H6: 0
  • Images
    1 GIF, 11 JPG, 3 PNG

Website Meta Analysis

  • Title
    مدونة الديف تيم العربية
  • Meta Keyword
    iPhone, iPad, iPod, Cydia, jailbreak, YouTube, Appstore, Apple, Google, Twitter, Free, iPhoneDevAR, videos, apps, application, codes, how-to, سيديا, أخبار, فيديوهات, يوتيوب, جيلبريك, آيفون, آيباد, ايبود, برامج, آب ستور، آبل, قوقل, تويتر, تطبيقات, ألعاب, عالم سيديا, مجانية, شروحات, اكواد, الديف, تيم, العربي, العربية, الديف تيم العربي, Arabic, dev, team, Arb dev, arabic dev team, عرب, ديف, تايم , ديف العرب
  • Meta Description
    مدونة مختصة في أخبار الآيفون ، الآيبود و الآيباد .وبرامج الجيلبريك والسيديا وشروحات حصرية بالفيديو وبرامج واستعراضات يومية مفيدة لجهازك.

Technical Analysis

  • Webserver
    nginx/1.2.0
  • Ip Address
    176.9.101.139
  • Domain Age
    2 Years, 11 Months, 9 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • content-type: text/html; charset=UTF-8
  • vary: Accept-Encoding
  • x-pingback: http://www.iphonedevar.com/xmlrpc.php
  • x-ua-compatible: IE=Edge,chrome=1
  • content-encoding: gzip
  • content-length: 17241
  • accept-ranges: bytes
  • date: Fri, 16 Aug 2013 16:32:04 GMT
  • age: 1490
  • connection: keep-alive
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
Domains By Proxy, LLC

Domain Name: IPHONEDEVAR.COM

Domain servers in listed order:
NS1.IPHONEDEVAR.COM
NS2.IPHONEDEVAR.COM

For complete domain details go to:
http://who.godaddy.com/whoischeck.aspx?domain=IPHONEDEVAR.COM

DNS Analysis


DNS servers
ns1.iphonedevar.com [176.9.101.139]
ns2.iphonedevar.com [176.9.101.139]


DNS Records

Answer records
iphonedevar.com TXT v=spf1 ip4:176.9.101.139 ip4:74.200.86.162 ip4:50.116.100.94 a mx include:websitewelcome.com ~all 14400s
iphonedevar.com MX
preference: 20
exchange: alt1.aspmx.l.google.com
300s
iphonedevar.com MX
preference: 0
exchange: aspmx.l.google.com
300s
iphonedevar.com MX
preference: 60
exchange: aspmx4.googlemail.com
300s
iphonedevar.com MX
preference: 50
exchange: aspmx3.googlemail.com
300s
iphonedevar.com MX
preference: 70
exchange: aspmx5.googlemail.com
300s
iphonedevar.com MX
preference: 10
exchange: aspmx.l.google.com
300s
iphonedevar.com MX
preference: 40
exchange: aspmx2.googlemail.com
300s
iphonedevar.com MX
preference: 30
exchange: alt2.aspmx.l.google.com
300s
iphonedevar.com SOA
server: ns1.iphonedevar.com
email: cpanel@arabhosters.com
serial: 2012101600
refresh: 86400
retry: 7200
expire: 3600000
minimum ttl: 86400
86400s
iphonedevar.com NS  ns2.iphonedevar.com 86400s
iphonedevar.com NS  ns1.iphonedevar.com 86400s
iphonedevar.com A 176.9.101.139 14400s

Authority records

Additional records
ns1.iphonedevar.com A 176.9.101.139 14400s
ns2.iphonedevar.com A 176.9.101.139 14400s

IP 176.9.101.139 Analysis

  • Country Code
    DE
  • Country Code3
    DEU
  • Country Name
    Germany
  • City
    EU
  • Continent Code
    51° North
  • Latitude
    9.
  • Longitude
  • No whois ip data for 176.9.101.139

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 46 Errors
  • 1 Warnings
Ratio Text/Html
  • 0.6427134170066591
Message Error
  • Error Line 134, Column 73: there is no attribute "data-count"
    …ass="twitter-share-button" data-count="vertical" data-text="هل تحسن عمر البطار…

    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 134, Column 94: there is no attribute "data-text"
    …tton" data-count="vertical" data-text="هل تحسن عمر البطارية لديك بعد التحديث ل…

    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 134, Column 165: there is no attribute "data-url"
    …تحديث لـiOS 6.1 ؟ [إستفتاء]" data-url="http://www.iphonedevar.com/2013/02/has-…

    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 134, Column 265: there is no attribute "data-via"
    …e-improved-after-upgrading-to-ios-6-1/" data-via="iPhoneDevAr">تويتر </a> <span

    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 136, Column 375: there is no attribute "allowTransparency"
    …50px; height:65px;" allowTransparency="true"></iframe></span> <g:plusone size=…

    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 136, Column 415: there is no attribute "size"
    …rue"></iframe></span> <g:plusone size="tall" href="http://www.iphonedevar.com/…

    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 136, Column 427: there is no attribute "href"
    …e></span> <g:plusone size="tall" href="http://www.iphonedevar.com/2013/02/has-…

    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 136, Column 517: element "g:plusone" undefined
    …-improved-after-upgrading-to-ios-6-1/"></g:plusone></div> الإستفتاءات &#8211; …

    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 153, Column 457: element "g:plusone" undefined
    …r.com/2013/02/flex-the-jailbreak-app/"></g:plusone></div> هل تُعجبك أدوات السي…

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 170, Column 473: element "g:plusone" undefined
    …13/02/video-showing-transparent-ipad/"></g:plusone></div> يبدو أن الجيلبريك جع…

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 187, Column 503: element "g:plusone" undefined
    …-tips-for-ios-6-untethered-jailbreak/"></g:plusone></div> جميعنا يعلم أن الجيل…

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 204, Column 467: element "g:plusone" undefined
    …/2013/02/evasi0n-is-now-80-completed/"></g:plusone></div> أخذ الجيلبريك في آخر…

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 221, Column 495: element "g:plusone" undefined
    …0n-ios-6-x-jailbreak-progress-update/"></g:plusone></div> كالعادة، نحمل لكم ال…

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 238, Column 509: element "g:plusone" undefined
    …obile-phone-vendor-in-the-us-q4-2012/"></g:plusone></div> وفقاً لشركة الأبحاث …

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 255, Column 455: element "g:plusone" undefined
    …ar.com/2013/02/top-news-of-25-31-jan/"></g:plusone></div> كعادة كل ليلة خميس، …

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 272, Column 521: element "g:plusone" undefined
    …-to-get-samsungs-galaxy-nexus-banned/"></g:plusone></div> رفضت مجدداً محكمة ال…

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 289, Column 517: element "g:plusone" undefined
    …aks-record-with-50-million-downloads/"></g:plusone></div> في الأمس، أعلنت الشر…

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 319, Column 24: end tag for "br" omitted, but OMITTAG NO was specified
    class="textwidget"><br> <a

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

  • Info Line 319, Column 20: start tag was here
    class="textwidget"><br> <a
  • Error Line 321, Column 148: end tag for "br" omitted, but OMITTAG NO was specified
    …012/05/total-jailbreak-tools-2.jpg" alt="" width="286" height="96" /></a><br><a

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

  • Info Line 321, Column 144: start tag was here
    …012/05/total-jailbreak-tools-2.jpg" alt="" width="286" height="96" /></a><br><a
  • Error Line 326, Column 178: "0" is not a member of a group specified for any attribute
    …lass="twitter-follow-button external" 0="data-show-count="false"" 1="data-size…
  • Error Line 326, Column 179: an attribute specification must start with a name or name token
    …ass="twitter-follow-button external" 0="data-show-count="false"" 1="data-size=…

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 326, Column 258: required attribute "type" not specified
    …large"">Follow @iPhoneDevAR</a><script>!function(d,s,id){var js,fjs=d.getEleme…

    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 326, Column 507: end tag for "br" omitted, but OMITTAG NO was specified
    …efore(js,fjs);}}(document,"script","twitter-wjs");</script><br></div></div><div

    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 326, Column 498: start tag was here
    …efore(js,fjs);}}(document,"script","twitter-wjs");</script><br></div></div><div
  • Error Line 329, Column 26: there is no attribute "data-href"
    class="g-plus" data-href="//plus.google.com/103324857017160493975?rel=publisher…

    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 342, Column 335: end tag for "br" omitted, but OMITTAG NO was specified
    …w', 'scrollbars=yes,width=550,height=520');return true"><p>ادخل بريدك<br><input

    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 342, Column 331: start tag was here
    …w', 'scrollbars=yes,width=550,height=520');return true"><p>ادخل بريدك<br><input
  • Error Line 346, Column 38: end tag for element "p" which is not open
    type="submit" value="اشترك الان"/></p></form></div></div></div></div></div></di…

    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 362, Column 240: end tag for element "span" which is not open
    …/4 والآيباد 3/2/1 والآيبود تاتش 3G و 4G">676</a></span></span></span></div><div

    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 370, Column 169: end tag for element "span" which is not open
    …يا : ثلاثة بطاقات آيتونز ! [ الفائزون ]">531</a></span></span></span></div><div

    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 378, Column 260: end tag for element "span" which is not open
    …باد والآيبود تاتش بواسطة السيرفر الروسي">458</a></span></span></span></div><div

    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 386, Column 213: end tag for element "span" which is not open
    …والآيباد 2 بواسطة Absinthe على الويندوز">436</a></span></span></span></div><div

    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 394, Column 208: end tag for element "span" which is not open
    …فون 4 اس والآيباد 2 بواسطة CLI للويندوز">392</a></span></span></span></div><div

    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 403, Column 211: end tag for element "span" which is not open
    …ية لديك بعد التحديث لـiOS 6.1 ؟ [إستفتاء]">1</a></span></span></span></div><div

    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 411, Column 165: end tag for element "span" which is not open
    …بيق Flex يتيح لك إنشاء الأدوات الخاصة بك!">1</a></span></span></span></div><div

    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 419, Column 167: end tag for element "span" which is not open
    …على تصميم تخيلي رائع لأيباد شفاف [فيديو]">21</a></span></span></span></div><div

    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 427, Column 201: end tag for element "span" which is not open
    …لبريك غير المقيد iOS 6.1 من فريق Evad3rs">41</a></span></span></span></div><div

    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 435, Column 180: end tag for element "span" which is not open
    …i0n غير المقيد iOS 6.1: إكتمل بنسبة 80%!">45</a></span></span></span></div><div

    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.

  • Warning Line 517, Column 27: character "<" is the first character of a delimiter but occurred as data
    class="clear"></div></div><!–Footer code starts here–><div

    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 541, Column 151: element "g:plusone" undefined
    …all" href="http://www.iPhoneDevAR.com"></g:plusone><script type="text/javascri…

    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 542, Column 10: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    /><center><ul> <br><h4 style="text-align: center;">تابع الديف تيم العربي</h4> <a

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

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

  • Error Line 542, Column 19: document type does not allow element "br" here; assuming missing "li" start-tag
    /><center><ul> <br><h4 style="text-align: center;">تابع الديف تيم العربي</h4> <a
  • Error Line 542, Column 20: end tag for "br" omitted, but OMITTAG NO was specified
    /><center><ul> <br><h4 style="text-align: center;">تابع الديف تيم العربي</h4> <a

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

  • Info Line 542, Column 16: start tag was here
    /><center><ul> <br><h4 style="text-align: center;">تابع الديف تيم العربي</h4> <a
  • Error Line 546, Column 138: end tag for "li" omitted, but OMITTAG NO was specified
    …tle="SEO text 4">البريد الإلكتروني</a></ul><center></center></center></div><div

    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 542, Column 16: start tag was here
    /><center><ul> <br><h4 style="text-align: center;">تابع الديف تيم العربي</h4> <a
  • Error Line 546, Column 170: end tag for "span" omitted, but OMITTAG NO was specified
    …tle="SEO text 4">البريد الإلكتروني</a></ul><center></center></center></div><div

    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 539, Column 75: start tag was here
    href="http://www.iphonedevar.com/feed/">تغذية الموقع </a></span> &middot; <span
  • Warning Line 548, Column 440: character "<" is the first character of a delimiter but occurred as data
    …t')[0];s.parentNode.insertBefore(ga,s);})();</script><!–Footer code ends here–>

    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 548, Column 466: end tag for "center" omitted, but OMITTAG NO was specified
    …t')[0];s.parentNode.insertBefore(ga,s);})();</script><!–Footer code ends here–>

    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 525, Column 72: start tag was here
    …"http://pagead2.googlesyndication.com/pagead/show_ads.js"></script><center><div
  • Error Line 548, Column 466: end tag for "center" omitted, but OMITTAG NO was specified
    …t')[0];s.parentNode.insertBefore(ga,s);})();</script><!–Footer code ends here–>

    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 518, Column 21: start tag was here
    class="clear"></div><center><script type="text/javascript"><!--
  • Error Line 548, Column 466: end tag for "div" omitted, but OMITTAG NO was specified
    …t')[0];s.parentNode.insertBefore(ga,s);})();</script><!–Footer code ends here–>

    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 30: start tag was here
    class="rtl home blog chrome"><div
  • Error Line 548, Column 466: end tag for "body" omitted, but OMITTAG NO was specified
    …t')[0];s.parentNode.insertBefore(ga,s);})();</script><!–Footer code ends here–>

    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 22, Column 231: start tag was here
    …TagName("script")[0];s.parentNode.insertBefore(po,s);})();</script></head><body
  • Error Line 548, Column 466: end tag for "html" omitted, but OMITTAG NO was specified
    …t')[0];s.parentNode.insertBefore(ga,s);})();</script><!–Footer code ends here–>

    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 1, Column 122: start tag was here
    …ansitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html

Visitor Analysis

Daily Visitor
  • 8.167 visits