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

...

skip EDNS-Check

skip Content-Check

check links

Timeout

Checked:
02.12.2025 10:50:33

Older results

H - 01.12.2025 00:55:25

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
sawaji.f5.si	A	49.250.187.112 Sakai/Osaka/Japan (JP) - JCOM Hostname: zaq31fabb70.rev.zaq.ne.jp	yes	1	0
	AAAA		yes
www.sawaji.f5.si		Name Error	yes	1	0
*.sawaji.f5.si	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 38696, Flags 257 (SEP = Secure Entry Point)


	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: 21.12.2025, 00:00:00 +, Signature-Inception: 30.11.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: si
si	1 DS RR in the parent zone found


	DS with Algorithm 13, KeyTag 1635, DigestType 2 and Digest wpdzBuNDnU+NQKGn9d6p6TpAjJ+zxaoyutCP6/DrhIs=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner si., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 15.12.2025, 05:00:00 +, Signature-Inception: 02.12.2025, 04: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 13, KeyTag 1635, Flags 257 (SEP = Secure Entry Point)


	Public Key with Algorithm 13, KeyTag 9785, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner si., Algorithm: 13, 1 Labels, original TTL: 3600 sec, Signature-expiration: 12.12.2025, 23:17:07 +, Signature-Inception: 29.11.2025, 11:15:21 +, KeyTag 1635, Signer-Name: si


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


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

Zone: f5.si
f5.si	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 "2s496f7uvflbhd9aear61rl8sv4nmqsj" between the hashed NSEC3-owner "2rui5sasbjtp95ur1ncv1obakh4mvo3i" and the hashed NextOwner "2sn43gcps18c3gtvp5h3m6geqm77sr0l". So the parent zone confirmes the not-existence of a DS RR. Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 2rui5sasbjtp95ur1ncv1obakh4mvo3i.si., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 13.12.2025, 14:46:41 +, Signature-Inception: 29.11.2025, 11:15:21 +, KeyTag 9785, Signer-Name: si


	DS-Query in the parent zone sends valid NSEC3 RR with the Hash "no3eu5aipg1p9u2t7uvjakvhtq7jvkhb" as Owner. That's the Hash of "si" with the NextHashedOwnerName "npcfqr5qi2pj6aon7j0prln5tnll2rj5". So that domain name is the Closest Encloser of "f5.si". Opt-Out: True. Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner no3eu5aipg1p9u2t7uvjakvhtq7jvkhb.si., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 13.12.2025, 21:52:19 +, Signature-Inception: 29.11.2025, 11:15:21 +, KeyTag 9785, Signer-Name: si


	0 DNSKEY RR found




Zone: sawaji.f5.si
sawaji.f5.si	0 DS RR in the parent zone found


	0 DNSKEY RR found




Zone: www.sawaji.f5.si
www.sawaji.f5.si	0 DS RR in the parent zone found

3. Name Servers

Domain	Nameserver	NS-IP
www.sawaji.f5.si	• pns101.cloudns.net
sawaji.f5.si	• pns101.cloudns.net / de2-5	185.136.96.99 London/England/United Kingdom (GB) - Cloud DNS Ltd
	•	2a06:fb00:1::1:99 Sofia/Sofia-Capital/Bulgaria (BG) - Cloud DNS Ltd
f5.si	• pns101.cloudns.net / de2-5	185.136.96.99 London/England/United Kingdom (GB) - Cloud DNS Ltd
	•	2a06:fb00:1::1:99 Sofia/Sofia-Capital/Bulgaria (BG) - Cloud DNS Ltd
	• pns102.cloudns.net / de3-5	185.136.97.99 London/England/United Kingdom (GB) - Cloud DNS Ltd
	•	2a06:fb00:1::2:99 Sofia/Sofia-Capital/Bulgaria (BG) - Cloud DNS Ltd
	• pns103.cloudns.net / de2-5	185.136.98.99 London/England/United Kingdom (GB) - Cloud DNS Ltd
	•	2a06:fb00:1::3:99 Sofia/Sofia-Capital/Bulgaria (BG) - Cloud DNS Ltd
	• pns104.cloudns.net / de2-5	185.136.99.99 Warsaw/Mazovia/Poland (PL) - Cloud DNS Ltd
	•	2a06:fb00:1::4:99 Sofia/Sofia-Capital/Bulgaria (BG) - Cloud DNS Ltd
si	• b.dns.si		•
	• f.dns.si / s2.dex		•
	• h.dns.si / 11.fra.pch		•
	• i.dns.si / tld-all-ffm1@53022		•
	• k.dns.si / LHR4		•
	• l.dns.si / FRA1		•

4. SOA-Entries

Domain:	si
Zone-Name:	si
Primary:	b.dns.si
Mail:	dns.register.si
Serial:	1764666017
Refresh:	3600
Retry:	1800
Expire:	720000
TTL:	3600
num Entries:	6

Domain:	f5.si
Zone-Name:	f5.si
Primary:	pns101.cloudns.net
Mail:	support.cloudns.net
Serial:	2027016097
Refresh:	1200
Retry:	180
Expire:	1209600
TTL:	60
num Entries:	1

Domain:	f5.si
Zone-Name:	f5.si
Primary:	pns101.cloudns.net
Mail:	support.cloudns.net
Serial:	2027016098
Refresh:	1200
Retry:	180
Expire:	1209600
TTL:	60
num Entries:	7

Domain:	sawaji.f5.si
Zone-Name:	f5.si
Primary:	pns101.cloudns.net
Mail:	support.cloudns.net
Serial:	2027016107
Refresh:	1200
Retry:	180
Expire:	1209600
TTL:	60
num Entries:	2

Domain:	www.sawaji.f5.si
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://sawaji.f5.si/ 49.250.187.112	-14	10.023	T
Timeout - The operation has timed out.

• https://sawaji.f5.si/ 49.250.187.112	-14	10.517	T
Timeout - The operation has timed out.

• http://sawaji.f5.si/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 49.250.187.112	-14	10.393	T
Timeout - The operation has timed out.
Visible Content:

• https://49.250.187.112/ 49.250.187.112	-14	10.020	T
Timeout - The operation has timed out.

7. Comments

	1. General Results, most used to calculate the result
A	name "sawaji.f5.si" is domain, public suffix is ".f5.si", top-level-domain is ".si", top-level-domain-type is "country-code", Country is Slovenia, tld-manager is "Academic and Research Network of Slovenia (ARNES)", num .si-domains preloaded: 175 (complete: 276475)
A	Good: All ip addresses are public addresses
	Warning: Only one ip address found: sawaji.f5.si 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: sawaji.f5.si 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.
X	Fatal error: Nameserver doesn't support TCP connection: pns101.cloudns.net / 185.136.96.99: Timeout
X	Fatal error: Nameserver doesn't support TCP connection: pns101.cloudns.net / 2a06:fb00:1::1:99: Timeout
X	Fatal error: Nameserver doesn't support TCP connection: pns102.cloudns.net / 185.136.97.99: Timeout
X	Fatal error: Nameserver doesn't support TCP connection: pns102.cloudns.net / 2a06:fb00:1::2:99: Timeout
X	Fatal error: Nameserver doesn't support TCP connection: pns103.cloudns.net / 185.136.98.99: Timeout
X	Fatal error: Nameserver doesn't support TCP connection: pns103.cloudns.net / 2a06:fb00:1::3:99: Timeout
X	Fatal error: Nameserver doesn't support TCP connection: pns104.cloudns.net / 185.136.99.99: Timeout
X	Fatal error: Nameserver doesn't support TCP connection: pns104.cloudns.net / 2a06:fb00:1::4:99: Timeout
	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 sawaji.f5.si, 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.sawaji.f5.si
	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: pns101.cloudns.net, pns102.cloudns.net, pns103.cloudns.net, pns104.cloudns.net, 4 Name Servers included in Delegation: pns101.cloudns.net, pns102.cloudns.net, pns103.cloudns.net, pns104.cloudns.net, 4 Name Servers included in 1 Zone definitions: pns101.cloudns.net, pns102.cloudns.net, pns103.cloudns.net, pns104.cloudns.net, 1 Name Servers listed in SOA.Primary: pns101.cloudns.net.
A	Good: Only one SOA.Primary Name Server found.: pns101.cloudns.net.
A	Good: SOA.Primary Name Server included in the delegation set.: pns101.cloudns.net.
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: pns101.cloudns.net, pns102.cloudns.net, pns103.cloudns.net, pns104.cloudns.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	Good: Minimal 2 different name servers (public suffix and public ip address) found: 4 different Name Servers found
A	Good: All name servers have ipv4- and ipv6-addresses.: 4 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.: 4 Name Servers, 1 Top Level Domain: net
	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: cloudns.net
A	Good: Name servers with different Country locations found: 4 Name Servers, 3 Countries: BG, GB, PL
A	Info: Ipv4-Subnet-list: 4 Name Servers, 1 different subnets (first Byte): 185., 1 different subnets (first two Bytes): 185.136., 4 different subnets (first three Bytes): 185.136.96., 185.136.97., 185.136.98., 185.136.99.
A	Good: Name Server IPv4-addresses from different subnet found:
A	Info: IPv6-Subnet-list: 4 Name Servers with IPv6, 1 different subnets (first block): 2a06:, 1 different subnets (first two blocks): 2a06:fb00:, 1 different subnets (first three blocks): 2a06:fb00:0001:, 1 different subnets (first four blocks): 2a06:fb00:0001:0000:
	Fatal: All Name Server IPv6 addresses from the same subnet.
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: pns101.cloudns.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
	http://sawaji.f5.si/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 49.250.187.112	-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: 358880 milliseconds, 358.880 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: pns101.cloudns.net, pns102.cloudns.net, pns103.cloudns.net, pns104.cloudns.net

QNr.	Domain	Type	NS used
1	net	NS	a.root-servers.net (2001:503:ba3e::2:30)
	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	pns101.cloudns.net	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: dns2.cloudns.net, dns7.cloudns.net, ns2.cloudns.net, pns1.cloudns.net, pns4.cloudns.net, pns64.cloudns.uk
	Answer: dns2.cloudns.net 185.136.97.77, 2a06:fb00:1::2:77
	Answer: dns7.cloudns.net 185.136.98.88, 2a06:fb00:1::3:88
	Answer: ns2.cloudns.net 2a01:4ff:f0:94da::1, 5.161.86.199
	Answer: pns1.cloudns.net 185.136.96.111, 2a06:fb00:1::1:111
	Answer: pns4.cloudns.net 185.136.99.111, 2a06:fb00:1::4:111
3	pns102.cloudns.net	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: dns2.cloudns.net, dns7.cloudns.net, ns2.cloudns.net, pns1.cloudns.net, pns4.cloudns.net, pns64.cloudns.uk
	Answer: dns2.cloudns.net 185.136.97.77, 2a06:fb00:1::2:77
	Answer: dns7.cloudns.net 185.136.98.88, 2a06:fb00:1::3:88
	Answer: ns2.cloudns.net 2a01:4ff:f0:94da::1, 5.161.86.199
	Answer: pns1.cloudns.net 185.136.96.111, 2a06:fb00:1::1:111
	Answer: pns4.cloudns.net 185.136.99.111, 2a06:fb00:1::4:111
4	pns103.cloudns.net	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: dns2.cloudns.net, dns7.cloudns.net, ns2.cloudns.net, pns1.cloudns.net, pns4.cloudns.net, pns64.cloudns.uk
	Answer: dns2.cloudns.net 185.136.97.77, 2a06:fb00:1::2:77
	Answer: dns7.cloudns.net 185.136.98.88, 2a06:fb00:1::3:88
	Answer: ns2.cloudns.net 2a01:4ff:f0:94da::1, 5.161.86.199
	Answer: pns1.cloudns.net 185.136.96.111, 2a06:fb00:1::1:111
	Answer: pns4.cloudns.net 185.136.99.111, 2a06:fb00:1::4:111
5	pns104.cloudns.net	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: dns2.cloudns.net, dns7.cloudns.net, ns2.cloudns.net, pns1.cloudns.net, pns4.cloudns.net, pns64.cloudns.uk
	Answer: dns2.cloudns.net 185.136.97.77, 2a06:fb00:1::2:77
	Answer: dns7.cloudns.net 185.136.98.88, 2a06:fb00:1::3:88
	Answer: ns2.cloudns.net 2a01:4ff:f0:94da::1, 5.161.86.199
	Answer: pns1.cloudns.net 185.136.96.111, 2a06:fb00:1::1:111
	Answer: pns4.cloudns.net 185.136.99.111, 2a06:fb00:1::4:111
6	uk	NS	k.root-servers.net (2001:7fd::1)
	Answer: dns1.nic.uk, dns2.nic.uk, dns3.nic.uk, dns4.nic.uk, nsa.nic.uk, nsb.nic.uk, nsc.nic.uk, nsd.nic.uk
7	pns64.cloudns.uk: 2a06:fb00:2::4:16, 45.83.251.16	NS	dns1.nic.uk (2a01:618:400::1)
8	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
9	ns2.cloudns.com	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: ns62.cloudns.com, pns1.cloudns.net, pns2.cloudns.com, pns3.cloudns.net, pns64.cloudns.uk
	Answer: ns62.cloudns.com 2a01:4ff:f0:cba1::1, 5.161.186.200
	Answer: pns2.cloudns.com 185.136.97.111, 2a06:fb00:1::2:111
10	pns3.cloudns.net	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: dns2.cloudns.net, dns7.cloudns.net, ns2.cloudns.net, pns1.cloudns.net, pns4.cloudns.net, pns64.cloudns.uk
	Answer: dns2.cloudns.net 185.136.97.77, 2a06:fb00:1::2:77
	Answer: dns7.cloudns.net 185.136.98.88, 2a06:fb00:1::3:88
	Answer: ns2.cloudns.net 2a01:4ff:f0:94da::1, 5.161.86.199
	Answer: pns1.cloudns.net 185.136.96.111, 2a06:fb00:1::1:111
	Answer: pns4.cloudns.net 185.136.99.111, 2a06:fb00:1::4:111
11	ns2.cloudns.com: 5.161.86.199	A	ns62.cloudns.com (2a01:4ff:f0:cba1::1)
12	ns2.cloudns.com: 2a01:4ff:f0:94da::1	AAAA	ns62.cloudns.com (2a01:4ff:f0:cba1::1)
13	pns3.cloudns.net: 185.136.98.111	A	dns2.cloudns.net (2a06:fb00:1::2:77)
14	pns3.cloudns.net: 2a06:fb00:1::3:111	AAAA	dns2.cloudns.net (2a06:fb00:1::2:77)
15	pns101.cloudns.net: 185.136.96.99	A	dns2.cloudns.net (2a06:fb00:1::2:77)
16	pns101.cloudns.net: 2a06:fb00:1::1:99	AAAA	dns2.cloudns.net (2a06:fb00:1::2:77)
17	pns102.cloudns.net: 185.136.97.99	A	dns2.cloudns.net (2a06:fb00:1::2:77)
18	pns102.cloudns.net: 2a06:fb00:1::2:99	AAAA	dns2.cloudns.net (2a06:fb00:1::2:77)
19	pns103.cloudns.net: 185.136.98.99	A	dns2.cloudns.net (2a06:fb00:1::2:77)
20	pns103.cloudns.net: 2a06:fb00:1::3:99	AAAA	dns2.cloudns.net (2a06:fb00:1::2:77)
21	pns104.cloudns.net: 185.136.99.99	A	dns2.cloudns.net (2a06:fb00:1::2:77)
22	pns104.cloudns.net: 2a06:fb00:1::4:99	AAAA	dns2.cloudns.net (2a06:fb00:1::2:77)

14. CAA - Entries

Domainname	Value	∑ Queries
sawaji.f5.si	no CAA entry found	1
f5.si	no CAA entry found	1
si	no CAA entry found	1

15. TXT - Entries

Domainname	Status	∑ Queries
sawaji.f5.si	ok	1
_acme-challenge.sawaji.f5.si	Name Error - The domain name does not exist	1
_acme-challenge.sawaji.f5.si.sawaji.f5.si	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=38522d36-6bc7-4f71-9e00-510d6776c565

Last Result: https://check-your-website.server-daten.de/?q=sawaji.f5.si - 2025-12-02 10:50:33

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

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