culiar.com

culiar.com has Alexa Rank 25.769 and Google Page Rank is 3

Display Widget for this domain on your website. Click Here
Processing update domain...

Overview Info

  • Domain Name
    culiar.com
  • Favicon
  • Alexa Rank
    #25769
  • Google Page Rank
    PR 3
  • Ip Address
    64.188.48.195
  • Page Size
    72.1 KB
  • Images
    1 GIF, 55 JPG, 2 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 1 0 0 0 0

Technical Analysis



  • Webserver
    nginx
  • Ip Address
    64.188.48.195
  • Domain Age
    11 Years, 2 Months, 19 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: nginx
  • date: Tue, 17 Sep 2013 18:13:49 GMT
  • content-type: text/html; charset=utf-8
  • connection: keep-alive
  • vary: Accept-Encoding
  • expires: Mon, 26 Jul 1997 05:00:00 GMT
  • last-modified: Tue, 17 Sep 2013 18:13:49 GMT
  • cache-control: no-store, no-cache, must-revalidate
  • pragma: no-cache
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Name: CULIAR.COM
Created on: 28-Jun-02
Expires on: 28-Jun-13
Last Updated on: 11-Sep-12

Registrant:
PROGRAM THREE LLC.
6955 SW 52ND ST.
MIAMI, Florida 33166
United States

Administrative Contact:
THREE, PROGRAM email
PROGRAM THREE LLC.
6955 SW 52ND ST.
MIAMI, Florida 33166
United States
+1.3056952500

Technical Contact:
THREE, PROGRAM email
PROGRAM THREE LLC.
6955 SW 52ND ST.
MIAMI, Florida 33166
United States
+1.3056952500

Domain servers in listed order:
PDNS1.ULTRADNS.NET
PDNS2.ULTRADNS.NET
PDNS3.ULTRADNS.ORG
PDNS4.ULTRADNS.ORG
PDNS5.ULTRADNS.INFO
PDNS6.ULTRADNS.CO.UK

DNS Analysis


DNS servers
pdns3.ultradns.org [199.7.68.1]
pdns4.ultradns.org [199.7.69.1]
pdns1.ultradns.net [204.74.108.1]
pdns2.ultradns.net [204.74.109.1]
pdns5.ultradns.info [204.74.114.1]
pdns6.ultradns.co.uk [204.74.115.1]

DNS Records

Answer records
culiar.com A 64.188.48.195 900s
culiar.com NS  pdns1.ultradns.net 86400s
culiar.com NS  pdns2.ultradns.net 86400s
culiar.com NS  pdns3.ultradns.org 86400s
culiar.com NS  pdns4.ultradns.org 86400s
culiar.com NS  pdns5.ultradns.info 86400s
culiar.com NS  pdns6.ultradns.co.uk 86400s
culiar.com SOA
server: pdns1.ultradns.net
email: support@isprime.com
serial: 2012082828
refresh: 3600
retry: 300
expire: 604800
minimum ttl: 86400
86400s

Authority records

Additional records

IP 64.188.48.195 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Weehawken
  • Continent Code
    07086
  • Latitude
    201
  • Longitude
    501
  • No whois ip data for 64.188.48.195

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 19 Errors
  • 15 Warnings
Ratio Text/Html
  • 0.8372902946038974
Message Error
  • Error Line 50, Column 109: required attribute "alt" not specified
    …com/siteimages/site/culiar/logo.jpeg"/></a>                    <h1>Nuevo Porta…

    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 61, Column 163: required attribute "alt" not specified
    …img src="http://images1.culiarmedia.com/siteimages/site/twitterfollow.png"></a>

    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 61, Column 167: end tag for "img" omitted, but OMITTAG NO was specified
    …img src="http://images1.culiarmedia.com/siteimages/site/twitterfollow.png"></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 61, Column 88: start tag was here
    ….com/#!/CuliarPuntoCom" target="_new"><img src="http://images1.culiarmedia.com…
  • Error Line 64, Column 157: required attribute "alt" not specified
    …new"><img src="http://images1.culiarmedia.com/siteimages/site/fbshare.png"></a>

    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 64, Column 161: end tag for "img" omitted, but OMITTAG NO was specified
    …new"><img src="http://images1.culiarmedia.com/siteimages/site/fbshare.png"></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 64, Column 88: start tag was here
    …ook.com/CuliarPuntoCom" target="_new"><img src="http://images1.culiarmedia.com…
  • Warning Line 100, Column 96: cannot generate system identifier for general entity "p"
    …raffichaus.com/directserve.php?z=1472&p=322" target="_new" rel="nofollow">Cama…

    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 100, Column 96: general entity "p" not defined and no default entity
    …raffichaus.com/directserve.php?z=1472&p=322" target="_new" rel="nofollow">Cama…

    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 100, Column 97: reference not terminated by REFC delimiter
    …affichaus.com/directserve.php?z=1472&p=322" target="_new" rel="nofollow">Camar…

    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 100, Column 97: reference to external entity in attribute value
    …affichaus.com/directserve.php?z=1472&p=322" target="_new" rel="nofollow">Camar…

    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 100, Column 97: reference to entity "p" for which no system identifier could be generated
    …affichaus.com/directserve.php?z=1472&p=322" target="_new" rel="nofollow">Camar…

    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 100, Column 95: entity was defined here
    …traffichaus.com/directserve.php?z=1472&p=322" target="_new" rel="nofollow">Cam…
  • Warning Line 751, Column 75: cannot generate system identifier for general entity "utm_campaign"
    …p://www.adbucks.com?utm_source=culiar&utm_campaign=ftr_ad&utm_medium=txt_ad" t…

    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 751, Column 75: general entity "utm_campaign" not defined and no default entity
    …p://www.adbucks.com?utm_source=culiar&utm_campaign=ftr_ad&utm_medium=txt_ad" t…

    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 751, Column 87: reference not terminated by REFC delimiter
    …cks.com?utm_source=culiar&utm_campaign=ftr_ad&utm_medium=txt_ad" target="_new"…

    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 751, Column 87: reference to external entity in attribute value
    …cks.com?utm_source=culiar&utm_campaign=ftr_ad&utm_medium=txt_ad" target="_new"…

    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 751, Column 87: reference to entity "utm_campaign" for which no system identifier could be generated
    …cks.com?utm_source=culiar&utm_campaign=ftr_ad&utm_medium=txt_ad" target="_new"…

    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 751, Column 74: entity was defined here
    …tp://www.adbucks.com?utm_source=culiar&utm_campaign=ftr_ad&utm_medium=txt_ad" …
  • Warning Line 751, Column 95: cannot generate system identifier for general entity "utm_medium"
    …utm_source=culiar&utm_campaign=ftr_ad&utm_medium=txt_ad" target="_new" rel="no…

    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 751, Column 95: general entity "utm_medium" not defined and no default entity
    …utm_source=culiar&utm_campaign=ftr_ad&utm_medium=txt_ad" target="_new" rel="no…

    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 751, Column 105: reference not terminated by REFC delimiter
    …=culiar&utm_campaign=ftr_ad&utm_medium=txt_ad" target="_new" rel="nofollow">AD…

    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 751, Column 105: reference to external entity in attribute value
    …=culiar&utm_campaign=ftr_ad&utm_medium=txt_ad" target="_new" rel="nofollow">AD…

    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 751, Column 105: reference to entity "utm_medium" for which no system identifier could be generated
    …=culiar&utm_campaign=ftr_ad&utm_medium=txt_ad" target="_new" rel="nofollow">AD…

    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 751, Column 94: entity was defined here
    …?utm_source=culiar&utm_campaign=ftr_ad&utm_medium=txt_ad" target="_new" rel="n…
  • Error Line 758, Column 22: required attribute "type" not specified
    </div>        <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>.

  • Warning Line 760, Column 56: cannot generate system identifier for general entity "s"
                var redirectUrl = '/index.php?widget=false&s='+componentPath;

    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 760, Column 56: general entity "s" not defined and no default entity
                var redirectUrl = '/index.php?widget=false&s='+componentPath;

    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 760, Column 57: reference not terminated by REFC delimiter
                var redirectUrl = '/index.php?widget=false&s='+componentPath;

    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.

  • Error Line 760, Column 57: reference to entity "s" for which no system identifier could be generated
                var redirectUrl = '/index.php?widget=false&s='+componentPath;

    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 760, Column 55: entity was defined here
                var redirectUrl = '/index.php?widget=false&s='+componentPath;
  • Warning Line 825, Column 51: cannot generate system identifier for general entity "q"
                loadModule('container','search.search&q='+jQuery('#search').val());

    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 825, Column 51: general entity "q" not defined and no default entity
                loadModule('container','search.search&q='+jQuery('#search').val());

    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 825, Column 52: reference not terminated by REFC delimiter
                loadModule('container','search.search&q='+jQuery('#search').val());

    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.

  • Error Line 825, Column 52: reference to entity "q" for which no system identifier could be generated
                loadModule('container','search.search&q='+jQuery('#search').val());

    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 825, Column 50: entity was defined here
                loadModule('container','search.search&q='+jQuery('#search').val());

Visitor Analysis

Daily Visitor
  • 4.783 visits

In Page Analysis