Skip to content
https://insightcenter.b2clogin.com/insightcenter.onmicrosoft.com/b2c_1a_ss_si/oauth2/v2.0/authorize?client_id=b1cf1b94-be82-4e12-a3ef-23c9154c772b&scope=https%3A%2F%2Finsightcenter.onmicrosoft.com%2Feservice-api-prd%2Fuser_impersonation%20openid%20profile%20offline_access&redirect_uri=https%3A%2F%2Fservice.stryker.com%2FloginSSO&client-request-id=019eb605-6af2-7793-98db-bf244f7a8554&response_mode=fragment&response_type=code&x-client-SKU=msal.js.browser&x-client-VER=3.30.0&client_info=1&code_challenge=BRub9pEd4Ln2tN_VOD8VCubek0OyYIqUDzff1E1zHMo&code_challenge_method=S256&nonce=019eb605-6af5-7490-9771-b2ecca73ccf4&state=eyJpZCI6IjAxOWViNjA1LTZhZjQtN2ZhZC1iZjQ3LWMzYmE1MmVjYjZiNyIsIm1ldGEiOnsiaW50ZXJhY3Rpb25UeXBlIjoicmVkaXJlY3QifX0%3D

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
76
GRADE
C
FIX
2
REVIEW
12
PASS
3
INFO
0
Probed from Santa Clara, United States
200 OK
Checks
17
3 PASS 12 REVIEW 2 FIX
F
IPv6 Readiness
Action
IPv6 records exist but unreachable
FIX
IPv6 records exist but unreachable
Warning::
IPv6 DNS records exist but server is not reachable
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Got: 2603:1037:1:130::6, 2603:1037:1:128::7, 2603:1036:3000:138::5, 2603:1036:3000:138::4, 2603:1037:1:130::4, 2603:1037:1:130::5, 2603:1036:3000:138::3, 2603:1037:1:128::6
Info::
IPv6 connection error
Got: dial tcp6 [2603:1037:1:130::6]:443: connect: network is unreachable
IPv6 Misconfigured
AAAA Records 2603:1037:1:130::6, 2603:1037:1:128::7, 2603:1036:3000:138::5, 2603:1036:3000:138::4, 2603:1037:1:130::4, 2603:1037:1:130::5, 2603:1036:3000:138::3, 2603:1037:1:128::6 Connection UNREACHABLE

Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.

Why this matters

Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.

Learn more ▾

Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.

Source: RFC 8305 (Happy Eyeballs)

D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

B
DNS Records
8 A records, 12 ms lookup
REVIEW
8 A records, 12 ms lookup
Info::
Resolves to 8 IPv4 address(es)
Got: 40.126.62.132, 20.190.190.130, 20.190.190.132, 40.126.62.129, 20.190.190.196, 20.190.190.129, 40.126.62.131, 20.190.190.193
Info::
Has 8 IPv6 (AAAA) record(s)
Got: 2603:1037:1:130::6, 2603:1037:1:128::7, 2603:1036:3000:138::5, 2603:1036:3000:138::4, 2603:1037:1:130::4, 2603:1037:1:130::5, 2603:1036:3000:138::3, 2603:1037:1:128::6
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: prda.aadg.msidentity.com
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 12 ms
Got: 12 ms
A40.126.62.132, 20.190.190.130, 20.190.190.132, 40.126.62.129, 20.190.190.196, 20.190.190.129, 40.126.62.131, 20.190.190.193
AAAA2603:1037:1:130::6, 2603:1037:1:128::7, 2603:1036:3000:138::5, 2603:1036:3000:138::4, 2603:1037:1:130::4, 2603:1037:1:130::5, 2603:1036:3000:138::3, 2603:1037:1:128::6
CNAMEprda.aadg.msidentity.com
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 12 ms

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more ▾

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
B
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
No CAA records published
Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.
C
Reverse DNS
Action
0/16 IPs match cert SAN
REVIEW
0/16 IPs match cert SAN
Info::
PTR lookup failed for 40.126.62.132: lookup 40.126.62.132: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 20.190.190.130: lookup 20.190.190.130: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 20.190.190.132: lookup 20.190.190.132: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 40.126.62.129: lookup 40.126.62.129: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 20.190.190.196: lookup 20.190.190.196: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 20.190.190.129: lookup 20.190.190.129: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 40.126.62.131: lookup 40.126.62.131: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 20.190.190.193: lookup 20.190.190.193: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2603:1037:1:130::6: lookup 2603:1037:1:130::6: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2603:1037:1:128::7: lookup 2603:1037:1:128::7: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2603:1036:3000:138::5: lookup 2603:1036:3000:138::5: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2603:1036:3000:138::4: lookup 2603:1036:3000:138::4: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2603:1037:1:130::4: lookup 2603:1037:1:130::4: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2603:1037:1:130::5: lookup 2603:1037:1:130::5: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2603:1036:3000:138::3: lookup 2603:1036:3000:138::3: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2603:1037:1:128::6: lookup 2603:1037:1:128::6: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
C
Multi-Resolver DNS Speed
Action
Mean 74ms across 3 resolvers (spread 203ms)
REVIEW
Mean 74ms across 3 resolvers (spread 203ms)
Info::
Cloudflare: 3ms
Got: 3ms via 1.1.1.1:53
Info::
Google: 15ms
Got: 15ms via 8.8.8.8:53
Info::
Quad9: 206ms
Got: 206ms via 9.9.9.9:53
Info::
High latency spread between resolvers: 203ms (min 3ms / max 206ms)
Wide gap between the fastest and slowest public resolver suggests a geographic anycast issue or an authoritative-server cache problem. Users in different regions will see materially different DNS times.
B
Crawlability
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

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.

Why this matters

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

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Warning::
Trailing slash inconsistency — both versions serve content
Got: Both with/without trailing slash return 200 Expected: One variant 301-redirects to the other
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

https://www.insightcenter.b2clogin.com/insightcenter.onmicrosoft.com/b2c_1a_ss_si/oauth2/v2.0/authorize
200https://insightcenter.b2clogin.com/insightcenter.onmicrosoft.com/b2c_1a_ss_si/oauth2/v2.0/authorize

Trailing Slash

200https://insightcenter.b2clogin.com/insightcenter.onmicrosoft.com/b2c_1a_ss_si/oauth2/v2.0/authorize/
200https://insightcenter.b2clogin.com/insightcenter.onmicrosoft.com/b2c_1a_ss_si/oauth2/v2.0/authorize?client_id=b1cf1b94-be82-4e12-a3ef-23c9154c772b&scope=https%3A%2F%2Finsightcenter.onmicrosoft.com%2Feservice-api-prd%2Fuser_impersonation%20openid%20profile%20offline_access&redirect_uri=https%3A%2F%2Fservice.stryker.com%2FloginSSO&client-request-id=019eb605-6af2-7793-98db-bf244f7a8554&response_mode=fragment&response_type=code&x-client-SKU=msal.js.browser&x-client-VER=3.30.0&client_info=1&code_challenge=BRub9pEd4Ln2tN_VOD8VCubek0OyYIqUDzff1E1zHMo&code_challenge_method=S256&nonce=019eb605-6af5-7490-9771-b2ecca73ccf4&state=eyJpZCI6IjAxOWViNjA1LTZhZjQtN2ZhZC1iZjQ3LWMzYmE1MmVjYjZiNyIsIm1ldGEiOnsiaW50ZXJhY3Rpb25UeXBlIjoicmVkaXJlY3QifX0%3D

Inconsistent — duplicate content risk

HTTP → HTTPS

302http://insightcenter.b2clogin.com/insightcenter.onmicrosoft.com/b2c_1a_ss_si/oauth2/v2.0/authorize → https://insightcenter.b2clogin.com:443/insightcenter.onmicrosoft.com/b2c_1a_ss_si/oauth2/v2.0/authorize

Use 301 (permanent) instead of 302 (temporary)

B
HTTP Probe Timing
Total 993 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
13 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
72 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
149 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
848 ms
Total Time Total request time from DNS lookup through full response.
994 ms

Connection waterfall

DNS Lookup 13 ms TCP Connect 72 ms TLS Handshake 149 ms Server Processing 613 ms Content Transfer 146 ms
B
TLS Certificate Expiry & Recommendations
156 days until leaf cert expires — 2 issues to address
REVIEW

Certificate validity

156
days left
0d 30d 60d 90d+

Recommended actions

  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • Enable DNSSEC on your domain for DNS spoofing protection
B
CDN Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
No CDN cache-status headers in the response
Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
CNAME does not point at a known takeover-able service
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://insightcenter.b2clogin.com/insightcenter.onmicrosoft.com/b2c_1a_ss_si/oauth2/v2.0/authorize?client_id=b1cf1b94-be82-4e12-a3ef-23c9154c772b&scope=https%3A%2F%2Finsightcenter.onmicrosoft.com%2Feservice-api-prd%2Fuser_impersonation%20openid%20profile%20offline_access&redirect_uri=https%3A%2F%2Fservice.stryker.com%2FloginSSO&client-request-id=019eb605-6af2-7793-98db-bf244f7a8554&response_mode=fragment&response_type=code&x-client-SKU=msal.js.browser&x-client-VER=3.30.0&client_info=1&code_challenge=BRub9pEd4Ln2tN_VOD8VCubek0OyYIqUDzff1E1zHMo&code_challenge_method=S256&nonce=019eb605-6af5-7490-9771-b2ecca73ccf4&state=eyJpZCI6IjAxOWViNjA1LTZhZjQtN2ZhZC1iZjQ3LWMzYmE1MmVjYjZiNyIsIm1ldGEiOnsiaW50ZXJhY3Rpb25UeXBlIjoicmVkaXJlY3QifX0%3D

https://insightcenter.b2clogin.com/insig...

456 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://insightcenter.b2clogin.com/insig...200456 msHTTP/1.1
A
Domain Intelligence
b2clogin.com — via Nom-iq Ltd. dba COM LAUDE, 9 years old
PASS
b2clogin.com — via Nom-iq Ltd. dba COM LAUDE, 9 years old
Warning::
Domain expires in 36 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Jul 17, 2026
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: Nom-iq Ltd. dba COM LAUDE
Warning::
Registrar lock is NOT enabled
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.
Domain expiry

34 days

July 17, 2026

SSL certificate

156 days

Issued by DigiCert Inc

Domain age

9 years

Registered July 17, 2017

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

Registrar

Nom-iq Ltd. dba COM LAUDE

Unlocked 8 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Nom-iq Ltd. dba COM LAUDE
Created July 17, 2017 (9 years ago)
Expires July 17, 2026 (1 months)
Last Updated June 17, 2025
Name Servers eur2.akam.net, ns1-169.akam.net, ns1-35.azure-dns.com, ns2-35.azure-dns.net, ns3-35.azure-dns.org, ns4-35.azure-dns.info, use2.akam.net, usw1.akam.net
DNSSEC Not enabled
Data source: rdap (0.1s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

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.

Why this matters

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback