DNS repair
A, CNAME, MX, TXT, SPF, DKIM, DMARC, nameserver, TTL, and propagation issues reviewed.
Hosting support
DNS, SSL and website hosting support
Fix domain, DNS, SSL, Cloudflare, redirects, hosting control panel, server, email-record, and launch issues that can make a healthy website look broken.
- DNS, SSL, redirects, Cloudflare, hosting, and email-record troubleshooting
- Website launches, host moves, domain changes, and migration support
- WordPress, PHP, static, WooCommerce, and custom app hosting checks
- Clear rollback and validation steps before risky cutovers
What you get
How DNS, SSL and website hosting support actually works
Concrete deliverables — no vague SaaS jargon. Each engagement is sized to your business and reviewed monthly.
SSL fixes
Expired certificates, mixed content, HTTPS redirects, HSTS, and Cloudflare SSL mode issues.
Hosting checks
Control panels, disk space, PHP versions, permissions, logs, backups, and resource limits checked.
Redirects and launch
301s, www/apex choices, staging cutovers, Search Console, and launch validation.
Email records
Protect email delivery during DNS or hosting changes by checking MX and authentication records.
Runbook
Document who controls domain, DNS, hosting, email, CDN, and SSL so future support is faster.
From experience
What we check after a DNS or certificate change
A “website-only” DNS change is how email and embedded tools quietly break.
-
Certificate installs and rekeys
Issuer problems, admin-only certificate warnings, and application pools that cannot read the new cert.
-
Mail after DNS
SPF, DKIM, and the mailbox that receives the website form.
-
Hard-coded http after HTTPS
Plugins that still request insecure scripts, so listings or widgets vanish on the encrypted site.
-
Nameserver reversions
A registrar putting obsolete nameservers back — the CMS cannot fix that.
Patterns drawn from our team’s years of agency support work.
From the support desk
Situations our team has handled
Anonymized cases from our team’s years of agency support work: what the owner saw, what was actually wrong, and what we check first because of it.
Listings vanished after the move to HTTPS
- What they saw
- Embedded registration listings disappeared when the site switched to HTTPS.
- What was wrong
- An integration plugin loaded its script from a hard-coded http:// address, which browsers block on secure pages.
- Outcome
- We corrected the address and the listings came back.
Takeaway: The certificate is usually fine. Look for old http:// links in plugins and embeds first, and ask the vendor to fix it at the source so the next update does not undo it.
Certificate had to be rekeyed, not reinstalled
- What they saw
- The live site needed a replacement SSL certificate after a problem at the issuer.
- What was wrong
- Reinstalling the existing certificate was not enough. It had to be rekeyed.
- Outcome
- The rekeyed certificate was installed and handed over for an independent check.
Takeaway: After any certificate change, test from outside your own network and in more than one browser.
Client names and identifying details removed. Outcomes are described as they happened, including the ones that needed follow-up.
After every DNS change
DNS, SSL, and email check
A DNS change that “only touches the website” still breaks mail more often than people expect. Test both.
Print this page to keep a paper copy beside the work.
- 1 Export the current DNS zone before you edit it.
- 2 Change one thing at a time: website records, or mail records, not both in the same unreviewed pass.
- 3 After a website change, wait for TTL and confirm A/AAAA/CNAME, HTTPS, HSTS, and redirect behaviour.
- 4 After any change, send a message from the website form and from the business mailbox.
- 5 Check SPF, DKIM, and DMARC still authorize the servers that actually send.
- 6 If you moved to HTTPS, search the codebase and plugins for hard-coded http:// asset or embed URLs.
- 7 If a certificate warning appears only in admin, check whether the application pool or the host user can read the new certificate.
- 8 If nameservers keep reverting, the registrar — not the CMS — is the incident.
Mixed content and vanished embeds after an HTTPS move are usually hard-coded insecure URLs, not a “SSL is broken” mystery.
Access usually needed
Domain registrar, DNS or Cloudflare, hosting panel, SSL provider if separate, and email provider access are usually enough. For launches, we also need the current and destination hosting details.
Symptoms we fix
A strong fit when
- The website says not secure, has an expired certificate, or redirects incorrectly
- A DNS, nameserver, or Cloudflare change made the site or email fail
- A hosting migration needs planning, cutover, and validation
- Email broke after changing website hosting or DNS records
- The host says DNS is wrong and the registrar says hosting is wrong
- You need a clean map of domain, DNS, hosting, email, and CDN ownership
Our process
How DNS and hosting support works
-
1
Map ownership
Identify registrar, DNS host, CDN, web host, email provider, and SSL authority.
-
2
Check records
Review active DNS, propagation, SSL, redirects, nameservers, MX, and authentication records.
-
3
Plan change
Lower TTL where useful, confirm rollback, and document exactly what will change.
-
4
Apply fix
Correct records, SSL mode, redirects, hosting settings, or control-panel configuration.
-
5
Validate
Check apex, www, HTTPS, forms, email, Search Console, and mobile access.
-
6
Document
Leave a practical map of services and credentials owners for future support.
Trusted technologies we support
Related services
Pairs well with
WordPress hosting
Managed hosting with WAF and backups.
Learn moreWordPress migration
Low-downtime host moves.
Learn moreContact form fixes
SMTP, DNS, and form delivery repair.
Learn moreChanged DNS? Check email
Why a website-only DNS edit is how mail and embeds break.
Learn moreFAQ
Frequently asked questions
Can you fix SSL certificate warnings?
Yes. We review certificate status, HTTPS redirects, mixed content, Cloudflare modes, and hosting SSL settings.
Can you help without moving hosting?
Yes. Many issues are DNS, SSL, redirects, or control-panel settings that can be fixed in place.
Will changing DNS break email?
It can if MX and authentication records are missed. We check email records before DNS cutovers.
Can you manage a hosting migration?
Yes. We plan backups, staging, DNS, SSL, redirects, email records, and validation.
Do you support Cloudflare?
Yes. We help with DNS, proxy status, SSL mode, cache rules, WAF basics, and redirect issues.
We only changed the website DNS. Why would email break?
Because SPF, MX, and the servers that send form mail often live on the same zone. We test a form send after every DNS change.
Listings disappeared after we moved to HTTPS. Is the certificate wrong?
Often the certificate is fine and a plugin still requests an insecure script. We search for hard-coded http:// embeds before we reissue the cert.
Fix the domain, SSL, or hosting issue
Send the domain, what changed recently, and which systems you can access.
Contact
Ready to modernize your IT?
Get expert guidance on security, hosting, WordPress care, and cloud.
- Phone
- +1 (778) 300-0356
- [email protected]
- Hours
- Mon–Fri · 9:00 AM – 6:00 PM (PT)