أخبار مغربية محدثة على مدار الساعة - المغرب - 20 فبراير - صحافة وطنية - لاماب - هسبريس Source centrale d'informations et de nouvelles sur le Maroc ...

febrayer.com
  • Domain Name
    febrayer.com
  • Favicon
  • Google Page Rank
    3
  • Alexa Rank
    #59003
  • Page Size
    136.5 KB
  • Ip Address
    213.251.158.197
  • Heading
    H1: 1, H2: 1, H3: 47, H4: 7, H5: 0, H6: 0
  • Images
    12 GIF, 2 JPG, 0 PNG

Website Meta Analysis

  • Title
    فبراير : الحقيقة كما هي
  • Meta Keyword
    مكتوب ياهو,الجزيرة, أخبار المغرب,maroc,جريدة إلكترونية مغربية,محمد السادس ,febrayer,فبراير : الحقيقة كما هي,الحسن الثاني , هيسبريس ,morocco,facebook,top stories,hespresse,fb,
  • Meta Description
    أخبار مغربية محدثة على مدار الساعة - المغرب - 20 فبراير - صحافة وطنية - لاماب - هسبريس Source centrale d'informations et de nouvelles sur le Maroc

Technical Analysis

  • Webserver
    WMaker/Prod
  • Ip Address
    213.251.158.197
  • Domain Age
    1 Years, 6 Months, 15 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Wed, 26 Jun 2013 22:51:33 GMT
  • vary: Accept-Encoding,User-Agent
  • content-encoding: gzip
  • content-length: 24082
  • connection: close
  • content-type: text/html; charset=UTF-8
  • server: WMaker/Prod
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Domain Name: febrayer.com
Registrant:

Maria Moukrim ()

Fax:
4 Rue La Gyenne, Manal 2, 10eme etage - Quartier Des Hopitau
Casablanca, 20000
MA
Administrative Contact:

Maria Moukrim ( email )
+212.661220252
Fax:
4 Rue La Gyenne, Manal 2, 10eme etage - Quartier Des Hopitau
Casablanca, 20000
MA
Technical Contact:
Arcanes Technologies - Heberjahiz
Amine RIADI ( email )
+212.522528868
Fax: +212.522214662
Casablanca Technopark - BP 16491
Casablanca, 20153
MA
Domain Status: Locked
Name Servers:
dns1.name-services.com
dns2.name-services.com
dns3.name-services.com
dns4.name-services.com
dns5.name-services.com

Created: 19 Dec 2011 19:18:00
Expires: 19 Dec 2012 11:18:00

DNS Analysis


DNS servers
dns1.wmaker.net [213.251.158.206]
dns2.wmaker.net [213.251.158.202]


DNS Records

Answer records
febrayer.com SOA
server: webpri.wmaker.net
email: info@webzinemaker.net
serial: 2011122209
refresh: 28800
retry: 7200
expire: 604800
minimum ttl: 86400
86400s
febrayer.com A 213.251.158.218 86400s
febrayer.com NS  dns1.wmaker.net 86400s
febrayer.com NS  dns2.wmaker.net 86400s
febrayer.com MX
preference: 10
exchange: smtp01.wmaker.net
86400s
febrayer.com MX
preference: 20
exchange: smtp02.wmaker.net
86400s
febrayer.com A 213.251.158.197 86400s

Authority records

Additional records
smtp01.wmaker.net A 94.23.134.226 86400s
smtp02.wmaker.net A 213.251.158.220 86400s
dns1.wmaker.net A 213.251.158.206 86400s
dns2.wmaker.net A 213.251.158.202 86400s

IP 213.251.158.197 Analysis

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 21 Errors
  • 0 Warnings
Ratio Text/Html
  • 0.6352635571267049
Message Error
  • Error Line 11, Column 16: there is no attribute "property"
    <meta property="og:url" content="http://www.febrayer.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 108, Column 59: there is no attribute "target"
    …="http://nissae.febrayer.com/" target="_blank"><img src="/photo/mod-4438332-11…

    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 821, Column 15: there is no attribute "src"
    	 <iframe src="//www.facebook.com/plugins/likebox.php?href=https%3A%2F%2Fwww.fa…

    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 821, Column 265: there is no attribute "scrolling"
    …&amp;appId=261732760539939" scrolling="no" frameborder="0" style="border:none;…

    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 821, Column 282: there is no attribute "frameborder"
    …760539939" scrolling="no" frameborder="0" style="border:none; overflow:hidden;…

    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 821, Column 292: there is no attribute "style"
    … scrolling="no" frameborder="0" style="border:none; overflow:hidden; width:400…

    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 821, Column 369: there is no attribute "allowTransparency"
    …overflow:hidden; width:400px; height:390px;" allowTransparency="true"></iframe>

    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 821, Column 375: element "iframe" undefined
    …overflow:hidden; width:400px; height:390px;" allowTransparency="true"></iframe>

    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 1740, Column 442: required attribute "alt" not specified
    …<img src="http://v-expresse.com/khadima.jpg" width="300" height="110"></a></td>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 1740, Column 446: end tag for "img" omitted, but OMITTAG NO was specified
    …<img src="http://v-expresse.com/khadima.jpg" width="300" height="110"></a></td>

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

  • Info Line 1740, Column 373: start tag was here
    …%D9%85%D8%B2%D9%82%D8%AA_a15351.html"><img src="http://v-expresse.com/khadima.…
  • Error Line 1744, Column 95: end tag for "param" omitted, but OMITTAG NO was specified
    …me="movie" value="http://www.youtube.com/v/YaphnNmO8kI?version=3&amp;hl=fr_FR">

    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 1744, Column 7: start tag was here
          <param name="movie" value="http://www.youtube.com/v/YaphnNmO8kI?version=3…
  • Error Line 1745, Column 50: end tag for "param" omitted, but OMITTAG NO was specified
          <param name="allowFullScreen" value="true">

    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 1745, Column 7: start tag was here
          <param name="allowFullScreen" value="true">
  • Error Line 1746, Column 54: end tag for "param" omitted, but OMITTAG NO was specified
          <param name="allowscriptaccess" value="always">

    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 1746, Column 7: start tag was here
          <param name="allowscriptaccess" value="always">
  • Error Line 1747, Column 18: there is no attribute "src"
          <embed src="http://www.youtube.com/v/YaphnNmO8kI?version=3&amp;hl=fr_FR" …

    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 1747, Column 85: there is no attribute "type"
    …hnNmO8kI?version=3&amp;hl=fr_FR" type="application/x-shockwave-flash" width="2…

    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 1747, Column 123: there is no attribute "width"
    …"application/x-shockwave-flash" width="299" height="300" allowscriptaccess="al…

    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 1747, Column 136: there is no attribute "height"
    …x-shockwave-flash" width="299" height="300" allowscriptaccess="always" allowfu…

    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 1747, Column 160: there is no attribute "allowscriptaccess"
    …h="299" height="300" allowscriptaccess="always" allowfullscreen="true"></embed>

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 1747, Column 185: there is no attribute "allowfullscreen"
    …h="299" height="300" allowscriptaccess="always" allowfullscreen="true"></embed>

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 1747, Column 191: element "embed" undefined
    …h="299" height="300" allowscriptaccess="always" allowfullscreen="true"></embed>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).

Visitor Analysis

Daily Visitor
  • 2.450 visits
Daily Visitor