Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Probed from Madrid, Spain

200 OK

Checks

6 PASS 11 REVIEW

DNSSEC

Unsigned (DNSSEC not deployed)

REVIEW

Unsigned (DNSSEC not deployed)

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).

CAA Records

No CAA records (any CA may issue certificates)

REVIEW

No CAA records (any CA may issue certificates)

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.

Reverse DNS

0/2 IPs match cert SAN

REVIEW

0/2 IPs match cert SAN

PTR for 149.126.6.123 does not match any cert SAN: vsa-vatmio.cyon.net

Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.

PTR for 2a01:ab20:0:6::123 does not match any cert SAN: vsa-vatmio.cyon.net

Crawlability

no robots.txt, no sitemap

REVIEW

no robots.txt, no sitemap

No robots.txt found

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

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.

URL Variants

www/non-www, trailing slash, HTTP→HTTPS

REVIEW

www/non-www, trailing slash, HTTP→HTTPS

HTTP version does not redirect to HTTPS

Got: HTTP 415 Expected: 301 redirect to HTTPS

www / non-www

200https://www.urimat.com/de/

415https://urimat.com/de/

Trailing Slash

200https://www.urimat.com/de/

415https://www.urimat.com/de

HTTP → HTTPS

415http://www.urimat.com/de/

HTTP version does not redirect to HTTPS

HTTP Probe Timing

Total 1315 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

REVIEW

DNS Lookup

42 ms

TCP Connect

26 ms

TLS Handshake

29 ms

Time to First Byte

1.29 s

Total Time

1.32 s

Connection waterfall

DNS Lookup 42 ms TCP Connect 26 ms TLS Handshake 29 ms Server Processing 1.19 s Content Transfer 26 ms

TLS Certificate Expiry & Recommendations

68 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

days left

0d 30d 60d 90d+

Recommended actions

Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
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

CDN & Delivery

Action

Assets on AWS CloudFront (host platform-cdn.sharethis.com, 6 assets); document served directly from origin

REVIEW

Assets on AWS CloudFront (host platform-cdn.sharethis.com, 6 assets); document served directly from origin

Document not behind existing CDN (AWS CloudFront serves the assets)

The page's subresources are delivered by AWS CloudFront (platform-cdn.sharethis.com, 6 assets), but the HTML document itself comes straight from the origin. Routing the document through the CDN already in use is the cheapest latency win available here -- the provider relationship, the certificate and the config already exist. A short edge TTL with stale-while-revalidate suits HTML that changes often; if the response is genuinely per-user, edge TLS termination alone still removes a full round trip from every visitor's first byte.

Got: x-amz-cf-id: aA5SBqiW7Pj4b8aTtcZ1ofjiuu7bGbbuCpx0loBE4bh69hT45w37Mg==

Assets on AWS CloudFront: platform-cdn.sharethis.com (assets: 6), cache Hit from cloudfront

Got: x-amz-cf-id: aA5SBqiW7Pj4b8aTtcZ1ofjiuu7bGbbuCpx0loBE4bh69hT45w37Mg==

Assets on Cloudflare: cdnjs.cloudflare.com (assets: 5), cache BYPASS

Got: cf-ray: a3878c855a0900a8-CDG

Assets on a CDN, document is not: AWS CloudFront

Document origin not attributed

Asset hosts on a CDN

platform-cdn.sharethis.com — AWS CloudFront · assets: 6 · Cache Status: Hit from cloudfront
cdnjs.cloudflare.com — Cloudflare · assets: 5 · Cache Status: BYPASS

Other asset hosts

www.google-analytics.com — assets: 2 · below probe threshold
ajax.googleapis.com — assets: 1 · below probe threshold
buttons-config.sharethis.com — assets: 1 · below probe threshold
platform-api.sharethis.com — assets: 1 · below probe threshold
scripts.clarity.ms — assets: 1 · below probe threshold
www.clarity.ms — assets: 1 · below probe threshold
www.googletagmanager.com — assets: 1 · below probe threshold
www.gstatic.com — assets: 1 · below probe threshold

The heavy static files already ride an edge network, but every visitor still waits on the origin for the HTML itself. Routing the document through the same CDN is usually a config change rather than a migration: a short edge TTL with stale-while-revalidate for cacheable HTML, or edge TLS termination alone when the response is per-user.

CDN Cache Observability

No CDN cache-status headers in the response

REVIEW

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.

Operational Status Page

No status page link detected

REVIEW

No status page link detected

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.

Health Check Endpoint

No conventional health endpoint found

REVIEW

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: 415, /health: 415, /healthz: 415, /ping: 415, /status: 415.

DNS Records

1 A records, 42 ms lookup

PASS

1 A records, 42 ms lookup

Resolves to 1 IPv4 address(es)

Got: 149.126.6.123

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

Has 1 IPv6 (AAAA) record(s)

Got: 2a01:ab20:0:6::123

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: urimat.com

2 nameserver(s) configured

Got: ns1.cyon.ch, ns2.cyon.ch

1 mail exchanger(s) configured

SPF record present in TXT

DNS resolution time: 42 ms

Got: 42 ms

A	149.126.6.123
AAAA	2a01:ab20:0:6::123
CNAME	urimat.com
NS	ns1.cyon.ch, ns2.cyon.ch
MX	0 urimat-com.mail.protection.outlook.com
TXT	google-site-verification=-hO1NR6aa8Kyz7o7O-3TKmLx9hlQgLQLnzAR8lvtgh4 SPF v=spf1 ip4:62.202.22.137 include:spf.abteilung.ch include:spf.protection.outlook... google-site-verification=LONTRPoH61FJOLYYon15BoBCyOJHvQTQrEFMt--NQss
CAA	Lookup not available with standard resolver

Resolved in 42 ms

Multiple A records provide failover if one server goes down.

Why this matters

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 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

A+

Subdomain Takeover

No subdomain takeover risk detected

PASS

No subdomain takeover risk detected

CNAME does not point at a known takeover-able service

Multi-Resolver DNS Speed

Mean 32ms across 3 resolvers (spread 64ms)

PASS

Mean 32ms across 3 resolvers (spread 64ms)

Quad9: 0ms

Got: 0ms via 9.9.9.9:53

Google: 34ms

Got: 34ms via 8.8.8.8:53

Cloudflare: 64ms

Got: 64ms via 1.1.1.1:53

A+

Redirect Chain

No redirects — direct access

PASS

No redirects — direct access

Got: https://www.urimat.com/de/

https://www.urimat.com/de/

84 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://www.urimat.com/de/	200	84 ms	HTTP/1.1

A+

IPv6 Readiness

IPv6 reachable (27 ms)

PASS

IPv6 reachable (27 ms)

IPv6 is configured and reachable at 2a01:ab20:0:6::123

Got: 27 ms connect

IPv6 Ready

AAAA Records 2a01:ab20:0:6::123 Connection Reachable (27 ms)

Domain Intelligence

urimat.com — via IONOS SE, 28 years, 3 months old

PASS

urimat.com — via IONOS SE, 28 years, 3 months old

Domain expires in 51 days

Consider enabling auto-renewal to prevent accidental expiration.

Got: Expires Oct 31, 2026

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.

Registrar: IONOS SE

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

49 days

October 31, 2026

SSL certificate

68 days

Issued by Let's Encrypt

Domain age

28 years, 3 months

Registered November 1, 1998

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2a01:ab20:0:6::123

Registrar

IONOS SE

Unlocked 2 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 IONOS SE

Created November 1, 1998 (28 years, 3 months ago)

Expires October 31, 2026 (1 months)

Last Updated November 1, 2025

Name Servers ns1.cyon.ch, ns2.cyon.ch

DNSSEC Not enabled

Hosting

IP Address 2a01:ab20:0:6::123

Data source: rdap (0.3s)

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.