eJobs iti ofera peste 16.000 de locuri de munca, disponibile in tara si in strainatate. Intra pe eJobs.ro, cel mai mare portal de joburi din Romania! ...

ejobs.ro
  • Domain Name
    ejobs.ro
  • Favicon
  • Google Page Rank
    6
  • Alexa Rank
    #13121
  • Page Size
    107.8 KB
  • Ip Address
    193.189.99.226
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    3 GIF, 12 JPG, 44 PNG

Website Meta Analysis

  • Title
    Locuri de munca - eJobs
  • Meta Keyword
    locuri de munca, angajari, joburi.
  • Meta Description
    eJobs iti ofera peste 16.000 de locuri de munca, disponibile in tara si in strainatate. Intra pe eJobs.ro, cel mai mare portal de joburi din Romania!

Technical Analysis

  • Webserver
    Concealed by Juniper Networks DX
  • Ip Address
    193.189.99.226
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from ejobs.ro.

HTML Analysis

  • date: Fri, 08 Mar 2013 09:57:53 GMT
  • 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
  • vary: Accept-Encoding, User-Agent
  • content-encoding: gzip
  • content-length: 19034
  • content-type: text/html
  • server: Concealed by Juniper Networks DX
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA

% Whois Server Version 2.17/2009-12-18 - whois.rotld.ro
% Rights restricted by copyright.
% Specifically, this data MAY ONLY be used for Internet operational
% purposes. It may not be used for targeted advertising or any
% other purpose.
% Este INTERZISA folosirea datelor de pe acest server in oricare
% alt scop decat operarea retelei. In special este INTERZISA
% folosirea lor in scopuri publicitare.
% Top Level Domain : ro
% Maintainance : www.rotld.ro
Domain Domain Name: ejobs.ro
Registrar: ICI - ROTLD
Whois Server: http://pwhois.rotld.ro/static
Registrar Registrar URL: http://www.rotld.ro
Name Servers: ns1.globalis.ro
Name Servers: ns.globalis.ro
Domain Domain Status: OK

DNS Analysis


DNS servers
ns1.globalis.ro
ns.globalis.ro


DNS Records

Answer records
ejobs.ro TXT v=spf1 a mx ip4:193.189.99.192/26 -all 3600s
ejobs.ro SOA
server: ns.globalis.ro
email: noc@globalis.ro
serial: 2012100900
refresh: 21600
retry: 7200
expire: 604800
minimum ttl: 86400
86400s
ejobs.ro MX
preference: 10
exchange: mail.ejobs.ro
86400s
ejobs.ro A 193.189.99.226 86400s
ejobs.ro 99 [39 bytes] 86400s
ejobs.ro NS  ns1.globalis.ro 86400s
ejobs.ro NS  ns.globalis.ro 86400s

Authority records

Additional records
ns.globalis.ro A 193.189.98.1 86400s
mail.ejobs.ro A 193.230.138.180 86400s
ns1.globalis.ro A 193.189.99.1 86400s

IP 193.189.99.226 Analysis

  • Country Code
    RO
  • Country Code3
    ROU
  • Country Name
    Romania
  • City
    EU
  • Continent Code
    46° North
  • Latitude
    25.
  • Longitude
  • No whois ip data for 193.189.99.226

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 27 Errors
  • 8 Warnings
Ratio Text/Html
  • 0.7853093016936872
Message Error
  • Warning Line 4, Column 58: NET-enabling start-tag requires SHORTTAG YES
    				<meta http-equiv="X-UA-Compatible" content="IE=edge" />

    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 5, Column 80: NET-enabling start-tag requires SHORTTAG YES
    …17103177476157742587" rel="publisher" /><meta name="keywords" content="locuri …

    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.

  • Error Line 5, Column 80: document type does not allow element "LINK" here
    …17103177476157742587" rel="publisher" /><meta name="keywords" content="locuri …

    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 5, Column 148: document type does not allow element "META" here
    …ublisher" /><meta name="keywords" content="locuri de munca, angajari, joburi.">

    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 6, Column 82: document type does not allow element "META" here
    …	<META name="verify-v1" content="q2Q3y3Pw6qwJoi/B2tOJV8JnOOW0EN2tR/kkneW8O9k=">

    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 7, Column 189: document type does not allow element "META" here
    …in strainatate. Intra pe eJobs.ro, cel mai mare portal de joburi din Romania!">

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

Visitor Analysis

Daily Visitor
  • 12.833 visits
Daily Visitor