Domain, hosting and infrastructure
Domain names, DNS records, SSL certificates, email routing, backups and monitoring: the invisible side of a website that stops everything when it breaks. I take that load on completely.
In my day job I build the infrastructure behind banking and defense systems. The same approach applies to a small brochure site: every configuration is written down, so nobody has to guess later.
Scope — what's included
-
Domain names
Choosing, registering and tracking renewal of the right domain. Registration is in your name — the domain is always your property, never held hostage with me.
-
DNS and Cloudflare
DNS records, management through Cloudflare, cache and security settings. www and http addresses are redirected to a single address, so the site lives at one canonical URL.
-
SSL and security headers
HTTPS enforced, HSTS enabled. Content-Security-Policy, X-Frame-Options and friends close off framing and content injection.
-
Business email
Addresses on your own domain (name@yourcompany.com) and forwarding. SPF, DKIM and DMARC records are set so your mail does not land in spam.
-
Hosting
Static sites hosted on Cloudflare: fast from anywhere in the world, no collapse under traffic spikes, near-zero cost. For projects needing a server, we pick the right host together.
-
Monitoring and continuity
Uptime monitoring plus certificate and domain renewal tracking. When something breaks, I usually know before you do.
How we proceed
-
1. Document what exists
Who holds the domain, where DNS lives, how email flows — all of it gets identified. On most projects I inherit, this part is a mess.
-
2. Migration plan
An order of operations for a zero-downtime move. Email and the site do not move at the same time; everything is tested first.
-
3. Setup
DNS, SSL, headers and email records are configured. Every setting is documented and handed to you in writing.
-
4. Handover
All accounts are opened in your name and access is yours. You can hand them to someone else any day; you are not locked to me.
Why me
- This site runs on Cloudflare Workers, alongside a separate Worker that moves www and plain-http traffic to the canonical address.
- In my day job I build enterprise delivery pipelines with Docker, GitLab CI/CD and Vault.
- The Content-Security-Policy on this site is checked automatically at build time: a violation stops the release.
- kelimely.com, kelimelab.com and the client site docdryasemindogan.com all run on the same infrastructure discipline.
Frequently asked
My domain is with another company — can you move it?
Yes. We can also manage it without moving — pointing the DNS is often enough. If you do want to transfer, I run the process with no downtime.
What does hosting cost?
For a static brochure site, hosting is close to zero on most projects; the real cost is the annual domain fee. If the project needs a server, I tell you the cost up front.
What happens if my site goes down?
Static sites have no server to go down; content is served from machines spread around the world. I still set up uptime monitoring, and handling any incident is on me.
Whose name are the accounts in?
Yours. You own the domain, hosting and email accounts; I work with administrator access. If we part ways, you do not have to migrate anything.