Kostenlos fernsehen im Internet. Live Streams aller wichtiger Sender, TELE Guide, Videothek, Radio und vielem mehr. Wilmaa, das Schweizer Online TV im Browser. ...

wilmaa.com
  • Domain Name
    wilmaa.com
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #46571
  • Page Size
    4 KB
  • Ip Address
    79.125.22.201
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 0 JPG, 7 PNG

Website Meta Analysis

  • Title
    Wilmaa - Das Schweizer Online TV - kostenlos als Live Stream schauen
  • Meta Keyword
  • Meta Description
    Kostenlos fernsehen im Internet. Live Streams aller wichtiger Sender, TELE Guide, Videothek, Radio und vielem mehr. Wilmaa, das Schweizer Online TV im Browser.

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    79.125.22.201
  • Domain Age
    4 Years, 8 Months, 8 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: Apache
  • content-type: text/html
  • etag: "07fdeb8283951324a651eeac5515d302:1346925085"
  • vary: Accept-Encoding
  • content-encoding: gzip
  • expires: Thu, 27 Jun 2013 11:35:21 GMT
  • cache-control: max-age=0, no-cache, no-store
  • pragma: no-cache
  • date: Thu, 27 Jun 2013 11:35:21 GMT
  • content-length: 1300
  • connection: keep-alive
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA


Registrant:
Gabathuler, Thomas
Gartenhof Medien GmbH
Gartenhofstrasse 17
Zurich, ZH CH-8004
CH

Domain Name: WILMAA.COM

Administrative Contact:
Gabathuler, Thomas email
Swisscom Event & Media Solutions AG
Gartenhofstrasse 15
Zurich, ZH CH-8004
CH
+41 44 446 3060


Record expires on 13-Oct-2014.
Record created on 13-Oct-2008.
Database last updated on 19-Nov-2012 22:24:53 EST.

Domain servers in listed order:

NS1.SOLUTIONPARK.CH 193.73.184.21
NS2.SOLUTIONPARK.CH 212.126.163.253

This whois service currently only reflects registrations
made through NameSecure as a registrar in the .com and .net
top-level domains.

DNS Analysis


DNS servers
ns1.solutionpark.ch [193.73.184.21]
ns2.solutionpark.ch [195.226.19.112]


DNS Records

Answer records
wilmaa.com SOA
server: ns1.solutionpark.ch
email: hostmaster@solutionpark.ch
serial: 2013021301
refresh: 28800
retry: 7200
expire: 604800
minimum ttl: 7200
86400s
wilmaa.com A 193.73.184.141 86400s
wilmaa.com TXT v=spf1 include:_spf.google.com ~all include:sendgrid.net ~all 86400s
wilmaa.com TXT google-site-verification=mN9TvJkjUukragNlr4o2pp14FIJeQZD1yumFk3znlEE 86400s
wilmaa.com MX
preference: 5
exchange: ALT1.ASPMX.L.GOOGLE.com
86400s
wilmaa.com MX
preference: 5
exchange: ALT2.ASPMX.L.GOOGLE.com
86400s
wilmaa.com MX
preference: 10
exchange: ASPMX2.GOOGLEMAIL.com
86400s
wilmaa.com MX
preference: 10
exchange: ASPMX3.GOOGLEMAIL.com
86400s
wilmaa.com MX
preference: 1
exchange: ASPMX.L.GOOGLE.com
86400s
wilmaa.com NS  ns1.solutionpark.ch 86400s
wilmaa.com NS  ns2.solutionpark.ch 86400s

Authority records

Additional records
ns1.solutionpark.ch A 193.73.184.21 600s
ns2.solutionpark.ch A 195.226.19.112 600s

IP 79.125.22.201 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 7 Errors
  • 3 Warnings
Ratio Text/Html
  • 0.5256064690026954
Message Error
  • Error Line 1, Column 1: no document type declaration; implying "<!DOCTYPE HTML SYSTEM>"
    <html>

    The checked page did not contain a document type ("DOCTYPE") declaration. The Validator has tried to validate with a fallback DTD, but this is quite likely to be incorrect and will generate a large number of incorrect error messages. It is highly recommended that you insert the proper DOCTYPE declaration in your document -- instructions for doing this are given above -- and it is necessary to have this declaration before the page can be declared to be valid.

  • Warning Line 4, Column 198: NET-enabling start-tag requires SHORTTAG YES
    …eothek, Radio und vielem mehr. Wilmaa, das Schweizer Online TV im Browser. " />

    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 6, Column 72: document type does not allow element "META" here
    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">

    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 23: document type does not allow element "STYLE" here
    <style type="text/css">

    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 59, Column 7: end tag for element "HEAD" which is not open
    </head>

    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.

  • Error Line 60, Column 6: document type does not allow element "BODY" here
    <body>

    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 70, Column 49: there is no attribute "HEIGHT"
    …able id="Table_01" width="943" height="520" border="0" cellpadding="0" cellspa…

    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 103, Column 15: end tag for "TR" which is not finished
          <tr></tr>

    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.

Visitor Analysis

Daily Visitor
  • 4.433 visits
Daily Visitor