m4marry.com has Alexa Rank 49.183 and Google Page Rank is 4

Domain Name m4marry.com
Favicon m4marry.com
Google Page Rank 4
Alexa Rank #49183
Page Size 255 B
Ip Address
Heading H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
Images 0 GIF, 0 JPG, 0 PNG

Website Meta Analysis

Title Kerala's Biggest Malayalee Matrimonial Site
Meta Keyword
Meta Description

Technical Analysis

Webserver Microsoft-IIS/6.0
Ip Address
Domain Age
Javascript Library
Language used HTML, CSS, Javascript

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

HTML Analysis

  • content-length: 244
  • content-type: text/html
  • content-location: http://m4marry.com/m4marrynew.htm
  • last-modified: Fri, 16 Aug 2013 18:44:29 GMT
  • accept-ranges: bytes
  • etag: "db62bea3b09ace1:d92f"
  • server: Microsoft-IIS/6.0
  • x-powered-by: ASP.NET
  • date: Sat, 17 Aug 2013 05:23:08 GMT
  • connection: close
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA

Malayala Manorama
P B No 26, KK Road,

Domain Name: M4MARRY.COM

Administrative Contact, Technical Contact:
Malayala Manorama email
P B No 26, KK Road,
481-2563646 fax: 481-2565399

Record expires on 12-Sep-2013.
Record created on 12-Sep-2007.
Database last updated on 8-Sep-2012 05:08:31 EDT.

Domain servers in listed order:


IP Analysis

Country Code :
Country Code3 :
Country Name :
City :
Continent Code :
Latitude :
Longitude :

No whois ip data for

In Page Analysis

Traffic Analysis

Magestic Backlinks

Daily Ranks

Rank Trend

Visitor Trend

Bounce Trend

HTML Analysis

HTML validation
  • 3 Errors
  • 5 Warnings
Ratio Text/Html


Message Error
  • Error Line 1, Column 1: no document type declaration; implying "<!DOCTYPE HTML SYSTEM>"

    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 103: NET-enabling start-tag requires SHORTTAG YES
    …CONTENT="0; URL=http://www.m4marry.com/cgi-bin/m4marry.dll/matrimony/home.do"/>

    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 7: end tag for element "HEAD" which is not open

    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 7, Column 6: document type does not allow element "BODY" here

    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

4.317 visits