<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Topics tagged with cloudflare]]></title><description><![CDATA[A list of topics that have been tagged with cloudflare]]></description><link>https://community.secnto.com//tags/cloudflare</link><generator>RSS for Node</generator><lastBuildDate>Mon, 08 Jun 2026 23:23:50 GMT</lastBuildDate><atom:link href="https://community.secnto.com//tags/cloudflare.rss" rel="self" type="application/rss+xml"/><pubDate>Invalid Date</pubDate><ttl>60</ttl><item><title><![CDATA[how to point dns like 2nd level subdomain of subdomain]]></title><description><![CDATA[@Engrnaveed-Saeed said in how to point dns like 2nd level subdomain of subdomain:

how to create subdomain in godaddy - youtube
how to create subdomain in godaddy without cpanel
godaddy subdomain forwarding
how to create subdomain in cpanel
how to create a subdomain in wordpress godaddy
how to create subdomain without cpanel
godaddy subdomain mx record
google domains

To point a second-level subdomain of a subdomain (like level2.level1.example.com) using DNS, follow these steps:

Access Your DNS Management System

Log in to your DNS hosting provider or control panel where the DNS records for your domain are managed.

Add an “A” or “CNAME” Record for the Second-Level Subdomain

You can create the DNS entry by adding an A or CNAME record, depending on how you want the subdomain to resolve.
For an A Record (Points directly to an IP address):
1.	Choose the option to add a new record.
2.	Select A Record as the type.
3.	In the Name field, input the second-level subdomain in the format level2.level1. This creates a subdomain of a subdomain.
4.	Enter the IP address where you want the subdomain to point.
5.	Set TTL (time to live) if necessary (default is usually fine).

For a CNAME Record (Alias to another domain):
1.	Choose the option to add a new record.
2.	Select CNAME Record as the type.
3.	In the Name field, input level2.level1.
4.	In the Value/Target field, enter the domain name (e.g., example.com) to which you want to alias this subdomain.
5.	Set the TTL (optional).


Ensure the Main Subdomain (level1.example.com) Is Set

If level1.example.com does not already exist, make sure to create a DNS record for level1 by adding either an A record or CNAME for it.

Save and Propagate

After saving the changes, it may take up to 24–48 hours for the DNS changes to propagate fully across the internet.
Example:
If you want shop.us.example.com to point to a server:
•	For an A record:
•	Name: shop.us
•	Type: A
•	Value: 192.0.2.1
•	For a CNAME record:
•	Name: shop.us
•	Type: CNAME
•	Value: store.example.com

Let me know if you need further clarification!
]]></description><link>https://community.secnto.com//topic/2675/how-to-point-dns-like-2nd-level-subdomain-of-subdomain</link><guid isPermaLink="true">https://community.secnto.com//topic/2675/how-to-point-dns-like-2nd-level-subdomain-of-subdomain</guid><dc:creator><![CDATA[cyberian]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[HTTP Strict Transport Security (HSTS)]]></title><description><![CDATA[@Danial-Ahmed said in HTTP Strict Transport Security (HSTS):

How to Enable HTTP Strict Transport Security (HSTS) Policy for following SSL certificates
— Free Let’s Encrypt SSL Certificate.
— Free Let’s Encrypt Wildcard SSL Certificate.
— Custom SSL Certificate.


Before enabling HSTS policy, you need to make sure that the SSL Certificate is deployed on your website, and HTTP to HTTPS redirection is implemented. The following kinds of SSL Certificates can be installed.
Now, you need to connect to your server remotely via SSH so you can access  .htaccess  file of your application.
Now, you need to go to that specific directory where your webroot is located. In other words, where your  .htaccess  file is located. By default, it is in  public_html  directory so enter a command mentioned below to go into the  public_html  folder.

cd applications/&lt;your_application_name&gt;/public_html/

4.1. Here comes the final step of editing the  .htaccess  file and adding the HSTS rule. Executing the below command will open the file for editing.
vim .htaccess

4.2. Once the file is opened, you need to press  i  key to go into the editing mode. You will see  – – INSERT – –  in the bottom of your screen after pressing the key.
4.3. Then, copy this HSTS  rule and paste the rule before the instance where it says  # BEGIN WordPress/etc .
Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains; preload" env=HTTPS

Then, copy this HSTS  rule and paste the rule before the instance where it says  # BEGIN WordPress/etc .
Header always set Strict-Transport-Security “max-age=31536000; includeSubDomains; preload” env=HTTPS
This rule defines one-year max-age access, which includes your website’s root domain and any subdomains. Once the browser has accessed the website, then it will no longer be able to access the unsecured version (HTTP) of a website for a year. Please make sure that all subdomains are covered in your SSL Certificate, and HTTPS redirection is enabled. If you fail to do so, then your subdomains will no be accessible after saving changes in the  .htaccess  file.
Note: Before adding the one-year max-age, test your entire website with five minutes max-age first using: max-age=300;
4.4. Finally, press  ESC  key to exit the editing mode and then type and run the below command to save the changes.
Tip: This command can’t be copied and pasted, you need to type the command and hit Enter key.
:wq!

]]></description><link>https://community.secnto.com//topic/2056/http-strict-transport-security-hsts</link><guid isPermaLink="true">https://community.secnto.com//topic/2056/http-strict-transport-security-hsts</guid><dc:creator><![CDATA[zaasmi]]></dc:creator><pubDate>Invalid Date</pubDate></item></channel></rss>