# security.txt - RFC 9116
#
# A machine-readable way to report a security problem with EMPIRE.
#
# This file is also a small, checkable legitimacy signal: automated
# reputation scanners look for it, and a domain that publishes a real
# contact for security reports does not look like a disposable host.
# That is a side effect, not the reason. The reason is that if someone
# finds a hole in this platform, there should be an obvious place to
# say so that does not depend on them guessing an email address.
#
# NOTE ON EXPIRES: RFC 9116 requires it, and an expired file is treated
# as invalid - worse than absent, because it signals an abandoned
# process. Renew this before the date below.

#
# TWO DIFFERENT THINGS, DELIBERATELY LISTED SEPARATELY:
#
#   Contact  - a security problem with the EMPIRE PLATFORM itself.
#              A vulnerability, a bug that exposes customer data.
#
#   /abuse.html - a site HOSTED ON the platform being used for phishing,
#              malware, spam or counterfeit goods. Different problem,
#              different queue, and by far the more common of the two.
#
# Collapsing them into one address means phishing reports sit behind
# vulnerability triage, and the phishing report is the urgent one.

Contact: mailto:cryptcodesupport@gmail.com
Contact: tel:+1-402-206-4827
Contact: https://empiresitebuilder.com/abuse.html
Expires: 2027-09-10T00:00:00.000Z
Preferred-Languages: en
Canonical: https://empiresitebuilder.com/.well-known/security.txt
Policy: https://empiresitebuilder.com/security.html

# Abuse hotline, staffed by the people who run the platform: +1-402-206-4827
# Sites removed for abuse return 410 Gone with a notice naming the reason,
# so a re-crawl can verify the takedown rather than taking our word for it.