Check server response of

Server response
NS records
Whois domain
Response headers
Request headers
Raw HTML code
200 OK - wazdi.com
HTTP Status: 200
User-Agent: Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; [email protected])
Date: Sun, 11 May 2025 06:15:21 GMT
Server: Apache
Upgrade: h2,h2c
Connection: Upgrade
Last-Modified: Tue, 04 Feb 2025 11:45:21 GMT
Accept-Ranges: bytes
Content-Length: 6416
Vary: Accept-Encoding
Content-Type: text/html

HTTP Code 200 OK

200 http status code is a standard successful HTTP server response. It means that the client’s request (e.g., from a browser) was successfully processed, and the server is delivering the requested data.

When is Code 200 used?

  • When loading a web page
  • When successfully receiving an API response
  • When processing a form or another HTTP request

What does Code 200 mean for the user?

The user receives content without errors, and the page or application functions properly. If Code 200 is accompanied by data, the browser or program processes and displays it to the user.

GET / HTTP/1.1
Host: wazdi.com
Accept: */*
User-Agent: Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; [email protected])
<!DOCTYPE html>
<html lang="en">
<head>
    <meta charset="UTF-8">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <title>PayNet Limited | MPoC-Certified SoftPOS Solutions</title>
    <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/6.0.0/css/all.min.css">
    <style>
        :root {
            --primary: #002A5C;
            --accent: #00B894;
            --dark: #1A1A1A;
            --light: #F8F9FA;
        }

        * {
            box-sizing: border-box;
            margin: 0;
            padding: 0;
            font-family: 'Segoe UI', sans-serif;
        }

        body {
            line-height: 1.6;
            color: var(--dark);
        }

        /* Navigation */
        .navbar {
            background: var(--primary);
            padding: 1rem 5%;
            position: fixed;
            width: 100%;
            top: 0;
            display: flex;
            justify-content: space-between;
            align-items: center;
        }

        .logo {
            height: 40px;
        }

        /* Hero Section */
        .hero {
            padding: 120px 5% 60px;
            background: linear-gradient(rgba(0,42,92,0.9), rgba(0,42,92,0.9)),
                        url('pos-bg.jpg') center/cover;
            color: white;
            text-align: center;
        }

        /* Features Grid */
        .features {
            display: grid;
            grid-template-columns: repeat(auto-fit, minmax(300px, 1fr));
            gap: 2rem;
            padding: 4rem 5%;
            background: var(--light);
        }

        .feature-card {
            background: white;
            padding: 2rem;
            border-radius: 8px;
            box-shadow: 0 4px 6px rgba(0,0,0,0.1);
            text-align: center;
        }

        .feature-icon {
            font-size: 2.5rem;
            color: var(--accent);
            margin-bottom: 1rem;
        }

        /* Architecture Section */
        .architecture {
            padding: 4rem 5%;
            background: white;
            text-align: center;
        }

        .arch-diagram {
            max-width: 800px;
            margin: 2rem auto;
        }

        /* Compliance Section */
        .compliance {
            background: var(--primary);
            color: white;
            padding: 4rem 5%;
            text-align: center;
        }

        .badge-grid {
            display: grid;
            grid-template-columns: repeat(auto-fit, minmax(150px, 1fr));
            gap: 2rem;
            margin: 2rem 0;
        }

        /* Contact Form */
        .contact {
            padding: 4rem 5%;
            background: var(--light);
        }

        .form-container {
            max-width: 600px;
            margin: 0 auto;
        }
    </style>
</head>
<body>
    <nav class="navbar">
        <img src="logo.png" class="logo" alt="PayNet Logo">
        <div class="nav-links">
            <a href="#features" style="color: white; text-decoration: none; margin-left: 2rem;">Features</a>
            <a href="#security" style="color: white; text-decoration: none; margin-left: 2rem;">Security</a>
            <a href="#contact" style="color: white; text-decoration: none; margin-left: 2rem;">Contact</a>
        </div>
    </nav>

    <section class="hero">
        <h1 style="font-size: 2.5rem; margin-bottom: 1.5rem;">Transform Mobile Devices into Secure POS Terminals</h1>
        <p style="font-size: 1.2rem; margin-bottom: 2rem;">MPoC-Certified SoftPOS Solution with PCI-DSS Level 1 Compliance</p>
        <div style="margin-top: 2rem;">
            <a href="#contact" class="cta-button">Request Demo</a>
            <a href="#features" class="cta-button" style="background: transparent; border: 2px solid white;">Learn More</a>
        </div>
    </section>

    <section id="features" class="features">
        <div class="feature-card">
            <i class="fas fa-shield-alt feature-icon"></i>
            <h3>End-to-End Encryption</h3>
            <p>Secure transaction processing with AES-256 encryption at every stage</p>
        </div>
        <div class="feature-card">
            <i class="fas fa-mobile-alt feature-icon"></i>
            <h3>Device Agnostic</h3>
            <p>Works on iOS, Android, and HarmonyOS devices with NFC capability</p>
        </div>
        <div class="feature-card">
            <i class="fas fa-tools feature-icon"></i>
            <h3>Easy Integration</h3>
            <p>RESTful APIs with comprehensive developer documentation</p>
        </div>
    </section>

    <section class="architecture">
        <h2 style="margin-bottom: 1rem;">Solution Architecture</h2>
        <p style="max-width: 800px; margin: 0 auto;">Our 3-tier security architecture ensures complete protection from device to processor</p>
        <img src="architecture-diagram.png" class="arch-diagram" alt="Security Architecture Diagram">
    </section>

    <section class="compliance">
        <h2 style="margin-bottom: 2rem;">Certified & Compliant</h2>
        <div class="badge-grid">
            <div>
                <img src="mpoc-badge.png" alt="MPoC Certified" style="height: 80px;">
                <p>MPoC Certified Solution</p>
            </div>
            <div>
                <img src="pci-dss-badge.png" alt="PCI DSS Level 1" style="height: 80px;">
                <p>PCI DSS Level 1 Service Provider</p>
            </div>
        </div>
    </section>

    <section id="contact" class="contact">
        <div class="form-container">
            <h2>Start Your Integration Today</h2>
            <form style="margin-top: 2rem;">
                <input type="text" placeholder="Organization Name" style="width: 100%; padding: 12px; margin: 8px 0;">
                <input type="email" placeholder="Email Address" style="width: 100%; padding: 12px; margin: 8px 0;">
                <textarea placeholder="Message" style="width: 100%; padding: 12px; margin: 8px 0; height: 120px;"></textarea>
                <button type="submit" style="background: var(--accent); color: white; padding: 12px 24px; border: none; cursor: pointer;">Submit Inquiry</button>
            </form>
        </div>
    </section>
</body>
</html>                               

Whois info of domain

Domain Name: WAZDI.COM
Registry Domain ID: 2660194499_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.name.com
Registrar URL: http://www.name.com
Updated Date: 2025-01-15T07:57:12Z
Creation Date: 2021-12-07T21:40:53Z
Registry Expiry Date: 2026-12-07T21:40:53Z
Registrar: Name.com, Inc.
Registrar IANA ID: 625
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: 7202492374
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: HGNS1.HOSTGATOR.COM
Name Server: HGNS2.HOSTGATOR.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2025-05-11T06:15:14Z <<<
For more information on Whois status codes, please visit https://icann.org/epp
NOTICE: The expiration date displayed in this record is the date the
TERMS OF USE: You are not authorized to access or query our Whois
by the following terms of use: You agree that you may use this Data only
to: (1) allow, enable, or otherwise support the transmission of mass