Infrastructure
· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DTLS Certificate Expiry & RecommendationsAction7 days until leaf cert expires — 3 issues to addressFIX
Certificate validity
Recommended actions
- Renew certificate — 7 days remaining
- Enable DNSSEC on your domain for DNS spoofing protection
- Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
BDNSSECUnsigned (DNSSEC not deployed)REVIEW
BReverse DNS0/2 IPs match cert SANREVIEW
BRedirect Chain2 redirect(s), 466 ms totalREVIEW
https://instagram.com
148 ms · HTTP/1.1
https://www.instagram.com/
180 ms · HTTP/1.1
https://www.instagram.com/accounts/login...
138 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://instagram.com | 301 | 148 ms | HTTP/1.1 | |
| 2 | https://www.instagram.com/ | 302 | 180 ms | HTTP/1.1 | |
| 3 | https://www.instagram.com/accounts/login... | 429 | 138 ms | HTTP/1.1 |
See the visual redirect chain in the HTTP Probe tab →
Each redirect adds latency. Try to minimize the chain to 1 hop.
Redirect chain — each hop adds latency; combine into one redirect where possible.
Source: Google Search Central / web.dev
If permanent, use 301 instead.
302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.
Learn more ▾ ▴
Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).
Source: Google Search Central
BCrawlabilityno robots.txt, no sitemapREVIEW
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.
Learn more ▾ ▴
A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.
Source: robotstxt.org
A sitemap helps search engines discover and index your pages more efficiently.
No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.
Learn more ▾ ▴
A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.
Source: sitemaps.org / Google Search Central
No robots.txt found
This is fine for most sites — a missing robots.txt allows all crawling by default.
No sitemap found
Adding a sitemap helps search engines discover your pages.
BCDN Cache ObservabilityNo CDN cache-status headers in the responseREVIEW
BOperational Status PageNo status page link detectedREVIEW
BHealth Check EndpointNo conventional health endpoint foundREVIEW
A+DNS Records1 A records, 31 ms lookupPASS
| A | 57.144.16.34 |
| AAAA | 2a03:2880:f307:22:face:b00c:0:4420 |
| CNAME | — |
| NS | a.ns.instagram.com, c.ns.instagram.com, b.ns.instagram.com, d.ns.instagram.com |
| MX | 10 mxa-00082601.gslb.pphosted.com 10 mxb-00082601.gslb.pphosted.com |
| TXT | ms=ms86975275 google-site-verification=GGtId51KFyq0hqX2xNvt1u0P9Xp0C7k6pp9do49fCNw nEXgIFIbDifAKlSMQvAhly5SA-vpsAkm5wiOdwdkrzY SPF v=spf1 include:facebookmail.com include:_spf.fb.com -all google-site-verification=_iQgLr68Rdg7YnN2PqOljSG5dnWOFUUXISF9R77fs5c _yvfspgyfwcjnwgopowc9qjme14c32od facebook-domain-verification=hksvhmzcutq39t1kgpmlx11kt8314q hyWdekepiNsp/V9b1JCR+wZDdzbESurl4GqY+FLMfiN+7aeFaway0Art+kNDHeL5OnGZipNeV/iIC+lO... adobe-idp-site-verification=367fda82-a8bb-46cf-9cff-0062d452d229 4cbb1b68-601f-4801-8e7f-e8f68a4a41dd |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.
Learn more ▾ ▴
Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.
Source: SRE practice / DNS architecture
A+Subdomain TakeoverNo subdomain takeover risk detectedPASS
ACAA Recordsissue: digicert.comPASS
A+Multi-Resolver DNS SpeedMean 14ms across 3 resolvers (spread 21ms)PASS
A+IPv6 ReadinessIPv6 reachable (16 ms)PASS
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligenceinstagram.com — via RegistrarSafe, LLC, 22 years, 6 months oldPASS
2848 days
June 4, 2034
7 days
Issued by DigiCert Inc
22 years, 6 months
Registered June 4, 2004
Not enabled
Protects against DNS spoofing
Unknown
2a03:2880:f307:22:face:b00c:0:4420
RegistrarSafe, LLC
Expiry timeline
Recommended actions
- Renew the TLS certificate or verify auto-renewal is working
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.
Learn more ▾ ▴
DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.
Source: ICANN / RFC 4033
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.
Learn more ▾ ▴
Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.
Source: ICANN / domain-security best practice