Login Login on any IP | Recover | Contact Broblem ? Clear cookies ! ...

filelist.ro
  • Domain Name
    filelist.ro
  • Favicon
  • Google Page Rank
    2
  • Alexa Rank
    #2847
  • Page Size
    2.3 KB
  • Ip Address
    88.80.11.31
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 0 JPG, 0 PNG

Website Meta Analysis

  • Title
    FileList :: Login
  • Meta Keyword
  • Meta Description
    Login Login on any IP | Recover | Contact Broblem ? Clear cookies !

Technical Analysis

  • Webserver
    Apache/2.2.22 (Debian)
  • Ip Address
    88.80.11.31
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Thu, 05 Sep 2013 18:03:15 GMT
  • content-type: text/html
  • content-length: 781
  • connection: keep-alive
  • server: Apache/2.2.22 (Debian)
  • vary: Accept-Encoding
  • content-encoding: gzip
  • 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: filelist.ro
Registrar: ICI - ROTLD
Whois Server: http://pwhois.rotld.ro/static
Registrar Registrar URL: http://www.rotld.ro
Name Servers: ns6.linuxsecurity.us
Name Servers: ns5.linuxsecurity.us
Name Servers: ns2.linuxsecurity.us
Name Servers: ns4.linuxsecurity.us
Name Servers: ns.linuxsecurity.us
Name Servers: ns3.linuxsecurity.us
Domain Domain Status: OK

DNS Analysis


DNS servers
ns4.zoneedit.com [216.98.150.236]
ns3.zoneedit.com [76.74.236.21]

DNS Records

Answer records
filelist.ro SOA
server: ns3.zoneedit.com
email: soacontact@zoneedit.com
serial: 2012444348
refresh: 2400
retry: 360
expire: 1209600
minimum ttl: 300
7200s
filelist.ro A 88.80.11.31 300s
filelist.ro TXT v=spf1 a ptr ip4:93.114.41.222 ip4:93.114.41.223 ip4:86.120.13.0/24 ip4:88.80.2.0/26 ip4:88.80.11.0/26 ~all 300s
filelist.ro MX
preference: 20
exchange: mx.filelist.ro
300s
filelist.ro MX
preference: 10
exchange: mx2.filelist.ro
300s
filelist.ro NS  ns4.zoneedit.com 7200s
filelist.ro NS  ns3.zoneedit.com 7200s

Authority records
filelist.ro NS  ns4.zoneedit.com 7200s
filelist.ro NS  ns3.zoneedit.com 7200s

Additional records

IP 88.80.11.31 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 7 Errors
  • 4 Warnings
Ratio Text/Html
  • 0.8022024565861923
Message Error
  • Error Line 23, Column 134: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …t type='checkbox' name='unlock' value=1 /></span><span style='position:relativ…
  • Error Line 35, Column 16: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    	    <b><center>Broblem ? <a href=https://support.google.com/mail/bin/answer.py…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 35, Column 35: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    	    <b><center>Broblem ? <a href=https://support.google.com/mail/bin/answer.py…
  • Error Line 35, Column 42: NET-enabling start-tag not immediately followed by null end-tag
    …  <b><center>Broblem ? <a href=https://support.google.com/mail/bin/answer.py?h…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Warning Line 35, Column 87: cannot generate system identifier for general entity "answer"
    …t.google.com/mail/bin/answer.py?hl=en&answer=32050>Clear cookies !</a></center…

    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 35, Column 87: general entity "answer" not defined and no default entity
    …t.google.com/mail/bin/answer.py?hl=en&answer=32050>Clear cookies !</a></center…

    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 35, Column 93: reference not terminated by REFC delimiter
    …ogle.com/mail/bin/answer.py?hl=en&answer=32050>Clear cookies !</a></center></b>

    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 35, Column 93: reference to entity "answer" for which no system identifier could be generated
    …ogle.com/mail/bin/answer.py?hl=en&answer=32050>Clear cookies !</a></center></b>

    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 35, Column 86: entity was defined here
    …rt.google.com/mail/bin/answer.py?hl=en&answer=32050>Clear cookies !</a></cente…
  • Error Line 35, Column 118: end tag for element "a" which is not open
    …ogle.com/mail/bin/answer.py?hl=en&answer=32050>Clear cookies !</a></center></b>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

Visitor Analysis

Daily Visitor
  • 38.500 visits