alinea.fr

Alinéa, le spécialiste meubles et déco. Boutique en ligne et 25 magasins sur toute la France. Conseils décoration pour votre intérieur : salon et séjour, cuisine et accessoires, bureau, chambre et salle de ...

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

Overview Info

  • Domain Name
    alinea.fr
  • Favicon
  • Alexa Rank
    #19846
  • Google Page Rank
    PR 5
  • Ip Address
    95.131.141.33
  • Page Size
    259.2 KB
  • Images
    2 GIF, 0 JPG, 5 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 21 12 38 0 0

Website Meta Analysis



  • Title
    Alinéa, Meubles et décoration d'intérieur : salon, chambre, cuisine, salle de bain et bureau
  • Meta Keyword
    Alinéa, Meubles, décoration d'intérieur, salon, chambre, cuisine, salle de bain, bureau, rangement, luminaire, tapis
  • Meta Description
    Alinéa, le spécialiste meubles et déco. Boutique en ligne et 25 magasins sur toute la France. Conseils décoration pour votre intérieur : salon et séjour, cuisine et accessoires, bureau, chambre et salle de bain.

Technical Analysis



  • Webserver
  • Ip Address
    95.131.141.33
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from alinea.fr.

HTML Analysis

  • cache-control: public, max-age=120, max-age=0
  • pragma: public
  • vary: Accept-Encoding
  • content-encoding: gzip
  • content-type: text/html; charset=UTF-8
  • x-cacheable-status: 200
  • x-cacheable: Cacheable
  • content-length: 28563
  • date: Sun, 27 Jan 2013 07:59:02 GMT
  • age: 118
  • connection: keep-alive
  • x-hit: 1
  • x-powered: Oxalide.com - 02
  • x-google-cache-control: remote-cache-hit
  • via: HTTP/1.1 GWA (remote cache hit)
%%
%% This is the AFNIC Whois server.
%%
%% complete date format : DD/MM/YYYY
%% short date format : DD/MM
%% version : FRNIC-2.5
%%
%% Rights restricted by copyright.
%% See http://www.afnic.fr/afnic/web/mentions-legales-whois_en
%%
%% Use '-h' option to obtain more information about this service.
%%
%% [188.190.96.209 REQUEST] >> alinea.fr
%%
%% RL Net [##########] - RL IP [#########.]
%%

domain: alinea.fr
status: ACTIVE
hold: NO
holder-c: A32382-FRNIC
admin-c: TC5118-FRNIC
tech-c: I10396-FRNIC
zone-c: NFC1-FRNIC
nsl-id: NSL27513-FRNIC
registrar: ASCIO TECHNOLOGIES Inc.
anniversary: 21/07
created: 18/09/1997
last-update: 03/09/2012
source: FRNIC

ns-list: NSL27513-FRNIC
nserver: indom130.indomco.org
nserver: indom10.indomco.com
nserver: indom20.indomco.net
nserver: indom30.indomco.fr [213.205.102.3]
nserver: indom80.indomco.hk
source: FRNIC

registrar: ASCIO TECHNOLOGIES Inc.
type: Isp Option 1
address: Islands Brygge 55
address: DK-2300 COPENHAGUE S
country: DK
phone: +45 33 88 61 00
fax-no: +45 33 88 61 01
e-mail: email
website: http://www.ascio.com
anonymous: NO
registered: 18/01/2001
source: FRNIC

nic-hdl: I10396-FRNIC
type: ORGANIZATION
contact: INDOM
address: 124-126, rue de Provence
address: 75008 Paris
country: FR
phone: +33 1 76 70 05 67
fax-no: +33 1 48 01 67 73
e-mail: email
registrar: ASCIO TECHNOLOGIES Inc.
changed: 03/09/2012 email
anonymous: NO
obsoleted: NO
eligstatus: ok
eligdate: 03/09/2012 09:24:54
source: FRNIC

nic-hdl: TC5118-FRNIC
type: ORGANIZATION
contact: TMARKS CONSEILS
address: 31, rue Tronchet
address: 75008 Paris
country: FR
phone: +33 1 43 12 86 12
fax-no: +33 1 43 12 86 13
e-mail: email
registrar: ASCIO TECHNOLOGIES Inc.
changed: 03/09/2012 email
anonymous: NO
obsoleted: NO
source: FRNIC

nic-hdl: A32382-FRNIC
type: ORGANIZATION
contact: ALINEA
address: centre commercial le Pontet
address: 84130 Le Pontet
country: FR
phone: +33 1 72 74 00 00
e-mail: email
registrar: ASCIO TECHNOLOGIES Inc.
changed: 03/09/2012 email
anonymous: NO
obsoleted: NO
eligstatus: ok
eligdate: 03/09/2012 09:34:55
source: FRNIC

DNS Analysis


DNS servers
indom80.indomco.hk
indom20.indomco.net [69.170.135.194]
indom10.indomco.com [217.174.200.97]
indom30.indomco.fr [213.205.102.3]
indom130.indomco.org


DNS Records

Answer records
alinea.fr SOA
server: indom10.indomco.com
email: technique@indom.com
serial: 2012122415
refresh: 86400
retry: 7200
expire: 604800
minimum ttl: 7200
300s
alinea.fr A 95.131.141.33 300s
alinea.fr MX
preference: 40
exchange: alt1.aspmx.l.google.com
300s
alinea.fr NS  indom80.indomco.hk 300s
alinea.fr NS  indom30.indomco.fr 300s
alinea.fr NS  indom130.indomco.org 300s
alinea.fr TXT v=spf1 ip4:212.99.91.198 include:_spf.google.com ~all 300s
alinea.fr MX
preference: 5
exchange: aspmx.l.google.com
300s
alinea.fr NS  indom10.indomco.com 300s
alinea.fr NS  indom20.indomco.net 300s
alinea.fr MX
preference: 50
exchange: alt2.aspmx.l.google.com
300s

Authority records

Additional records
indom130.indomco.org A 209.235.192.171 21600s
indom80.indomco.hk A 202.157.180.150 21600s

IP 95.131.141.33 Analysis

  • Country Code
    FR
  • Country Code3
    FRA
  • Country Name
    France
  • City
    EU
  • Continent Code
    46° North
  • Latitude
    2.
  • Longitude
  • No whois ip data for 95.131.141.33

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 12 Errors
  • 9 Warnings
Ratio Text/Html
  • 0.7320193481307355
Message Error
  • Error Line 150, Column 9: end tag for "p" omitted, but OMITTAG NO was specified
    		</form>

    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 147, Column 3: start tag was here
    		<p><label for="compte">E-mail&nbsp;:</label> <input name="login[username]" cl…
  • Warning Line 2547, Column 134: cannot generate system identifier for general entity "config"
    …rl=http://alinea.scene7.com/is/image/&config=Scene7SharedAssets/eCatalog%5Fema…

    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 2547, Column 134: general entity "config" not defined and no default entity
    …rl=http://alinea.scene7.com/is/image/&config=Scene7SharedAssets/eCatalog%5Fema…

    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 2547, Column 140: reference not terminated by REFC delimiter
    …p://alinea.scene7.com/is/image/&config=Scene7SharedAssets/eCatalog%5Femail%5FD…

    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 2547, Column 140: reference to external entity in attribute value
    …p://alinea.scene7.com/is/image/&config=Scene7SharedAssets/eCatalog%5Femail%5FD…

    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 2547, Column 140: reference to entity "config" for which no system identifier could be generated
    …p://alinea.scene7.com/is/image/&config=Scene7SharedAssets/eCatalog%5Femail%5FD…

    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 2547, Column 133: entity was defined here
    …Url=http://alinea.scene7.com/is/image/&config=Scene7SharedAssets/eCatalog%5Fem…
  • Warning Line 2547, Column 185: cannot generate system identifier for general entity "contentRoot"
    …SharedAssets/eCatalog%5Femail%5FDHTML&contentRoot=http://alinea.scene7.com/ski…

    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 2547, Column 185: general entity "contentRoot" not defined and no default entity
    …SharedAssets/eCatalog%5Femail%5FDHTML&contentRoot=http://alinea.scene7.com/ski…

    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 2547, Column 196: reference not terminated by REFC delimiter
    …s/eCatalog%5Femail%5FDHTML&contentRoot=http://alinea.scene7.com/skins/&asset=A…

    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 2547, Column 196: reference to external entity in attribute value
    …s/eCatalog%5Femail%5FDHTML&contentRoot=http://alinea.scene7.com/skins/&asset=A…

    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 2547, Column 196: reference to entity "contentRoot" for which no system identifier could be generated
    …s/eCatalog%5Femail%5FDHTML&contentRoot=http://alinea.scene7.com/skins/&asset=A…

    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 2547, Column 184: entity was defined here
    …7SharedAssets/eCatalog%5Femail%5FDHTML&contentRoot=http://alinea.scene7.com/sk…
  • Warning Line 2547, Column 229: cannot generate system identifier for general entity "asset"
    …tRoot=http://alinea.scene7.com/skins/&asset=Alinea/Alinea%5FLeaflet%5FElectro%…

    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 2547, Column 229: general entity "asset" not defined and no default entity
    …tRoot=http://alinea.scene7.com/skins/&asset=Alinea/Alinea%5FLeaflet%5FElectro%…

    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 2547, Column 234: reference not terminated by REFC delimiter
    …=http://alinea.scene7.com/skins/&asset=Alinea/Alinea%5FLeaflet%5FElectro%5FOK#…

    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 2547, Column 234: reference to external entity in attribute value
    …=http://alinea.scene7.com/skins/&asset=Alinea/Alinea%5FLeaflet%5FElectro%5FOK#…

    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 2547, Column 234: reference to entity "asset" for which no system identifier could be generated
    …=http://alinea.scene7.com/skins/&asset=Alinea/Alinea%5FLeaflet%5FElectro%5FOK#…

    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 2547, Column 228: entity was defined here
    …ntRoot=http://alinea.scene7.com/skins/&asset=Alinea/Alinea%5FLeaflet%5FElectro…
  • Error Line 2903, Column 150: required attribute "alt" not specified
    …/Alinea/logo%5Ffacebook" title="http://www.facebook.com/alineameublesetdeco" />

    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 2907, Column 134: required attribute "alt" not specified
    …ne7.com/is/image/Alinea/logo%5Ftwitter" title="http://twitter.com/Alinea_fr" />

    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 2911, Column 136: required attribute "alt" not specified
    …7.com/is/image/Alinea/logo%5Fpinterest" title="http://pinterest.com/alinea/" />

    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 2915, Column 177: required attribute "alt" not specified
    …s?$original$" title="http://plus.google.com/u/0/104628443975205771070/posts" />

    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 2919, Column 154: required attribute "alt" not specified
    …nea/logo%5Fyou%2Dtube" title="http://www.youtube.com/user/alineafrance/feed" />

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

Visitor Analysis

Daily Visitor
  • 10.033 visits
Daily Visitor

In Page Analysis