laxx.dj

laxx.dj has Alexa Rank 412.152 and Google Page Rank is 0

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

Overview Info

  • Domain Name
    laxx.dj
  • Favicon
  • Alexa Rank
    #412152
  • Google Page Rank
    PR 0
  • Ip Address
    69.64.43.195
  • Page Size
    8 KB
  • Images
    0 GIF, 0 JPG, 0 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 0 0 0 0 0

Technical Analysis



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

Hyper Text Transfer Protocol (HTTP) header show data header response from laxx.dj.

HTML Analysis

  • content-encoding: gzip
  • content-type: text/html; charset=utf-8
  • x-powered-by: HPHP
  • date: Tue, 25 Jun 2013 07:38:00 GMT
  • content-length: 2686
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for laxx.dj

DNS Analysis


DNS servers
ns.udagdns.net [89.31.142.100]
ns.udagdns.de [89.31.138.100]


DNS Records

Answer records
laxx.dj MX
preference: 20
exchange: mx01.udag.de
14400s
laxx.dj MX
preference: 10
exchange: mx00.udag.de
14400s
laxx.dj A 69.64.43.195 3600s
laxx.dj NS  ns.udagdns.de 259200s
laxx.dj NS  ns.udagdns.net 259200s
laxx.dj SOA
server: ns.udagdns.net
email: hostmaster@united-domains.de
serial: 2012111313
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 3600
1048576s

Authority records

Additional records
mx01.udag.de A 62.146.106.40 86400s
ns.udagdns.de A 89.31.138.100 3600s
ns.udagdns.net A 89.31.142.100 3600s
mx00.udag.de A 62.146.106.39 86400s

IP 69.64.43.195 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Saint Louis
  • Continent Code
    63101
  • Latitude
    314
  • Longitude
    609
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 69.64.43.195"
    #
    # Use "?" to get help.
    #

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

    NetRange: 69.64.32.0 - 69.64.63.255
    CIDR: 69.64.32.0/19
    OriginAS: AS30083
    NetName: HSI-1
    NetHandle: NET-69-64-32-0-1
    Parent: NET-69-0-0-0-0
    NetType: Direct Allocation
    RegDate: 2003-07-30
    Updated: 2012-05-10
    Ref: http://whois.arin.net/rest/net/NET-69-64-32-0-1

    OrgName: Hosting Solutions International, Inc.
    OrgId: SERVE-6
    Address: 210 North Tucker Blvd.
    Address: Suite 910
    City: Saint Louis
    StateProv: MO
    PostalCode: 63101
    Country: US
    RegDate: 2003-04-15
    Updated: 2012-05-10
    Comment: Please forward abuse complaints to abuse@hostingsolutionsint.com
    Ref: http://whois.arin.net/rest/org/SERVE-6

    OrgNOCHandle: SWI19-ARIN
    OrgNOCName: Wintz, Sascha
    OrgNOCPhone: +1-314-480-6840
    OrgNOCEmail: s.wintz@hostingsolutionsinternational.com
    OrgNOCRef: http://whois.arin.net/rest/poc/SWI19-ARIN

    OrgAbuseHandle: HAD15-ARIN
    OrgAbuseName: HSI Abuse Department
    OrgAbusePhone: +1-314-266-3638
    OrgAbuseEmail: abuse@hostingsolutionsint.com
    OrgAbuseRef: http://whois.arin.net/rest/poc/HAD15-ARIN

    OrgTechHandle: SWI19-ARIN
    OrgTechName: Wintz, Sascha
    OrgTechPhone: +1-314-480-6840
    OrgTechEmail: s.wintz@hostingsolutionsinternational.com
    OrgTechRef: http://whois.arin.net/rest/poc/SWI19-ARIN

    RNOCHandle: SWI19-ARIN
    RNOCName: Wintz, Sascha
    RNOCPhone: +1-314-480-6840
    RNOCEmail: s.wintz@hostingsolutionsinternational.com
    RNOCRef: http://whois.arin.net/rest/poc/SWI19-ARIN

    RTechHandle: SWI19-ARIN
    RTechName: Wintz, Sascha
    RTechPhone: +1-314-480-6840
    RTechEmail: s.wintz@hostingsolutionsinternational.com
    RTechRef: http://whois.arin.net/rest/poc/SWI19-ARIN

    RAbuseHandle: HAD15-ARIN
    RAbuseName: HSI Abuse Department
    RAbusePhone: +1-314-266-3638
    RAbuseEmail: abuse@hostingsolutionsint.com
    RAbuseRef: http://whois.arin.net/rest/poc/HAD15-ARIN

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 3 Errors
  • 4 Warnings
Ratio Text/Html
  • 0.6461312797946461
Message Error
  • Error Line 20, Column 18: there is no attribute "property"
    		<meta property="fb:admins" content="100002338337419" />

    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 144, Column 37: end tag for "ul" which is not finished
    					<ul id="playlist" class=""></ul>

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Warning Line 182, Column 31: cannot generate system identifier for general entity "B"
    									<option value='25'>R&B</option>

    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 182, Column 31: general entity "B" not defined and no default entity
    									<option value='25'>R&B</option>

    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 182, Column 32: reference not terminated by REFC delimiter
    									<option value='25'>R&B</option>

    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 182, Column 32: reference to entity "B" for which no system identifier could be generated
    									<option value='25'>R&B</option>

    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 182, Column 30: entity was defined here
    									<option value='25'>R&B</option>
  • Warning Line 188, Column 34: character "&" is the first character of a delimiter but occurred as data
    									<option value='31'>Rock & Roll</option>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 189, Column 35: character "&" is the first character of a delimiter but occurred as data
    									<option value='32'>Stage & Screen</option>

    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 219, Column 339: there is no attribute "allowTransparency"
    … overflow:hidden; width:341px; height:62px;" 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.

Visitor Analysis

Daily Visitor
  • 58 visits
Daily Visitor

In Page Analysis