ST

security.txt history

A historical index of security.txt files across the web.

security.txt

cynalytics.com

Collected on 2026-10-22 22:41 UTC.

#   _____                  _       _   _          
#  / ____|                | |     | | (_)         
# | |    _   _ _ __   __ _| |_   _| |_ _  ___ ___ 
# | |   | | | | '_ \ / _` | | | | | __| |/ __/ __|
# | |___| |_| | | | | (_| | | |_| | |_| | (__\__ \
#  \_____\__, |_| |_|\__,_|_|\__, |\__|_|\___|___/
#         __/ |               __/ |               
#        |___/               |___/                

# Thank you and acknowledgement
#
# Dear security researcher, we are most happy that you're taking the
# time to look at our security.txt, probably to identify who to contact
# with your findings.
#
# We would be very happy to receive your findings and possible recommendations.
# And in order to show our gratitude, we will mention you on our security.txt
# with the security issues that you raised.

# Our policy and our commitment to you
#
# Please feel free and invited to research our system. But please also keep
# the following pointers in mind:
# - Research to see if you can find a way in. When you do, please inform us
#   through mail, rather than leaving a message on the website. We will
#   consider this defacing of the site.
# - Please do not test our website by DDoS'ing it. That's not related to
#   website security but rather a game of bandwidth and filtering. We will
#   consider DDoS as an attack rather than research.
# - If you manage to find a way in, please leave the data intact, and don't
#   download all the data. That's not necessary to prove your point.
#   Downloading significant amounts of data, i.e. more than what's
#   reasonably needed to prove your point, will be considered data theft.
#
# In return, when you stick to these rules, we hereby promise you we will
# not only not take legal action, but rather be very happy with your input.
# If you're in the neighbourhood, please do feel free to drop by and claim
# your lunch with us, when you've reported a security issue!


# The formal bit
Contact: mailto:bas.vanderlinden@cynalytics.nl
Expires: 2025-09-01T10:00:00.000Z
Encryption: https://www.cynalytics.nl/pubkey.asc
Preferred-Languages: nl, en

# Thank you for reading, and thank  you even more for reporting
# security issues in our site!

This file is shown exactly as published by the domain, as collected by the securitytxthistory crawler. 2,198 bytes · 49 lines.

Collection details

HTTP 200/.well-known/security.txttext/plain
Collected URL

https://cynalytics.com/.well-known/security.txt

SHA-256

8cf46be485c55bd0ffd5f87b3a8ab50183570b558bd55e5571c53124020602e7