Service · Security and speed
How do we protect your website, your domain and your email?
The guest types their name, phone number and email address into the booking form. That this information travels over an encrypted connection, that the website stays available under heavy traffic and that your domain remains under your control are preconditions for the booking. We publish your website and booking engine on our infrastructure partner's worldwide network. We set up the encrypted connection, attack protection, caching, domain records and email authentication records, and we measure them on the live website after every release. We back up the data in the hotel management system to a separate store every night.
- What we do
We publish the website and booking engine with an encrypted connection, attack protection and caching. The domain, email authentication records, browser protections and the nightly backup are also part of this work.
- What changes at the hotel
You do not keep track of the infrastructure account, the domain settings or the certificate renewal. We check the website after every release; if a problem occurs, the alert comes to us.
- Possible benefit
The guest's information travels encrypted, and pages open quickly from a point close to the guest. Trust in your website and your email may make the booking decision easier.
Request an AI findability report
Which protections do we set up?
Encrypted connection
Every page opens over https; a visit arriving over http is redirected to the https address. The browser is told to open the website only over an encrypted connection for 180 days. The infrastructure renews the certificate automatically.
Attack protection
Every request to the website first passes through our infrastructure partner's network. Heavy traffic attacks aimed at making the website unavailable are filtered at network level before they reach the website.
Worldwide delivery and caching
Pages and images come from the point closest to the guest; a guest browsing from abroad also opens the page quickly. We clear the cache after every release, so no outdated page stays with the guest.
Browser protections
We block other websites from framing and displaying your page inside their own. The page does not ask the browser for location, microphone or camera permission; the browser's file type guessing is switched off.
Domain lock
When we register your domain through our infrastructure partner, the domain is protected by a transfer lock and the registrant's personal details are hidden in the public record. Only the administrator account can change the domain settings.
Email authentication records
We set up SPF, DKIM and DMARC records for your business email. The recipient's mail server uses these records to verify that a message really comes from your domain; it becomes harder for someone else to send email in your domain's name.
AI crawler settings
We set at network level which search engine and AI crawlers may read your website, and we measure access on the live website.
Nightly backup
We back up the data in the hotel management system to a separate store every night.
Post-release check
After every release we automatically check the encrypted connection, the security settings and the pages on the live website; if a link breaks, the alert comes to us.
How do we set it up?
We set it up in six steps; the last step repeats after every release.
- 1
Account
We open your hotel's infrastructure account; every account has a Faralya administrator login.
- 2
Domain
We register a new domain or move the settings of your existing domain to our infrastructure partner; we keep your email records during the move.
- 3
Encrypted connection
We activate the certificate and redirect visits arriving over http to the https address.
- 4
Security settings
We write the framing, permission and cache settings into the website's release file; the settings go out with every release.
- 5
Email records
We add SPF, DKIM and DMARC records for your business email.
- 6
Live measurement
After every release we measure on the live website that the settings are really in place.
Why are speed and security in the same place?
The network that protects the website also serves pages from the point closest to the guest. The same layer filters attacks and makes the page open quickly; we do not set up a separate service for each.
Fast page loading is among Google's page experience criteria. We write your website's loading speed into the monthly report with its source.
What are the limits?
These protections cover the website, the booking engine, the domain and the email infrastructure. The security of the computers, phones and network at the hotel is not part of this service.
No infrastructure can guarantee that it prevents every attack. We measure every setting we put in place on the live website; we make no claim about a protection we cannot measure.
Sources
Frequently asked questions
- On which infrastructure is our website published?
- We publish your website and booking engine on our infrastructure partner's worldwide network. We open your hotel's infrastructure account; every account has a Faralya administrator login.
- Who renews the encrypted connection certificate?
- The infrastructure renews the certificate automatically. After every release we measure the encrypted connection on the live website.
- Can we move our existing domain?
- Yes. We move your domain's settings to our infrastructure partner; we keep your email records during the move. If we register the domain new, the transfer lock is on and the registrant's personal details are hidden.
- Do these protections also cover the computers at the hotel?
- No. The protections cover the website, the booking engine, the domain and the email infrastructure; the computers, phones and network at the hotel are not part of this service.