is-cod.in documentation
Put your project online without managing the DNS machinery.
Request a hostname under an available domain, tell us where it should point, and follow the request from analysis to publication.
Submit
Choose a domain and add the record your project needs.
Review
Rules and risk signals check configuration and intent.
Publish
Safe records publish; uncertain requests go to an admin.
01
Getting started
There is no password to create or email verification step. Sign in with GitHub or Google, then submit your first request from the dashboard.
- 1Create an account with GitHub or Google.
- 2Select one of the domains currently available on the platform.
- 3Choose a unique subdomain label and DNS record type.
- 4Enter the destination value, check the preview, and submit.
- 5Watch the status in your dashboard and respond if an admin requests changes.
02
Supported record types
Availability can vary by managed domain. The form will show the types currently accepted for your selection.
APoint a hostname to an IPv4 address.
76.76.21.21AAAAPoint a hostname to an IPv6 address.
2001:db8::1CNAMEAlias a hostname to another hostname.
cname.vercel-dns.comMXDirect email to a mail server.
10 mail.example.comTXTPublish verification or policy text.
google-site-verification=...project.example.com, not https://project.example.com/path.03
Review and publication
Every request is scored by the platform's local safety engine before it reaches Cloudflare. Low-risk requests can proceed automatically; suspicious or ambiguous ones wait for a human decision.
What checks consider
- Record syntax and destination validity
- Restricted or misleading subdomain names
- Conflicting records and unsafe destinations
- Account history and recent submission velocity
Manual review
Manual review does not mean the request is rejected. It means the automated result was not confident enough to publish without an administrator checking the context.
Analyzing
Technical validation and safety checks are running.
Publishing
The request passed review and is being sent to the DNS provider.
Active
The provider accepted the record and it is live.
Manual review
An administrator needs to inspect the request before publishing.
Rejected or failed
The request was declined or the provider operation did not finish.
04
Troubleshooting
Why is my request in manual review?
A rule or risk signal needs an administrator to confirm the request. Check the dashboard for notes; you do not need to submit duplicates.
Why does the record not resolve yet?
First confirm the status is Active. DNS caches may continue serving an older answer until its TTL expires, so changes are not always visible immediately.
Why was my value rejected?
The destination may use the wrong format, conflict with another record, or violate a domain policy. Recheck the examples above and the message attached to the request.
Can I use the subdomain for anything?
No. Projects must follow the Terms of Service. Requests connected to phishing, malware, impersonation, spam, or other abuse are removed.