Skip to main content
About

Why is-cool-me exists

is-cool-me was founded and is maintained by Mayank Baswal to make practical subdomain access available to builders who need reliable DNS controls without unnecessary friction.

Last updated: May 2026

Project mission

Our mission is to provide dependable, free subdomains under is-pro.dev and is-into.tech for personal projects, open-source work, and community services. We focus on operational clarity: users should understand what records exist, why they exist, and what happens when policy boundaries are crossed.

Why this project exists

Many first-time deployments fail on DNS details, not application code. is-cool-me exists to remove that barrier while keeping enough guardrails to prevent the platform from being abused as a low-cost attack surface.

DNS and subdomain philosophy

  • User control: DNS records should remain explicit and editable.
  • Predictability: avoid hidden behavior that surprises operators in production.
  • Documentation tied to reality: guides are based on recurring support and moderation incidents.

Security and abuse prevention principles

  • Evidence-first moderation with clear escalation paths.
  • Rapid containment for active phishing and malware campaigns.
  • Appeal paths for disputed decisions.

Safety principle: we may suspend active harmful subdomains quickly to reduce user harm while a full review is still in progress.

Reliability goals

Reliability includes operational consistency, accurate docs, and incident follow-through. Mayank’s reliability philosophy is to treat DNS as production infrastructure: changes must be reversible, verification must be explicit, and documentation must reflect real platform behavior.

Maintainer transparency

Mayank Baswal is the primary technical maintainer for is-cool-me. He owns platform reliability decisions, DNS safety policy implementation, and production change stewardship across the service.

Technical guidance is published from operational experience: DNS incident reviews, resolver behavior debugging, certificate failures, and abuse-handling workflows observed in production support and moderation queues.

Community focus

We build for people shipping real projects. Community reports directly shape what we document next and how we improve abuse handling, support quality, and platform safeguards.