Check DNS, Urls + Redirects, Certificates and Content of your Website

...

skip EDNS-Check

skip Content-Check

check links

No dns entry found - perhaps mistype. Or wrong IDN

Checked:
03.10.2025 21:37:23

Older results

No older results found

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
n8n.freask.ru		Name Error	yes	1	0
www.n8n.freask.ru		Name Error	yes	1	0
*.freask.ru	A	Name Error	yes
	AAAA	Name Error	yes
	CNAME	Name Error	yes
*.n8n.freask.ru	A	Name Error	yes
	AAAA	Name Error	yes
	CNAME	Name Error	yes

2. DNSSEC

Zone (*)	DNSSEC - Informations

Zone: (root)
(root)	1 DS RR published


	DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest 4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=


	• Status: Valid because published


	4 DNSKEY RR found


	Public Key with Algorithm 8, KeyTag 20326, Flags 257 (SEP = Secure Entry Point)


	Public Key with Algorithm 8, KeyTag 38696, Flags 257 (SEP = Secure Entry Point)


	Public Key with Algorithm 8, KeyTag 46441, Flags 256


	Public Key with Algorithm 8, KeyTag 61809, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 22.10.2025, 00:00:00 +, Signature-Inception: 01.10.2025, 00:00:00 +, KeyTag 20326, Signer-Name: (root)


	• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 20326 used to validate the DNSKEY RRSet


	• Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest "4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: ru
ru	1 DS RR in the parent zone found


	DS with Algorithm 8, KeyTag 18374, DigestType 2 and Digest gFjQwIjZs/fzAIDiuMmASUQwFyKizOnuZvasdP6y4gA=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner ru., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 16.10.2025, 17:00:00 +, Signature-Inception: 03.10.2025, 16:00:00 +, KeyTag 61809, Signer-Name: (root)


	• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 61809 used to validate the DS RRSet in the parent zone


	2 DNSKEY RR found


	Public Key with Algorithm 8, KeyTag 15580, Flags 256


	Public Key with Algorithm 8, KeyTag 18374, Flags 257 (SEP = Secure Entry Point)


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner ru., Algorithm: 8, 1 Labels, original TTL: 345600 sec, Signature-expiration: 17.10.2025, 00:00:00 +, Signature-Inception: 27.09.2025, 00:00:00 +, KeyTag 18374, Signer-Name: ru


	• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 18374 used to validate the DNSKEY RRSet


	• Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 18374, DigestType 2 and Digest "gFjQwIjZs/fzAIDiuMmASUQwFyKizOnuZvasdP6y4gA=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: freask.ru
freask.ru	0 DS RR in the parent zone found


	DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed query name "2nrbapll6b1akvalc4sn809ghglt94fo" between the hashed NSEC3-owner "2nqf2meqcsvaniba5glfkteqmga5be9h" and the hashed NextOwner "2nu5nrpt7l2rebgi6jhi3ga5kst1fq2h". So the parent zone confirmes the not-existence of a DS RR. Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 2nqf2meqcsvaniba5glfkteqmga5be9h.ru., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 30.10.2025, 16:37:15 +, Signature-Inception: 26.09.2025, 00:16:04 +, KeyTag 15580, Signer-Name: ru


	DS-Query in the parent zone sends valid NSEC3 RR with the Hash "j20c0qkdhua3cumnkst289ff06u2sq91" as Owner. That's the Hash of "ru" with the NextHashedOwnerName "j21lulr2unpa28sere28ovnjnj67qp7v". So that domain name is the Closest Encloser of "freask.ru". Opt-Out: True. Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner j20c0qkdhua3cumnkst289ff06u2sq91.ru., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 24.10.2025, 06:47:44 +, Signature-Inception: 24.09.2025, 02:16:10 +, KeyTag 15580, Signer-Name: ru


	0 DNSKEY RR found




Zone: n8n.freask.ru
n8n.freask.ru	0 DS RR in the parent zone found

Zone: www.n8n.freask.ru
www.n8n.freask.ru	0 DS RR in the parent zone found

3. Name Servers

Domain	Nameserver	NS-IP
www.n8n.freask.ru	• ns3.allns.net
n8n.freask.ru	• ns3.allns.net
freask.ru	• ns1.yandexcloud.net	84.201.185.208 Moscow/Russia (RU) - Yandex enterprise network	•
	•	2a0d:d6c1:0:1a::1b4 Moscow/Russia (RU) - Yandex.Cloud LLC	•
	• ns15.allns.net / ns5.dnska.com	185.142.35.4 Secaucus/New Jersey/United States (US) - MIRhosting B.V.	•
	• ns2.yandexcloud.net	84.201.189.229 Moscow/Russia (RU) - Yandex Cloud	•
	•	2a0d:d6c1:0:1a::2c9 Moscow/Russia (RU) - Yandex.Cloud LLC	•
	• ns3.allns.net / ns8.dnska.com	194.242.45.17 Dronten/Flevoland/The Netherlands (NL) - MIRholding B.V	•
ru	• a.dns.ripn.net / tau.ripn.net		•
	• b.dns.ripn.net / m9p-tau-12.ripn.net		•
	• d.dns.ripn.net / tau-sin.ripn.net		•
	• e.dns.ripn.net / gamma-fra.ripn.net		•
	• f.dns.ripn.net / nyk-tau-01.ripn.net		•

4. SOA-Entries

Domain:	ru
Zone-Name:	ru
Primary:	a.dns.ripn.net
Mail:	hostmaster.ripn.net
Serial:	4066203
Refresh:	86400
Retry:	14400
Expire:	2592000
TTL:	3600
num Entries:	5

Domain:	freask.ru
Zone-Name:	freask.ru
Primary:	ns1.yandexcloud.net
Mail:	mx.cloud.yandex.net
Serial:	1
Refresh:	10800
Retry:	900
Expire:	604800
TTL:	900
num Entries:	4

Domain:	freask.ru
Zone-Name:	freask.ru
Primary:	ns3.allns.net
Mail:	root.russia13.dnska.com
Serial:	2025100304
Refresh:	3600
Retry:	1800
Expire:	1209600
TTL:	86400
num Entries:	2

Domain:	n8n.freask.ru
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:	1

Domain:	www.n8n.freask.ru
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:	1

5. Screenshots

No Screenshot listed, because no url-check with https + http status 200-299, 400-599 + not-ACME-check found.

6. Url-Checks

Domainname	Http-Status	redirect	Sec.	G
•

7. Comments

	1. General Results, most used to calculate the result
A	name "n8n.freask.ru" is subdomain, public suffix is ".ru", top-level-domain is ".ru", top-level-domain-type is "country-code", Country is Russian Federation (the), tld-manager is "Coordination Center for TLD RU", num .ru-domains preloaded: 3331 (complete: 276475)
A	Good: No asked Authoritative Name Server had a timeout
A	DNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
	HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
B	No _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Read the result of server-daten.de (Url-Checks, Comments, Connections and DomainServiceRecords) to see a complete definition. Domainname: _mta-sts.n8n.freask.ru
	2. Header-Checks
U		No https result with http status 2 or 4 (standard-check) found, no header checked.
	3. DNS- and NameServer - Checks
A	Info:: 22 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers.
A	Info:: 22 Queries complete, 22 with IPv6, 0 with IPv4.
A	Good: All DNS Queries done via IPv6.
	Ok (4 - 8):: An average of 5.5 queries per domain name server required to find all ip addresses of all name servers.
A	Info:: 4 different Name Servers found: ns1.yandexcloud.net, ns15.allns.net, ns2.yandexcloud.net, ns3.allns.net, 4 Name Servers included in Delegation: ns1.yandexcloud.net, ns15.allns.net, ns2.yandexcloud.net, ns3.allns.net, 4 Name Servers included in 2 Zone definitions: ns1.yandexcloud.net, ns2.yandexcloud.net, ns15.allns.net, ns3.allns.net, 2 Name Servers listed in SOA.Primary: ns1.yandexcloud.net, ns3.allns.net.
	Error: Different SOA.Primary Name Servers found, different SOA Definitions.: ns1.yandexcloud.net,ns3.allns.net.
	Error: SOA.Primary Name Server not included in the delegation set.: ns1.yandexcloud.net,ns3.allns.net.
X	Fatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns1.yandexcloud.net (84.201.185.208): Delegation: ns1.yandexcloud.net, ns15.allns.net, ns2.yandexcloud.net, ns3.allns.net, Zone: ns1.yandexcloud.net, ns2.yandexcloud.net. Name Servers defined in Delegation, missing in Zone: ns15.allns.net, ns3.allns.net.
X	Fatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns1.yandexcloud.net (2a0d:d6c1:0:1a::1b4): Delegation: ns1.yandexcloud.net, ns15.allns.net, ns2.yandexcloud.net, ns3.allns.net, Zone: ns1.yandexcloud.net, ns2.yandexcloud.net. Name Servers defined in Delegation, missing in Zone: ns15.allns.net, ns3.allns.net.
X	Fatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns15.allns.net (185.142.35.4): Delegation: ns1.yandexcloud.net, ns15.allns.net, ns2.yandexcloud.net, ns3.allns.net, Zone: ns15.allns.net, ns3.allns.net. Name Servers defined in Delegation, missing in Zone: ns1.yandexcloud.net, ns2.yandexcloud.net.
X	Fatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns2.yandexcloud.net (84.201.189.229): Delegation: ns1.yandexcloud.net, ns15.allns.net, ns2.yandexcloud.net, ns3.allns.net, Zone: ns1.yandexcloud.net, ns2.yandexcloud.net. Name Servers defined in Delegation, missing in Zone: ns15.allns.net, ns3.allns.net.
X	Fatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns2.yandexcloud.net (2a0d:d6c1:0:1a::2c9): Delegation: ns1.yandexcloud.net, ns15.allns.net, ns2.yandexcloud.net, ns3.allns.net, Zone: ns1.yandexcloud.net, ns2.yandexcloud.net. Name Servers defined in Delegation, missing in Zone: ns15.allns.net, ns3.allns.net.
X	Fatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns3.allns.net (194.242.45.17): Delegation: ns1.yandexcloud.net, ns15.allns.net, ns2.yandexcloud.net, ns3.allns.net, Zone: ns15.allns.net, ns3.allns.net. Name Servers defined in Delegation, missing in Zone: ns1.yandexcloud.net, ns2.yandexcloud.net.
A	Good: All Name Server Domain Names have a Public Suffix.
A	Good: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
A	Good: All Name Server ip addresses are public.
A	Info: Ipv4-Subnet-list: 4 Name Servers, 3 different subnets (first Byte): 185., 194., 84., 3 different subnets (first two Bytes): 185.142., 194.242., 84.201., 4 different subnets (first three Bytes): 185.142.35., 194.242.45., 84.201.185., 84.201.189.
A	Good: Name Server IPv4-addresses from different subnet found:
A	Info: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2a0d:, 1 different subnets (first two blocks): 2a0d:d6c1:, 1 different subnets (first three blocks): 2a0d:d6c1:0000:, 1 different subnets (first four blocks): 2a0d:d6c1:0000:001a:
	Fatal: All Name Server IPv6 addresses from the same subnet.
A	Good: Nameserver supports TCP connections: 6 good Nameserver
A	Good: Nameserver supports Echo Capitalization: 6 good Nameserver
A	Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 6 good Nameserver
	Nameserver doesn't pass all EDNS-Checks: ns3.allns.net: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
	Nameserver doesn't pass all EDNS-Checks: ns3.allns.net: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
A	Good: All SOA have the same Serial Number
	Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries.
	4. Content- and Performance-critical Checks
	Info: Creating a Letsencrypt certificate with that domain name isn't possible. To create a certificate you need a registered, worldwide unique domain name. The domain name ends with a public suffix, that's good (not Grade Z). But the domain isn't registered. If you want a certificate with that domain name, you have to proof that you are the domain owner. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
A	Good: Domainname is not on the "Specially Designated Nationals And Blocked Persons List" (SDN). That's an US-list of individuals and companies owned or controlled by, or acting for or on behalf of, targeted countries. It also lists individuals, groups, and entities, such as terrorists and narcotics traffickers designated under programs that are not country-specific. Collectively, such individuals and companies are called "Specially Designated Nationals" or "SDNs." Their assets are blocked and U.S. persons are generally prohibited from dealing with them. So if a domain name is on that list, it's impossible to create a Letsencrypt certificate with that domain name. Check the list manual - https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx
A	Duration: 53730 milliseconds, 53.730 seconds

8. Connections

No connection informations found. Perhaps only http - connections.

9. Certificates

No certificate informations found. Perhaps only http - connections.

10. Last Certificates - Certificate Transparency Log Check

1. Source CertSpotter - active certificates (one check per day)

No CertSpotter - CT-Log entries found

2. Source crt.sh - old and new certificates, sometimes very slow - only certificates with "not after" > of the last months are listed

Issuer				last 7 days	active	num Certs
CN=R10, O=Let's Encrypt, C=US				0	0	6
CN=R11, O=Let's Encrypt, C=US				0	0	3
CN=R13, O=Let's Encrypt, C=US				0	0	2
CN=R12, O=Let's Encrypt, C=US				0	0	1

CRT-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
21087063128 leaf cert	CN=R12, O=Let's Encrypt, C=US	2025-09-17 12:12:41	2025-12-16 13:12:40	*.freask.ru, www.api.freask.ru, www.develop.freask.ru 3 entries
20732717294 leaf cert	CN=R13, O=Let's Encrypt, C=US	2025-09-01 21:12:01	2025-11-30 22:12:00	*.freask.ru, www.shop.freask.ru 2 entries
20532663343 leaf cert	CN=R13, O=Let's Encrypt, C=US	2025-08-24 00:12:08	2025-11-22 01:12:07	*.freask.ru, www.giver.freask.ru, www.wedding.freask.ru 3 entries
20214265408 leaf cert	CN=R10, O=Let's Encrypt, C=US	2025-08-09 00:12:04	2025-11-07 01:12:03	*.freask.ru, freask.ru 2 entries
19757201017 leaf cert	CN=R10, O=Let's Encrypt, C=US	2025-07-18 12:12:29	2025-10-16 12:12:28	*.freask.ru, www.api.freask.ru, www.develop.freask.ru 3 entries
19406193678 leaf cert	CN=R10, O=Let's Encrypt, C=US	2025-07-02 21:12:05	2025-09-30 21:12:04	*.freask.ru, www.shop.freask.ru 2 entries
19216057482 leaf cert	CN=R11, O=Let's Encrypt, C=US	2025-06-24 00:12:06	2025-09-22 00:12:05	*.freask.ru, www.giver.freask.ru, www.wedding.freask.ru 3 entries
18903022781 precert	CN=R11, O=Let's Encrypt, C=US	2025-06-09 00:12:22	2025-09-07 00:12:21	*.freask.ru, freask.ru 2 entries
18480638963 leaf cert	CN=R10, O=Let's Encrypt, C=US	2025-05-18 12:13:23	2025-08-16 12:13:22	*.freask.ru, www.api.freask.ru, www.develop.freask.ru 3 entries
18190301883 leaf cert	CN=R10, O=Let's Encrypt, C=US	2025-05-02 21:13:19	2025-07-31 21:13:18	*.freask.ru, www.shop.freask.ru 2 entries
18029661330 precert	CN=R10, O=Let's Encrypt, C=US	2025-04-24 00:13:04	2025-07-23 00:13:03	*.freask.ru, www.giver.freask.ru, www.wedding.freask.ru 3 entries
17732446798 leaf cert	CN=R11, O=Let's Encrypt, C=US	2025-04-09 00:14:18	2025-07-08 00:14:17	*.freask.ru, freask.ru 2 entries

11. Html-Content - Entries

No Html-Content entries found. Only checked if https + status 200/401/403/404

12. Html-Parsing via https://validator.w3.org/nu/

No https result http status 200 and Content-Type text/html or text/xml found, no Html-Parsing - Check

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: ns1.yandexcloud.net, ns15.allns.net, ns2.yandexcloud.net, ns3.allns.net

QNr.	Domain	Type	NS used
1	net	NS	l.root-servers.net (2001:500:9f::42)
	Answer: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net
2	ns1.yandexcloud.net	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: ns5.yandex.ru, ns6.yandex.ru
3	ns15.allns.net	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: ns1.dnska.com, ns2.dnska.com
4	ns2.yandexcloud.net	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: ns5.yandex.ru, ns6.yandex.ru
5	ns3.allns.net	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: ns1.dnska.com, ns2.dnska.com
6	ru	NS	b.root-servers.net (2001:500:200::b)
	Answer: a.dns.ripn.net, b.dns.ripn.net, d.dns.ripn.net, e.dns.ripn.net, f.dns.ripn.net
7	ns5.yandex.ru	NS	a.dns.ripn.net (2001:678:17:0:193:232:128:6)
	Answer: ns1.yandex.ru, ns2.yandex.ru
	Answer: ns1.yandex.ru 213.180.193.1, 2a02:6b8::1
	Answer: ns2.yandex.ru 2a02:6b8:0:1::1, 93.158.134.1
8	ns6.yandex.ru	NS	a.dns.ripn.net (2001:678:17:0:193:232:128:6)
	Answer: ns1.yandex.ru, ns2.yandex.ru
	Answer: ns1.yandex.ru 213.180.193.1, 2a02:6b8::1
	Answer: ns2.yandex.ru 2a02:6b8:0:1::1, 93.158.134.1
9	com	NS	d.root-servers.net (2001:500:2d::d)
	Answer: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net
10	ns1.dnska.com: 194.242.45.2, 2a03:afc0:5:2003::1	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: ns2.dnska.com 185.142.35.10
11	ns5.yandex.ru: 213.180.193.11	A	ns1.yandex.ru (2a02:6b8::1)
12	ns5.yandex.ru: 2a02:6b8::f1	AAAA	ns1.yandex.ru (2a02:6b8::1)
13	ns6.yandex.ru: 213.180.193.36	A	ns1.yandex.ru (2a02:6b8::1)
14	ns6.yandex.ru: 2a02:6b8::404	AAAA	ns1.yandex.ru (2a02:6b8::1)
15	ns1.yandexcloud.net: 84.201.185.208	A	ns5.yandex.ru (2a02:6b8::f1)
16	ns1.yandexcloud.net: 2a0d:d6c1:0:1a::1b4	AAAA	ns5.yandex.ru (2a02:6b8::f1)
17	ns15.allns.net: 185.142.35.4	A	ns1.dnska.com (2a03:afc0:5:2003::1)
18	ns15.allns.net: No AAAA record found	AAAA	ns1.dnska.com (2a03:afc0:5:2003::1)
19	ns2.yandexcloud.net: 84.201.189.229	A	ns5.yandex.ru (2a02:6b8::f1)
20	ns2.yandexcloud.net: 2a0d:d6c1:0:1a::2c9	AAAA	ns5.yandex.ru (2a02:6b8::f1)
21	ns3.allns.net: 194.242.45.17	A	ns1.dnska.com (2a03:afc0:5:2003::1)
22	ns3.allns.net: No AAAA record found	AAAA	ns1.dnska.com (2a03:afc0:5:2003::1)

14. CAA - Entries

Domainname	flag	Name	Value	∑ Queries	∑ Timeout
freask.ru	0		no CAA entry found	1	0
ru	0		no CAA entry found	1	0

15. TXT - Entries

Domainname	TXT Entry	Status	∑ Queries	∑ Timeout
freask.ru		ok	1	0
_acme-challenge.n8n.freask.ru.freask.ru		Name Error - The domain name does not exist	1	0

16. DomainService - Entries

No DomainServiceEntries entries found

17. Cipher Suites

No Ciphers found

18. Portchecks

No open Ports <> 80 / 443 found, so no additional Ports checked.

Permalink: https://check-your-website.server-daten.de/?i=7d6c34d3-ebf8-4f71-829a-4e1c80145756

Last Result: https://check-your-website.server-daten.de/?q=n8n.freask.ru - 2025-10-03 21:37:23

Do you like this page? Support this tool, add a link on your page:

<a href="https://check-your-website.server-daten.de/?q=n8n.freask.ru" target="_blank">Check this Site: n8n.freask.ru</a>

Do you really want to support this project? Donate: Check-your-website, IBAN DE98 1001 0010 0575 2211 07, SWIFT/BIC PBNKDEFF, Euro

QR-Code of this page - https://check-your-website.server-daten.de/?d=n8n.freask.ru