Skip to content
https://hurriyet.com.tr

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
83
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
4 PASS 4 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.

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
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 736 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 736 B Sitemaps referenced 0 User-agents *, GPTBot, anthropic-ai, ChatGPT-User, cohere-ai, quillbot.com, PerplexityBot, TurnitinBot, Flipboard, FlipboardProxy, ClaudeBot, Claude-Web, OAI-SearchBot, AmazonAdBot Blocking No — crawling allowed
User-agent:*

Disallow: /ad/

Disallow: /api/

Disallow: /arkadasimamektup/

Disallow: /okurtemsilcisi/

Disallow: /widgets/

Disallow: /_includes/

Disallow: /_othernews/

Disallow: /_test/

Disallow: /_includescms/

Disallow: /arama/


User-agent: Flipboard

User-agent: FlipboardProxy

Allow: /api/


User-agent: GPTBot

Disallow: /


User-agent: anthropic-ai

Disallow: /


User-agent: ChatGPT-User

Disallow: /


User-agent: ClaudeBot

Disallow: /


User-agent: Claude-Web

Disallow: /


User-agent: cohere-ai

Disallow: /


User-agent: OAI-SearchBot

Disallow: /


User-agent: quillbot.com

Disallow: /


User-agent: PerplexityBot

Disallow: /


User-agent: TurnitinBot

Disallow: /


User-agent: AmazonAdBot

Allow: /
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
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.hurriyet.com.tr/
200https://hurriyet.com.tr/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://hurriyet.com.tr/ https://www.hurriyet.com.tr/

Consistent

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

Certificate validity

96
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
A+
DNS Records
1 A records, 47 ms lookup
PASS
1 A records, 47 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 83.66.162.26
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: ns-1789.awsdns-31.co.uk, ns-601.awsdns-11.net, ns-63.awsdns-07.com, ns-1172.awsdns-18.org
Info::
1 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 47 ms
Got: 47 ms
A83.66.162.26
AAAA
CNAME
NSns-1789.awsdns-31.co.uk, ns-601.awsdns-11.net, ns-63.awsdns-07.com, ns-1172.awsdns-18.org
MX
0 hurriyet-com-tr.mail.protection.outlook.com
TXT
_globalsign-domain-verification=LKvNitbBFj3VJa1KFqsFjlyfHSfYZDm1xw5mXpk8cJ
google-site-verification=_84-1_9YnXomVnJVsE4ZYf1UbFlwtu1ghYmc217CY80
google-site-verification=OSu-mCpWalutdjyurMi1MUhsnaA8bs6TcKemgAtkHNQ
SPF v=spf1 mx a ip4:212.31.1.224/28 ip4:212.31.1.29 ip4:212.31.1.58 ip4:52.214.28.15...
google-site-verification=CUKWCZDz-H7kAuQmJ3AFHCac8xVY5SxT7W6Hv6l3kk4
atlassian-domain-verification=6bTSRLIXtfkrK1YwBLEjxN9IM26ijkhnj0i4ADjQ5W68+2JUC4...
google-gws-recovery-domain-verification=68015205
google-site-verification=ve06mvct1C1X9FGCYni0ZoWc8fK01lQxYjmfGuxJFe8
tiktok-developers-site-verification=Mq8iYBhHeXBJwg7GM0B4kGvQSS2pVLeW
CAALookup not available with standard resolver
Resolved in 47 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

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A
Redirect Chain
1 redirect(s), 607 ms total
PASS
1 redirect(s), 607 ms total
Info::
Single redirect
Got: https://hurriyet.com.tr → https://www.hurriyet.com.tr/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 607 ms total
Got: 607 ms

https://hurriyet.com.tr

408 ms · HTTP/1.1

301

https://www.hurriyet.com.tr/

200 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://hurriyet.com.tr301408 msHTTP/1.1
2https://www.hurriyet.com.tr/200200 msHTTP/1.1MerlinCDN

See the visual redirect chain in the HTTP Probe tab →

A+
Domain Intelligence
hurriyet.com.tr — hosted on DSMART, TR
PASS
hurriyet.com.tr — hosted on DSMART, 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: DSMART, TR
Got: AS12978
Domain expiry

Unknown

SSL certificate

96 days

Issued by GlobalSign nv-sa

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

DSMART, TR

ASN AS12978

83.66.162.26

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 83.66.162.26
ASN AS12978 (DSMART, TR)
Provider DSMART, 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

A
HTTP Probe Timing
Total 429 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.
231 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
429 ms
Total Time Total request time from DNS lookup through full response.
429 ms

Connection waterfall

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

Send Feedback