Skip to content
https://www.ikv.org.tr

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
89
GRADE
B
FIX
2
REVIEW
8
PASS
7
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
7 PASS 8 REVIEW 2 FIX
D
HTTP Probe Timing
Action
Total 2961 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
FIX
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
73 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
60 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
124 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
2.78 s
Total Time Total request time from DNS lookup through full response.
2.96 s

Connection waterfall

DNS Lookup 73 ms TCP Connect 60 ms TLS Handshake 124 ms Server Processing 2.53 s Content Transfer 178 ms
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
Multi-Resolver DNS Speed
Mean 122ms across 3 resolvers (spread 159ms)
REVIEW
Mean 122ms across 3 resolvers (spread 159ms)
Info::
Google: 69ms
Got: 69ms via 8.8.8.8:53
Info::
Quad9: 71ms
Got: 71ms via 9.9.9.9:53
Info::
Cloudflare: 228ms
Got: 228ms via 1.1.1.1:53
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
125 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • 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, 129 ms lookup
PASS
1 A records, 129 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 212.58.8.151
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
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: 129 ms
Got: 129 ms
A212.58.8.151
AAAA—
CNAME—
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 129 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

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)

A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Reverse DNS
1/1 IPs match cert SAN
PASS
1/1 IPs match cert SAN
Info::
PTR for 212.58.8.151 matches certificate SAN: ikv.org.tr
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.ikv.org.tr

https://www.ikv.org.tr

3600 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.ikv.org.tr2003600 msHTTP/1.1Microsoft-IIS/8.5
A+
Crawlability
robots.txt present, sitemap with 17198 URLs
PASS
robots.txt present, sitemap with 17198 URLs
Info::
robots.txt is present
Got: 187 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 17198 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 187 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-Agent: *

Allow: /

Disallow: /intranet

Disallow: /includes

Disallow: /ydk

Disallow: /intranet/

Disallow: /includes/

Disallow: /ydk/

Sitemap: https://www.ikv.org.tr/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 17198 entries Valid XML Yes
Sample URLs:
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: www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.ikv.org.tr/
301https://ikv.org.tr/

Preferred variant: www

HTTP → HTTPS

301http://www.ikv.org.tr/ → https://www.ikv.org.tr/

Consistent

A+
Domain Intelligence
ikv.org.tr — hosted on DORUKNET, TR
PASS
ikv.org.tr — hosted on DORUKNET, TR
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: DORUKNET, TR
Got: AS8685
Domain expiry

Unknown

SSL certificate

125 days

Issued by DigiCert Inc

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

DORUKNET, TR

ASN AS8685

212.58.8.151

Registrar

Registrar unknown

Unlocked Name servers unknown
Expiry timeline
Today
+1 year
SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar
Hosting
IP Address 212.58.8.151
ASN AS8685 (DORUKNET, TR)
Provider DORUKNET, TR
Data source: whois (0.9s)

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