Skip to main content
Utilnivo

Developer workflow

Pre-launch domain and TLS check

Shipping a new hostname fails more often on DNS and TLS than on app code. This workflow checks resolution, registration details, certificate validity, and common security headers before you flip traffic.

Confirm DNS, WHOIS, SSL certificates, and security headers before go-live.

  • 4 steps
  • About 8 minutes
  • Data stays on this device
  • Updated 2026-07-24
Copy & customize

Workflow

Steps to complete

Work through each step in order. Progress is saved in this browser. Utilnivo does not save uploaded files permanently between tools.

Progress: 0 of 4 steps complete (0%)

  1. Check DNS

    DNS Lookup

    Verify A/AAAA/CNAME records resolve to the expected targets.

    • Online lookup
    • No signup
    Open DNS Lookup

  2. Review registration

    WHOIS Lookup

    Confirm registrar, expiry, and nameserver details look correct.

    • Online lookup
    • No signup
    Open WHOIS Lookup

  3. Validate TLS

    SSL Checker

    Check certificate chain, expiry, and hostname match.

    • Online lookup
    • No signup
    Open SSL Checker

  4. Scan security headers

    Security Headers Checker

    Review HSTS, CSP, and related response headers on HTTPS.

    • On your device
    • No signup
    Open Security Headers Checker

Track progress

Your progress

0 of 4 complete (0%). Your progress is saved in this browser.

Printable step list with checkboxes—generated on your device.

Results

Overall output

What you entered and what each step produced appear here. Values used in the next step are passed when supported. Data stays in this browser only.

Run each step and submit the calculator form. Key results will appear here as a connected summary.

Progress: 0 of 4 steps marked complete (0%).

When to use this workflow

  • You pointed a new domain or subdomain at hosting and want confirmation.
  • Users report certificate warnings after a cutover.
  • You are preparing a launch checklist for staging → production.

Tips

Tips for better results

  • Allow time for DNS TTL to expire when comparing old vs new records.
  • SSL Checker should cover the exact hostname users will type, including www.
  • Pair this with the technical SEO health workflow after the site responds 200.

FAQ

Frequently asked questions

Do these lookups run from my browser?

Network lookup tools contact public resolvers or the target host as described on each tool page—they are diagnostic, not a hosting control panel.

Why do DNS results still show the old IP?

Caches and TTLs can delay updates. Re-check from another network after the TTL window.

Is a green SSL check enough?

It confirms certificate basics. Still test redirects, HSTS, and the full user journey.

Keep going

Related workflows

Technical SEO health pass

SEO

Check HTTP status and headers, security headers, Core Web Vitals concepts, and redirects.

5 steps

  1. Check status codes
  2. Inspect headers
  3. Review security headers
  4. Review CWV concepts
  5. Audit redirects

Debug a site before launch

SEO

Check DNS, SSL certificates, HTTP headers, and structured data before you go live.

5 steps

  1. Check DNS
  2. Check SSL
  3. Inspect headers
  4. Generate schema
  5. Validate schema

Check if a site can be indexed

SEO

Generate and test robots.txt, build/validate sitemaps, and spot redirect or broken-link traps.

6 steps

  1. Draft robots.txt
  2. Test rules
  3. Build sitemap
  4. Validate sitemap
  5. Check redirects
  6. Find broken links