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

...

skip EDNS-Check

skip Content-Check

check links

DNS-problem - authoritative Nameserver refused, not defined or timeout

Checked:
10.01.2025 19:39:04

Older results

No older results found

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
fw.gy-sin.ch	A	84.74.64.189 Lenzburg/Aargau/Switzerland (CH) - UPC Schweiz GmbH Hostname: 84-74-64-189.dclient.hispeed.ch	yes	1	0
	AAAA		yes
www.fw.gy-sin.ch		Name Error	yes	1	0
*.gy-sin.ch	A	Name Error	yes
	AAAA	Name Error	yes
	CNAME	Name Error	yes
*.fw.gy-sin.ch	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


	3 DNSKEY RR found


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


	Public Key with Algorithm 8, KeyTag 26470, Flags 256


	Public Key with Algorithm 8, KeyTag 61050, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 22.01.2025, 00:00:00 +, Signature-Inception: 01.01.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: ch
ch	1 DS RR in the parent zone found


	DS with Algorithm 13, KeyTag 14051, DigestType 2 and Digest q/C5xWKC8FWNWbXu8PiBt9tPOQQ5ckEf2wbmZZOp6LE=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner ch., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 23.01.2025, 17:00:00 +, Signature-Inception: 10.01.2025, 16:00:00 +, KeyTag 26470, Signer-Name: (root)


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


	3 DNSKEY RR found


	Public Key with Algorithm 13, KeyTag 442, Flags 256


	Public Key with Algorithm 13, KeyTag 14051, Flags 257 (SEP = Secure Entry Point)


	Public Key with Algorithm 13, KeyTag 57263, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner ch., Algorithm: 13, 1 Labels, original TTL: 86400 sec, Signature-expiration: 03.02.2025, 10:09:09 +, Signature-Inception: 19.12.2024, 09:09:09 +, KeyTag 14051, Signer-Name: ch


	• Status: Good - Algorithmus 13 and DNSKEY with KeyTag 14051 used to validate the DNSKEY RRSet


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

Zone: gy-sin.ch
gy-sin.ch	1 DS RR in the parent zone found


	DS with Algorithm 13, KeyTag 53392, DigestType 2 and Digest MKQvQT8ZO7hnjCM7Z7Ik6WUOaf+Juy48ia91bj4auXs=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner gy-sin.ch., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 04.02.2025, 14:43:26 +, Signature-Inception: 05.01.2025, 14:01:58 +, KeyTag 442, Signer-Name: ch


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


	2 DNSKEY RR found


	Public Key with Algorithm 13, KeyTag 24352, Flags 256


	Public Key with Algorithm 13, KeyTag 53392, Flags 257 (SEP = Secure Entry Point)


	2 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner gy-sin.ch., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 30.01.2025, 13:52:07 +, Signature-Inception: 09.01.2025, 13:15:06 +, KeyTag 24352, Signer-Name: gy-sin.ch


	RRSIG-Owner gy-sin.ch., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 30.01.2025, 13:52:07 +, Signature-Inception: 09.01.2025, 13:15:06 +, KeyTag 53392, Signer-Name: gy-sin.ch


	• Status: Good - Algorithmus 13 and DNSKEY with KeyTag 24352 used to validate the DNSKEY RRSet


	• Status: Good - Algorithmus 13 and DNSKEY with KeyTag 53392 used to validate the DNSKEY RRSet


	• Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 53392, DigestType 2 and Digest "MKQvQT8ZO7hnjCM7Z7Ik6WUOaf+Juy48ia91bj4auXs=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: fw.gy-sin.ch
fw.gy-sin.ch	0 DS RR in the parent zone found


	DS-Query in the parent zone has a valid NSEC RR as result with the domain name between the NSEC-Owner "fw.gy-sin.ch" and the NextOwner "homeassistant.gy-sin.ch". So the parent zone confirmes the non-existence of a DS RR. Bitmap: A, RRSIG, NSEC


	0 DNSKEY RR found





	RRSIG Type 1 validates the A - Result: 84.74.64.189 Validated: RRSIG-Owner fw.gy-sin.ch., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 27.01.2025, 05:06:11 +, Signature-Inception: 06.01.2025, 04:15:45 +, KeyTag 24352, Signer-Name: gy-sin.ch


	CNAME-Query sends a valid NSEC RR as result with the query name "fw.gy-sin.ch" equal the NSEC-owner "fw.gy-sin.ch" and the NextOwner "homeassistant.gy-sin.ch". So the zone confirmes the not-existence of that CNAME RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, RRSIG, NSEC Validated: RRSIG-Owner fw.gy-sin.ch., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 27.01.2025, 16:45:06 +, Signature-Inception: 06.01.2025, 16:06:52 +, KeyTag 24352, Signer-Name: gy-sin.ch


	Status: Good. NoData-Proof required and found.


	TXT-Query sends a valid NSEC RR as result with the query name "fw.gy-sin.ch" equal the NSEC-owner "fw.gy-sin.ch" and the NextOwner "homeassistant.gy-sin.ch". So the zone confirmes the not-existence of that TXT RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, RRSIG, NSEC Validated: RRSIG-Owner fw.gy-sin.ch., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 27.01.2025, 16:45:06 +, Signature-Inception: 06.01.2025, 16:06:52 +, KeyTag 24352, Signer-Name: gy-sin.ch


	Status: Good. NoData-Proof required and found.


	AAAA-Query sends a valid NSEC RR as result with the query name "fw.gy-sin.ch" equal the NSEC-owner "fw.gy-sin.ch" and the NextOwner "homeassistant.gy-sin.ch". So the zone confirmes the not-existence of that AAAA RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, RRSIG, NSEC Validated: RRSIG-Owner fw.gy-sin.ch., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 27.01.2025, 16:45:06 +, Signature-Inception: 06.01.2025, 16:06:52 +, KeyTag 24352, Signer-Name: gy-sin.ch


	Status: Good. NoData-Proof required and found.


	TLSA-Query (_443._tcp.fw.gy-sin.ch) sends a valid NSEC RR as result with the owner name fw.gy-sin.ch. So that's the Closest Encloser of the query name. TLSA-Query sends a valid NSEC RR as result and covers the Wildcard expansion of the ClosestEncloser with the owner "fw.gy-sin.ch" and the NextOwner "homeassistant.gy-sin.ch". So that NSEC confirms the not-existence of the Wildcard expansion. TLSA-Query (_443._tcp.fw.gy-sin.ch) sends a valid NSEC RR as result with the query name "_443._tcp.fw.gy-sin.ch" between the NSEC-owner "fw.gy-sin.ch" and the NextOwner "homeassistant.gy-sin.ch". So the zone confirmes the not-existence of that TLSA RR.TLSA-Query (_443._tcp.fw.gy-sin.ch) sends a valid NSEC RR as result with the parent Wildcard "*._tcp.fw.gy-sin.ch" between the NSEC-owner "fw.gy-sin.ch" and the NextOwner "homeassistant.gy-sin.ch". So the zone confirmes the not-existence of that Wildcard-expansion. Bitmap: A, RRSIG, NSEC Validated: RRSIG-Owner fw.gy-sin.ch., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 27.01.2025, 16:45:06 +, Signature-Inception: 06.01.2025, 16:06:52 +, KeyTag 24352, Signer-Name: gy-sin.ch


	Status: Good. NXDomain-Proof required and found.


	CAA-Query sends a valid NSEC RR as result with the query name "fw.gy-sin.ch" equal the NSEC-owner "fw.gy-sin.ch" and the NextOwner "homeassistant.gy-sin.ch". So the zone confirmes the not-existence of that CAA RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, RRSIG, NSEC Validated: RRSIG-Owner fw.gy-sin.ch., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 27.01.2025, 16:45:06 +, Signature-Inception: 06.01.2025, 16:06:52 +, KeyTag 24352, Signer-Name: gy-sin.ch


	Status: Good. NoData-Proof required and found.

Zone: www.fw.gy-sin.ch
www.fw.gy-sin.ch	0 DS RR in the parent zone found


	DS-Query in the parent zone has a valid NSEC RR as result with the domain name between the NSEC-Owner "fw.gy-sin.ch" and the NextOwner "homeassistant.gy-sin.ch". So the parent zone confirmes the non-existence of a DS RR. Bitmap: A, RRSIG, NSEC

3. Name Servers

Domain	Nameserver	NS-IP
www.fw.gy-sin.ch	• ns41.infomaniak.com
fw.gy-sin.ch	• ns41.infomaniak.com	83.166.143.74 Geneva/Switzerland (CH) - Infomaniak Network Management	•
	•	2001:1600:0:aaaa::3 Geneva/Switzerland (CH) - Infomaniak Network SA	•
gy-sin.ch	• ns41.infomaniak.com	83.166.143.74 Geneva/Switzerland (CH) - Infomaniak Network Management	•
	•	2001:1600:0:aaaa::3 Geneva/Switzerland (CH) - Infomaniak Network SA	•
	• ns42.infomaniak.com	83.166.143.75 Geneva/Switzerland (CH) - Infomaniak Network Management	•
	•	2001:1600:0:aaaa::4 Geneva/Switzerland (CH) - Infomaniak Network SA	•
ch	• a.nic.ch / mario.switch.ch		•
	• b.nic.ch / luigi.switch.ch		•
	• d.nic.ch / tld-all-ffm1@53039		•
	• e.nic.ch / 5.ams.pch		•
	• f.nic.ch / s2.amx		•

4. SOA-Entries

Domain:	ch
Zone-Name:	ch
Primary:	a.nic.ch
Mail:	dns-operation.switch.ch
Serial:	2025011019
Refresh:	900
Retry:	600
Expire:	1209600
TTL:	900
num Entries:	5

Domain:	gy-sin.ch
Zone-Name:	gy-sin.ch
Primary:	ns41.infomaniak.com
Mail:	hostmaster.infomaniak.ch
Serial:	2024101301
Refresh:	10800
Retry:	3600
Expire:	605800
TTL:	3600
num Entries:	4

Domain:	fw.gy-sin.ch
Zone-Name:	gy-sin.ch
Primary:	ns41.infomaniak.com
Mail:	hostmaster.infomaniak.ch
Serial:	2024101301
Refresh:	10800
Retry:	3600
Expire:	605800
TTL:	3600
num Entries:	2

Domain:	www.fw.gy-sin.ch
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	Sec.	G
• http://fw.gy-sin.ch/ 84.74.64.189	-14	10.017	T
Timeout - The operation has timed out.

• https://fw.gy-sin.ch/ 84.74.64.189	-14	10.023	T
Timeout - The operation has timed out.

• http://fw.gy-sin.ch/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 84.74.64.189	-14	10.016	T
Timeout - The operation has timed out.
Visible Content:

• https://84.74.64.189/ 84.74.64.189	-14	10.024	T
Timeout - The operation has timed out.

7. Comments

	1. General Results, most used to calculate the result
A	name "fw.gy-sin.ch" is subdomain, public suffix is ".ch", top-level-domain is ".ch", top-level-domain-type is "country-code", Country is Switzerland, tld-manager is "SWITCH The Swiss Education & Research Network", num .ch-domains preloaded: 2284 (complete: 263653)
A	Good: All ip addresses are public addresses
	Warning: Only one ip address found: fw.gy-sin.ch has only one ip address.
	Warning: No ipv6 address found. Ipv6 is the future with a lot of new features. So every domain name should have an ipv6 address. See https://en.wikipedia.org/wiki/IPv6: fw.gy-sin.ch has no ipv6 address.
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.
	Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain fw.gy-sin.ch, 1 ip addresses.
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.fw.gy-sin.ch
	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:: 9 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
A	Info:: 9 Queries complete, 9 with IPv6, 0 with IPv4.
A	Good: All DNS Queries done via IPv6.
	Ok (4 - 8):: An average of 4.5 queries per domain name server required to find all ip addresses of all name servers.
A	Info:: 2 different Name Servers found: ns41.infomaniak.com, ns42.infomaniak.com, 2 Name Servers included in Delegation: ns41.infomaniak.com, ns42.infomaniak.com, 2 Name Servers included in 1 Zone definitions: ns41.infomaniak.com, ns42.infomaniak.com, 1 Name Servers listed in SOA.Primary: ns41.infomaniak.com.
A	Good: Only one SOA.Primary Name Server found.: ns41.infomaniak.com.
A	Good: SOA.Primary Name Server included in the delegation set.: ns41.infomaniak.com.
A	Good: Consistency 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. Ordered list of name servers: ns41.infomaniak.com, ns42.infomaniak.com
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	Good: Minimal 2 different name servers (public suffix and public ip address) found: 2 different Name Servers found
A	Good: All name servers have ipv4- and ipv6-addresses.: 2 different Name Servers found
	Warning: All Name Servers have the same Top Level Domain / Public Suffix. If there is a problem with that Top Level Domain, your domain may be affected. Better: Use Name Servers with different top level domains.: 2 Name Servers, 1 Top Level Domain: com
	Warning: All Name Servers have the same domain name. If there is a problem with that domain name (or with the name servers of that domain name), your domain may be affected. Better: Use Name Servers with different domain names / different top level domains.: Only one domain name used: infomaniak.com
	Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: CH
A	Info: Ipv4-Subnet-list: 2 Name Servers, 1 different subnets (first Byte): 83., 1 different subnets (first two Bytes): 83.166., 1 different subnets (first three Bytes): 83.166.143.
X	Fatal: All Name Server IPv4 addresses from the same subnet. Check https://www.iana.org/help/nameserver-requirements to learn some basics about name server configurations. If you manage these name servers, fix it. If it's your provider, change your provider.:
A	Info: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2001:, 1 different subnets (first two blocks): 2001:1600:, 1 different subnets (first three blocks): 2001:1600:0000:, 1 different subnets (first four blocks): 2001:1600:0000:aaaa:
	Fatal: All Name Server IPv6 addresses from the same subnet.
A	Good: Nameserver supports TCP connections: 2 good Nameserver
A	Good: Nameserver supports Echo Capitalization: 2 good Nameserver
A	Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 2 good Nameserver
A	Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 2 good Nameserver
	Nameserver doesn't pass all EDNS-Checks: ns41.infomaniak.com: 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
	http://fw.gy-sin.ch/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 84.74.64.189	-14	Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
A	Info: No img element found, no alt attribute checked
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: 128393 milliseconds, 128.393 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

No CRT - CT-Log entries found

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: ns41.infomaniak.com, ns42.infomaniak.com

QNr.	Domain	Type	NS used
1	com	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	ns41.infomaniak.com	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: ns1.infomaniak.ch, ns2.infomaniak.ch
3	ns42.infomaniak.com	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: ns1.infomaniak.ch, ns2.infomaniak.ch
4	ch	NS	e.root-servers.net (2001:500:a8::e)
	Answer: a.nic.ch, b.nic.ch, d.nic.ch, e.nic.ch, f.nic.ch
5	ns1.infomaniak.ch: 2001:1600:0:aaaa::a, 84.16.66.66	NS	a.nic.ch (2001:620:0:ff::56)
	Answer: ns2.infomaniak.ch 2001:1600:0:aaaa::b, 84.16.67.66
6	ns41.infomaniak.com: 83.166.143.74	A	ns1.infomaniak.ch (2001:1600:0:aaaa::a)
7	ns41.infomaniak.com: 2001:1600:0:aaaa::3	AAAA	ns1.infomaniak.ch (2001:1600:0:aaaa::a)
8	ns42.infomaniak.com: 83.166.143.75	A	ns1.infomaniak.ch (2001:1600:0:aaaa::a)
9	ns42.infomaniak.com: 2001:1600:0:aaaa::4	AAAA	ns1.infomaniak.ch (2001:1600:0:aaaa::a)

14. CAA - Entries

Domainname	Value	∑ Queries
fw.gy-sin.ch	no CAA entry found	1
gy-sin.ch	no CAA entry found	1
ch	no CAA entry found	1

15. TXT - Entries

Domainname	TXT Entry	Status	∑ Queries
gy-sin.ch	v=spf1 include:spf.infomaniak.ch -all	ok	1
fw.gy-sin.ch		ok	1
_acme-challenge.fw.gy-sin.ch		Name Error - The domain name does not exist	1
_acme-challenge.fw.gy-sin.ch.gy-sin.ch		Name Error - The domain name does not exist	1
_acme-challenge.fw.gy-sin.ch.fw.gy-sin.ch		Name Error - The domain name does not exist	1

16. DomainService - Entries

No DomainServiceEntries entries found

17. Cipher Suites

No results

18. Portchecks

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

Permalink: https://check-your-website.server-daten.de/?i=c5fe0fb5-9618-4398-8ef4-c8e7d2bb3765

Last Result: https://check-your-website.server-daten.de/?q=fw.gy-sin.ch - 2025-01-10 19:39:04

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

<a href="https://check-your-website.server-daten.de/?q=fw.gy-sin.ch" target="_blank">Check this Site: fw.gy-sin.ch</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=fw.gy-sin.ch