Felhasználónév Jelszó Bejelentkezés Problémák a belépéssel? Jelszó emlékeztetőért kattints ide Új profil regisztrálásához kattints ide ...

bithorlo.net
  • Domain Name
    bithorlo.net
  • Favicon
  • Google Page Rank
    0
  • Alexa Rank
    #60700
  • Page Size
    68 B
  • Ip Address
    80.82.209.126
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 0 JPG, 0 PNG

Website Meta Analysis

  • Title
    Bejelentkezés
  • Meta Keyword
  • Meta Description
    Felhasználónév Jelszó Bejelentkezés Problémák a belépéssel? Jelszó emlékeztetőért kattints ide Új profil regisztrálásához kattints ide

Technical Analysis

  • Webserver
    nginx/0.9.4
  • Ip Address
    80.82.209.126
  • Domain Age
    4 Months, 18 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from bithorlo.net.

HTML Analysis

  • server: nginx/0.9.4
  • date: Mon, 11 Mar 2013 15:12:12 GMT
  • content-type: text/html; charset=iso-8859-2
  • connection: keep-alive
  • vary: Accept-Encoding
  • x-powered-by: PHP/5.2.17
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • content-language: hu
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA

Registration Service Provided By: F.D.W. HOSTING GROUP
Contact: +001.3525567702
Website: https://www.fdwhostingco.com

Domain Name: BITHORLO.NET

Registrant:
Deathlord
Burato KFT. ( email )
Kossuth Ferenc 33-35
Cegled
Pest,2700
HU
Tel. +36.36306125220

Creation Date: 11-Oct-2012
Expiration Date: 11-Oct-2014

Domain servers in listed order:
ns01.deathlord.eu
ns02.deathlord.eu


Administrative Contact:
Deathlord
Burato KFT. ( email )
Kossuth Ferenc 33-35
Cegled
Pest,2700
HU
Tel. +36.36306125220

Technical Contact:
Deathlord
Burato KFT. ( email )
Kossuth Ferenc 33-35
Cegled
Pest,2700
HU
Tel. +36.36306125220

Billing Contact:
Deathlord
Burato KFT. ( email )
Kossuth Ferenc 33-35
Cegled
Pest,2700
HU
Tel. +36.36306125220

Status:LOCKED
Note: This Domain Name is currently Locked. In this status the domain
name cannot be transferred, hijacked, or modified. The Owner of this
domain name can easily change this status from their control panel.
This feature is provided as a security measure against fraudulent domain name hijacking.

The data in this whois database is provided to you for information purposes only,
that is, to assist you in obtaining information about or related
to a domain name registration record. We make this information available "as is",
and do not guarantee its accuracy. By submitting a whois query, you agree that you will
use this data only for lawful purposes and that, under no circumstances will you use this data to:
(1) enable high volume, automated, electronic processes that stress
or load this whois database system providing you this information; or
(2) allow, enable, or otherwise support the transmission of mass unsolicited,
commercial advertising or solicitations via direct mail, electronic mail, or by telephone.
The compilation, repackaging, dissemination or other use of this data is expressly prohibited without
prior written consent from us. The Registrar of record is NetEarth One, Inc..
We reserve the right to modify these terms at any time.
By submitting this query, you agree to abide by these terms.

DNS Analysis


DNS servers
ns01.deathlord.eu [68.233.243.9]
ns02.deathlord.eu [80.82.209.126]


DNS Records

Answer records
bithorlo.net SOA
server: ns01.deathlord.eu
email: halaszk@deathlord.eu
serial: 2012101500
refresh: 28800
retry: 7200
expire: 1209600
minimum ttl: 86400
86400s
bithorlo.net MX
preference: 10
exchange: mail.bithorlo.net
86400s
bithorlo.net A 80.82.209.126 86400s
bithorlo.net NS  ns01.deathlord.eu 86400s
bithorlo.net NS  ns02.deathlord.eu 86400s

Authority records

Additional records
mail.bithorlo.net A 80.82.209.126 86400s
ns01.deathlord.eu A 68.233.243.9 86400s
ns02.deathlord.eu A 80.82.209.126 86400s

IP 80.82.209.126 Analysis

  • Country Code
  • Country Code3
  • Country Name
  • City
  • Continent Code
  • Latitude
  • Longitude
  • No whois ip data for 80.82.209.126

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 6 Errors
  • 6 Warnings
Ratio Text/Html
  • 0.5735294117647058
Message Error
  • Error Line 1, Column 1: no document type declaration; will parse without validation
    <head><title>Bejelentkezés</title></head>

    The document type could not be determined, because the document had no correct DOCTYPE declaration. The document does not look like HTML, therefore automatic fallback could not be performed, and the document was only checked against basic markup syntax.

    Learn how to add a doctype to your document from our FAQ, or use the validator's Document Type option to validate your document against a specific Document Type.

  • Error Line 2, Column 7: document type does not allow element "STYLE" here
    <style>

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 71, Column 5: invalid comment declaration: found character "<" outside comment but inside comment declaration
    <!--<![endif]-->

    Check that you are using a proper syntax for your comments, e.g: <!-- comment here -->. This error may appear if you forget the last "--" to close one comment, and later open another.

  • Info Line 62, Column 1: comment declaration started here
    <!--[if IE 9 ]> 
  • Error Line 71, Column 6: character data is not allowed here
    <!--<![endif]-->

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 81, Column 5: invalid comment declaration: found character "<" outside comment but inside comment declaration
    <!--<![endif]-->

    Check that you are using a proper syntax for your comments, e.g: <!-- comment here -->. This error may appear if you forget the last "--" to close one comment, and later open another.

  • Info Line 72, Column 1: comment declaration started here
    <!--[if IE 8 ]> 
  • Error Line 82, Column 56: document type does not allow element "FORM" here
    <form method="post" action="takelogin.php" name="login">

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Warning Line 92, Column 195: NET-enabling start-tag requires SHORTTAG YES
    …bmit" style="position: absolute; display:none; width: 1px; height: 1px;"/></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 101, Column 5: NET-enabling start-tag requires SHORTTAG YES
    <br />Jelszó emlékeztetőért kattints <a href="./recover.php" class="login">ide<…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 102, Column 5: NET-enabling start-tag requires SHORTTAG YES
    <br />Új profil regisztrálásához kattints <a href="./signup.php" class="login">…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

Visitor Analysis

Daily Visitor
  • 2.333 visits
Daily Visitor