Skip to content
https://ohm-energie.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
89
GRADE
B
FIX
1
REVIEW
8
PASS
8
INFO
0
Probed from New York, United Stated
200 OK
Checks
17
8 PASS 8 REVIEW 1 FIX
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
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.
B
Reverse DNS
0/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR for 5.135.23.164 does not match any cert SAN: cluster100.hosting.ovh.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.
C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
TLS Certificate Expiry & Recommendations
63 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

63
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
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+
DNS Records
1 A records, 48 ms lookup
PASS
1 A records, 48 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 5.135.23.164
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns1106.ui-dns.de, ns1086.ui-dns.com, ns1074.ui-dns.org, ns1111.ui-dns.biz
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 48 ms
Got: 48 ms
A5.135.23.164
AAAA—
CNAME—
NSns1106.ui-dns.de, ns1086.ui-dns.com, ns1074.ui-dns.org, ns1111.ui-dns.biz
MX
9 ohmenergie-com0i.mail.protection.outlook.com
TXT
EY3021224MJ
google-site-verification=zDIR31HXNVSNQM2v2bC4h6unKQK0TEjY1UtTvNaAbPw
brevo-code:2eb81b4cbb50a13b3d0db875f6031f10
google-site-verification=-dpNmP5gWSh0lWSyl-D9vReJUNfG4oe9v-ZhZ9NRZEQ
ns1.sendinblue.com
ns2.sendinblue.com
box-domain-verification=6e43f795afa12ad3d22c2637b383bc80713a9e885123169c32503056...
SPF v=spf1 include:spf.protection.outlook.com include:spf.mailjet.com -all
UrT456PdJ632
MS=40C13755A0D635255CAEFB01672AFBBB18387B6C
brevo-code:035e0fa9540a867bc5e4ab4a438713ac
1987w2w2w2
SFMC-7M3tSw29hHeeJXvzAle0XTzNYoaenRBz0T3FXvjY
brevo-code:44d10a62a6cd91fef91cb0d11415bebe
CAALookup not available with standard resolver
Resolved in 48 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+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A
Multi-Resolver DNS Speed
Mean 26ms across 3 resolvers (spread 67ms)
PASS
Mean 26ms across 3 resolvers (spread 67ms)
Info::
Cloudflare: 3ms
Got: 3ms via 1.1.1.1:53
Info::
Google: 7ms
Got: 7ms via 8.8.8.8:53
Info::
Quad9: 70ms
Got: 70ms via 9.9.9.9:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://ohm-energie.com

https://ohm-energie.com

399 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://ohm-energie.com200399 msHTTP/1.1Apache
A+
Crawlability
robots.txt present, sitemap with 10 URLs
PASS
robots.txt present, sitemap with 10 URLs
Info::
robots.txt is present
Got: 191 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 10 entries
Info::
Sitemap index with 10 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 191 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
# START YOAST BLOCK
# ---------------------------
User-agent: *
Disallow:

Sitemap: http://oyzuzez.cluster100.hosting.ovh.net/sitemap_index.xml
# ---------------------------
# END YOAST BLOCK
sitemap.xml 200 OK
Type Sitemap Index URLs 10 entries Valid XML Yes
Child Sitemaps:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.ohm-energie.com/
200https://ohm-energie.com/

Preferred variant: non-www

HTTP → HTTPS

301http://ohm-energie.com/ → https://ohm-energie.com/

Consistent

A+
Domain Intelligence
ohm-energie.com — via IONOS SE, 8 years, 7 months old, hosted on OVH
PASS
ohm-energie.com — via IONOS SE, 8 years, 7 months old, hosted on OVH
Info::
Domain registered until Jan 13, 2027 (5 months remaining)
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: IONOS SE
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.
Info::
Hosting: OVH
Got: AS16276
Domain expiry

171 days

January 13, 2027

SSL certificate

63 days

Issued by Let's Encrypt

Domain age

8 years, 7 months

Registered January 13, 2018

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

OVH

ASN AS16276

5.135.23.164

Registrar

IONOS SE

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar IONOS SE
Created January 13, 2018 (8 years, 7 months ago)
Expires January 13, 2027 (5 months)
Last Updated January 14, 2026
Name Servers ns1074.ui-dns.org, ns1086.ui-dns.com, ns1106.ui-dns.de, ns1111.ui-dns.biz
DNSSEC Not enabled
Hosting
IP Address 5.135.23.164
ASN AS16276 (OVH - OVH SAS, FR)
Provider OVH
Data source: rdap (0.1s)

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

A
HTTP Probe Timing
Total 446 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
46 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
76 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
85 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
295 ms
Total Time Total request time from DNS lookup through full response.
446 ms

Connection waterfall

DNS Lookup 46 ms TCP Connect 76 ms TLS Handshake 85 ms Server Processing 88 ms Content Transfer 152 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback