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

0 in Queue, 0 of max. 8 Checks (06:18:34)
Why should you only use Prefix - Cookies? |
Hall of Fame - A+ and A

 

Shortcuts: 1. IP-Addresses | 2. DNSSEC | 3. Name Servers | 4. SOA-Entries | 5. Screenshots | 6. Url-Checks | 7. Comments | 8. Connections | 9. Certificates | 10. CT-Logs | 11. Html-Content | 12. Html-Parsing | 13. NameServer-IPAddresses | 14. CAA | 15. TXT | 16. DomainServiceEntries | 17. Cipher Suites | 18. Portchecks |

 

R

 

Redirect to not existing domain

 

Checked:
14.01.2026 11:05:20

 

Older results

No older results found

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
fsvm.be
A

yes
1
0

A

yes
1
0

A

yes
1
0

AAAA

yes


www.fsvm.be
CNAME
cd12078.fsvm.be
yes
1
0

CNAME
proxy03.fsvm.be
yes
1
0

CNAME
cd12078.fsvm.be
yes



A
193.190.62.74
Ghent/Flanders/Belgium (BE) - BELNET
Hostname: cd12078.irc.ugent.be
yes


*.fsvm.be
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 21831, Flags 256






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






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 01.02.2026, 00:00:00 +, Signature-Inception: 11.01.2026, 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: be

be
1 DS RR in the parent zone found






DS with Algorithm 13, KeyTag 45588, DigestType 2 and Digest aHV1w/D6RXC+OsI69A/6/F4oqN5p3oVaLbH7m00ncxk=






3 RRSIG RR to validate DS RR found






RRSIG-Owner be., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 27.01.2026, 05:00:00 +, Signature-Inception: 14.01.2026, 04:00:00 +, KeyTag 21831, Signer-Name: (root)






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






2 DNSKEY RR found






Public Key with Algorithm 13, KeyTag 19214, Flags 256






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






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner be., Algorithm: 13, 1 Labels, original TTL: 86400 sec, Signature-expiration: 01.05.2026, 21:48:30 +, Signature-Inception: 14.01.2026, 08:49:19 +, KeyTag 45588, Signer-Name: be






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






• Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 45588, DigestType 2 and Digest "aHV1w/D6RXC+OsI69A/6/F4oqN5p3oVaLbH7m00ncxk=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone



Zone: fsvm.be

fsvm.be
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 "skba5rad6454ur3260g38pkj4bjds10p" between the hashed NSEC3-owner "skb3octnafu0a74sfdt12ttqcq698uko" and the hashed NextOwner "skbaq38628bh0t704oisbvmns311kljl". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner skb3octnafu0a74sfdt12ttqcq698uko.be., Algorithm: 13, 2 Labels, original TTL: 600 sec, Signature-expiration: 05.02.2026, 21:29:42 +, Signature-Inception: 14.01.2026, 08:49:19 +, KeyTag 19214, Signer-Name: be






DS-Query in the parent zone sends valid NSEC3 RR with the Hash "pdrpqgs0t19r8qul7c2h4bhnb7agh1b8" as Owner. That's the Hash of "be" with the NextHashedOwnerName "pdrrmahc5llbo4dhp1j3tfp2jersm6g0". So that domain name is the Closest Encloser of "fsvm.be". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner pdrpqgs0t19r8qul7c2h4bhnb7agh1b8.be., Algorithm: 13, 2 Labels, original TTL: 600 sec, Signature-expiration: 05.02.2026, 10:41:07 +, Signature-Inception: 14.01.2026, 08:49:19 +, KeyTag 19214, Signer-Name: be






0 DNSKEY RR found









Zone: www.fsvm.be

www.fsvm.be
0 DS RR in the parent zone found



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 21831, Flags 256






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






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 01.02.2026, 00:00:00 +, Signature-Inception: 11.01.2026, 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: be

be
1 DS RR in the parent zone found






DS with Algorithm 13, KeyTag 45588, DigestType 2 and Digest aHV1w/D6RXC+OsI69A/6/F4oqN5p3oVaLbH7m00ncxk=






3 RRSIG RR to validate DS RR found






RRSIG-Owner be., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 27.01.2026, 05:00:00 +, Signature-Inception: 14.01.2026, 04:00:00 +, KeyTag 21831, Signer-Name: (root)






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






2 DNSKEY RR found






Public Key with Algorithm 13, KeyTag 19214, Flags 256






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






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner be., Algorithm: 13, 1 Labels, original TTL: 86400 sec, Signature-expiration: 01.05.2026, 21:48:30 +, Signature-Inception: 14.01.2026, 08:49:19 +, KeyTag 45588, Signer-Name: be






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






• Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 45588, DigestType 2 and Digest "aHV1w/D6RXC+OsI69A/6/F4oqN5p3oVaLbH7m00ncxk=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone



Zone: fsvm.be

fsvm.be
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 "skba5rad6454ur3260g38pkj4bjds10p" between the hashed NSEC3-owner "skb3octnafu0a74sfdt12ttqcq698uko" and the hashed NextOwner "skbaq38628bh0t704oisbvmns311kljl". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner skb3octnafu0a74sfdt12ttqcq698uko.be., Algorithm: 13, 2 Labels, original TTL: 600 sec, Signature-expiration: 05.02.2026, 21:29:42 +, Signature-Inception: 14.01.2026, 08:49:19 +, KeyTag 19214, Signer-Name: be






DS-Query in the parent zone sends valid NSEC3 RR with the Hash "pdrpqgs0t19r8qul7c2h4bhnb7agh1b8" as Owner. That's the Hash of "be" with the NextHashedOwnerName "pdrrmahc5llbo4dhp1j3tfp2jersm6g0". So that domain name is the Closest Encloser of "fsvm.be". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner pdrpqgs0t19r8qul7c2h4bhnb7agh1b8.be., Algorithm: 13, 2 Labels, original TTL: 600 sec, Signature-expiration: 05.02.2026, 10:41:07 +, Signature-Inception: 14.01.2026, 08:49:19 +, KeyTag 19214, Signer-Name: be






0 DNSKEY RR found









Zone: cd12078.fsvm.be

cd12078.fsvm.be
0 DS RR in the parent zone found






0 DNSKEY RR found









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 21831, Flags 256






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






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 01.02.2026, 00:00:00 +, Signature-Inception: 11.01.2026, 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: be

be
1 DS RR in the parent zone found






DS with Algorithm 13, KeyTag 45588, DigestType 2 and Digest aHV1w/D6RXC+OsI69A/6/F4oqN5p3oVaLbH7m00ncxk=






3 RRSIG RR to validate DS RR found






RRSIG-Owner be., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 27.01.2026, 05:00:00 +, Signature-Inception: 14.01.2026, 04:00:00 +, KeyTag 21831, Signer-Name: (root)






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






2 DNSKEY RR found






Public Key with Algorithm 13, KeyTag 19214, Flags 256






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






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner be., Algorithm: 13, 1 Labels, original TTL: 86400 sec, Signature-expiration: 01.05.2026, 21:48:30 +, Signature-Inception: 14.01.2026, 08:49:19 +, KeyTag 45588, Signer-Name: be






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






• Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 45588, DigestType 2 and Digest "aHV1w/D6RXC+OsI69A/6/F4oqN5p3oVaLbH7m00ncxk=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone



Zone: fsvm.be

fsvm.be
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 "skba5rad6454ur3260g38pkj4bjds10p" between the hashed NSEC3-owner "skb3octnafu0a74sfdt12ttqcq698uko" and the hashed NextOwner "skbaq38628bh0t704oisbvmns311kljl". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner skb3octnafu0a74sfdt12ttqcq698uko.be., Algorithm: 13, 2 Labels, original TTL: 600 sec, Signature-expiration: 05.02.2026, 21:29:42 +, Signature-Inception: 14.01.2026, 08:49:19 +, KeyTag 19214, Signer-Name: be






DS-Query in the parent zone sends valid NSEC3 RR with the Hash "pdrpqgs0t19r8qul7c2h4bhnb7agh1b8" as Owner. That's the Hash of "be" with the NextHashedOwnerName "pdrrmahc5llbo4dhp1j3tfp2jersm6g0". So that domain name is the Closest Encloser of "fsvm.be". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner pdrpqgs0t19r8qul7c2h4bhnb7agh1b8.be., Algorithm: 13, 2 Labels, original TTL: 600 sec, Signature-expiration: 05.02.2026, 10:41:07 +, Signature-Inception: 14.01.2026, 08:49:19 +, KeyTag 19214, Signer-Name: be






0 DNSKEY RR found









Zone: proxy03.fsvm.be

proxy03.fsvm.be
0 DS RR in the parent zone found

 

3. Name Servers

DomainNameserverNS-IP
fsvm.be
•  ns01.fsvm.be
193.190.62.7
Ghent/Flanders/Belgium (BE) - BELNET		•

•  ns02.fsvm.be
193.190.62.8
Ghent/Flanders/Belgium (BE) - BELNET		•

•  ns03.fsvm.be
157.193.231.208
Ghent/Flanders/Belgium (BE) - BELNET		•
be
•  a.nsset.be / zaventem3.ns.prodng.dc3.be
•

•  b.nsset.be / heverlee1.ns.prodng.dc3.be
•

•  c.nsset.be / prague1.ns.prodng.dc3.be
•

•  d.nsset.be / brussels2.ns.prodng.dc3.be
•

•  y.nsset.be / dns4.defra1
•

•  z.nsset.be / tld-all-ffm1@53036
•
cd12078.fsvm.be
•  ns01.fsvm.be
193.190.62.7
Ghent/Flanders/Belgium (BE) - BELNET		•
fsvm.be
•  ns01.fsvm.be
193.190.62.7
Ghent/Flanders/Belgium (BE) - BELNET		•

• 
193.190.62.7
Ghent/Flanders/Belgium (BE) - BELNET		•

•  ns02.fsvm.be
193.190.62.8
Ghent/Flanders/Belgium (BE) - BELNET		•

• 
193.190.62.8
Ghent/Flanders/Belgium (BE) - BELNET		•

•  ns03.fsvm.be
157.193.231.208
Ghent/Flanders/Belgium (BE) - BELNET		•

• 
157.193.231.208
Ghent/Flanders/Belgium (BE) - BELNET		•
be
•  a.nsset.be / zaventem3.ns.prodng.dc3.be
•

•  a.nsset.be / zaventem3.ns.prodng.dc3.be
•

•  b.nsset.be / heverlee1.ns.prodng.dc3.be
•

•  b.nsset.be / heverlee1.ns.prodng.dc3.be
•

•  c.nsset.be / prague1.ns.prodng.dc3.be
•

•  c.nsset.be / prague1.ns.prodng.dc3.be
•

•  d.nsset.be / brussels2.ns.prodng.dc3.be
•

•  d.nsset.be / brussels2.ns.prodng.dc3.be
•

•  y.nsset.be / dns3.defra1
•

•  y.nsset.be / dns2.defra1
•

•  z.nsset.be / tld-all-ffm1@53036
•

•  z.nsset.be / tld-all-ffm1@53036
•

 

4. SOA-Entries


Domain:be
Zone-Name:be
Primary:a.nsset.be
Mail:be-hostmaster.dnsbelgium.be
Serial:1028228986
Refresh:3600
Retry:1800
Expire:2419200
TTL:600
num Entries:6


Domain:fsvm.be
Zone-Name:fsvm.be
Primary:ns01.fsvm.be
Mail:itsupport.irc.vib-ugent.be
Serial:2026011304
Refresh:3600
Retry:900
Expire:1209600
TTL:1800
num Entries:3


Domain:be
Zone-Name:be
Primary:a.nsset.be
Mail:be-hostmaster.dnsbelgium.be
Serial:1028228986
Refresh:3600
Retry:1800
Expire:2419200
TTL:600
num Entries:6


Domain:fsvm.be
Zone-Name:fsvm.be
Primary:ns01.fsvm.be
Mail:itsupport.irc.vib-ugent.be
Serial:2026011304
Refresh:3600
Retry:900
Expire:1209600
TTL:1800
num Entries:3


Domain:cd12078.fsvm.be
Zone-Name:fsvm.be
Primary:ns01.fsvm.be
Mail:itsupport.irc.vib-ugent.be
Serial:2026011304
Refresh:3600
Retry:900
Expire:1209600
TTL:1800
num Entries:1


Domain:be
Zone-Name:be
Primary:a.nsset.be
Mail:be-hostmaster.dnsbelgium.be
Serial:1028228986
Refresh:3600
Retry:1800
Expire:2419200
TTL:600
num Entries:6


Domain:fsvm.be
Zone-Name:fsvm.be
Primary:ns01.fsvm.be
Mail:itsupport.irc.vib-ugent.be
Serial:2026011304
Refresh:3600
Retry:900
Expire:1209600
TTL:1800
num Entries:3


5. Screenshots

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

 

 

6. Url-Checks


:

:
DomainnameHttp-StatusredirectSec.G
• http://www.fsvm.be/
193.190.62.74
302
http://.irc.ugent.be/
Html is minified: 110.69 %
0.043
D
Server: nginx/1.20.1
Date: Wed, 14 Jan 2026 10:06:18 GMT
Connection: keep-alive
Location: http://.irc.ugent.be/
Content-Type: text/html
Content-Length: 145

• http://.irc.ugent.be/

-101


0.006
R
Error parsing Url "http://.irc.ugent.be/"

• https://www.fsvm.be/
193.190.62.74
302
https://.irc.ugent.be/
Html is minified: 110.69 %
2.196
N
Certificate error: RemoteCertificateNameMismatch
Server: nginx/1.20.1
Date: Wed, 14 Jan 2026 10:06:18 GMT
Connection: keep-alive
Location: https://.irc.ugent.be/
Strict-Transport-Security: max-age=63072000
Content-Type: text/html
Content-Length: 145

• https://.irc.ugent.be/

-101


0.006
R
Error parsing Url "https://.irc.ugent.be/"

• http://www.fsvm.be/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
193.190.62.74
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0		302
http://.irc.ugent.be/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Html is minified: 110.69 %
Other inline scripts (∑/total): 0/0		0.023
D
Visible Content:
Server: nginx/1.20.1
Date: Wed, 14 Jan 2026 10:06:22 GMT
Connection: keep-alive
Location: http://.irc.ugent.be/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Content-Type: text/html
Content-Length: 145

• http://.irc.ugent.be/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

-101


0.006
R
Error parsing Url "http://.irc.ugent.be/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de"
Visible Content:

• https://193.190.62.74/
193.190.62.74
302
https://.irc.ugent.be/
Html is minified: 110.69 %
2.167
N
Certificate error: RemoteCertificateNameMismatch
Server: nginx/1.20.1
Date: Wed, 14 Jan 2026 10:06:22 GMT
Connection: keep-alive
Location: https://.irc.ugent.be/
Strict-Transport-Security: max-age=63072000
Content-Type: text/html
Content-Length: 145

 

7. Comments


1. General Results, most used to calculate the result

Aname "fsvm.be" is domain, public suffix is ".be", top-level-domain is ".be", top-level-domain-type is "country-code", Country is Belgium, tld-manager is "DNS Belgium vzw/asbl", num .be-domains preloaded: 1496 (complete: 276475)
AGood: All ip addresses are public addresses
Warning: Only one ip address found: www.fsvm.be 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: www.fsvm.be has no ipv6 address.
AGood: No asked Authoritative Name Server had a timeout
AGood: No cookie sent via http.
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
CError - no version with Http-Status 200
Dhttp://www.fsvm.be/ 193.190.62.74
302
http://.irc.ugent.be/
Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
Dhttp://www.fsvm.be/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 193.190.62.74
302
http://.irc.ugent.be/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
HFatal error: No https - result with http-status 200, no encryption
Nhttps://www.fsvm.be/ 193.190.62.74
302
https://.irc.ugent.be/
Error - Certificate isn't trusted, RemoteCertificateNameMismatch
Nhttps://193.190.62.74/ 193.190.62.74
302
https://.irc.ugent.be/
Error - Certificate isn't trusted, RemoteCertificateNameMismatch
Rhttp://www.fsvm.be/ 193.190.62.74
302
http://.irc.ugent.be/
Redirect to not existing domain
Rhttps://www.fsvm.be/ 193.190.62.74
302
https://.irc.ugent.be/
Redirect to not existing domain
Rhttp://www.fsvm.be/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 193.190.62.74
302
http://.irc.ugent.be/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Redirect to not existing domain
Rhttps://193.190.62.74/ 193.190.62.74
302
https://.irc.ugent.be/
Redirect to not existing domain
Info: Checking all ip addresses of that domain without sending the hostname only one certificate found. Checking all ip addresses and sending the hostname only one certificate found. Both certificates are the same. So that domain doesn't require Server Name Indication (SNI), it's the primary certificate of that set of ip addresses.: Domain www.fsvm.be, 1 ip addresses, 1 different http results.
BNo _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.fsvm.be

2. Header-Checks

U

No https result with http status 2** or 4** (standard-check) found, no header checked.

3. DNS- and NameServer - Checks

AInfo:: 2 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 3 Name Servers.
AInfo:: 2 Queries complete, 2 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
AGood: Some ip addresses of name servers found with the minimum of two DNS Queries. One to find the TLD-Zone, one to ask the TLD-Zone.ns01.fsvm.be (193.190.62.7), ns02.fsvm.be (193.190.62.8), ns03.fsvm.be (157.193.231.208)
AGood (1 - 3.0):: An average of 0.7 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 3 different Name Servers found: ns01.fsvm.be, ns02.fsvm.be, ns03.fsvm.be, 3 Name Servers included in Delegation: ns01.fsvm.be, ns02.fsvm.be, ns03.fsvm.be, 3 Name Servers included in 1 Zone definitions: ns01.fsvm.be, ns02.fsvm.be, ns03.fsvm.be, 1 Name Servers listed in SOA.Primary: ns01.fsvm.be.
AGood: Only one SOA.Primary Name Server found.: ns01.fsvm.be.
AGood: SOA.Primary Name Server included in the delegation set.: ns01.fsvm.be.
AGood: 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: ns01.fsvm.be, ns02.fsvm.be, ns03.fsvm.be
AGood: All Name Server Domain Names have a Public Suffix.
AGood: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
AGood: All Name Server ip addresses are public.
AGood: Minimal 2 different name servers (public suffix and public ip address) found: 3 different Name Servers found
Warning: No Name Server IPv6 address found. IPv6 is the future, so your name servers should be visible via IPv6.: 3 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.: 3 Name Servers, 1 Top Level Domain: be
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: fsvm.be
Warning: All Name Servers from the same Country / IP location.: 3 Name Servers, 1 Countries: BE
AInfo: Ipv4-Subnet-list: 3 Name Servers, 2 different subnets (first Byte): 157., 193., 2 different subnets (first two Bytes): 157.193., 193.190., 2 different subnets (first three Bytes): 157.193.231., 193.190.62.
AGood: Name Server IPv4-addresses from different subnet found:
AGood: Nameserver supports TCP connections: 9 good Nameserver
AGood: Nameserver supports Echo Capitalization: 9 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 9 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 9 good Nameserver
AGood: 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://.irc.ugent.be/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
-101

Fatal: Check of /.well-known/acme-challenge/random-filename redirects to not-existing domain. Creating a Letsencrypt certificate via http-01 challenge can't work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
AInfo: No img element found, no alt attribute checked
AGood: 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
ADuration: 109586 milliseconds, 109.586 seconds

 

8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
www.fsvm.be
193.190.62.74
443
name does not match
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok
www.fsvm.be
193.190.62.74
443
name does not match
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok
http/2 via ALPN supported 
Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
http/2 via ALPN supported
 Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
Chain (complete)

1CN=*.irc.ugent.be


2CN=E7, O=Let's Encrypt, C=US


193.190.62.74
193.190.62.74
443
name does not match
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok

193.190.62.74
193.190.62.74
443
name does not match
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok
http/2 via ALPN supported 
Cert sent without SNI 		Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
http/2 via ALPN supported
Cert sent without SNI 		Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
Chain (complete)

1CN=*.irc.ugent.be


2CN=E7, O=Let's Encrypt, C=US

 

9. Certificates

1.
1.
CN=*.irc.ugent.be
01.01.2026
01.04.2026
expires in 46 days		*.irc.ugent.be - 1 entry
1.
1.
CN=*.irc.ugent.be
01.01.2026

01.04.2026
expires in 46 days


*.irc.ugent.be - 1 entry

KeyalgorithmEC Public Key (256 bit, prime256v1)
Signatur:ECDSA SHA384
Serial Number:061029BF9CD7D78AC7180BC37EFD20C178FC
Thumbprint:DF52BE672D302F57462FED5C02C0728C22CE5D87
SHA256 / Certificate:tk60PUCm/BQ3fsvK8iTFyci0fog6s4V0wUGpeniN3Q8=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):d0746238798912140f72a31e3938ace29ca53c20e9a2d3b3a9a83e54d3f962ed
SHA256 hex / Subject Public Key Information (SPKI):d0746238798912140f72a31e3938ace29ca53c20e9a2d3b3a9a83e54d3f962ed (is buggy, ignore the result)
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:
OCSP - must staple:no
Certificate Transparency:yes
Enhanced Key Usage:Serverauthentifizierung (1.3.6.1.5.5.7.3.1), Clientauthentifizierung (1.3.6.1.5.5.7.3.2)




2.
CN=E7, O=Let's Encrypt, C=US
13.03.2024
13.03.2027
expires in 392 days

2.
CN=E7, O=Let's Encrypt, C=US
13.03.2024

13.03.2027
expires in 392 days




KeyalgorithmEC Public Key (384 bit, secp384r1)
Signatur:SHA256 With RSA-Encryption
Serial Number:00AA75F1E62B8F0A220966D38BBFD4BAA1
Thumbprint:3B73C17E3DF87CF3AA77F1389219EB5EDD519E7F
SHA256 / Certificate:rrH9dBDoO8lvXaPGp8LBu4NtH6XLhucIUViQ5Ciodws=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):cbbc559b44d524d6a132bdac672744da3407f12aae5d5f722c5f6c7913871c75
SHA256 hex / Subject Public Key Information (SPKI):
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Check unknown. No result 404 / 200
OCSP - Url:
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:Clientauthentifizierung (1.3.6.1.5.5.7.3.2), Serverauthentifizierung (1.3.6.1.5.5.7.3.1)




3.
CN=ISRG Root X1, O=Internet Security Research Group, C=US
04.06.2015
04.06.2035
expires in 3397 days

3.
CN=ISRG Root X1, O=Internet Security Research Group, C=US
04.06.2015

04.06.2035
expires in 3397 days




KeyalgorithmRSA encryption (4096 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:008210CFB0D240E3594463E0BB63828B00
Thumbprint:CABD2A79A1076A31F21D253635CB039D4329A5E8
SHA256 / Certificate:lrzsBiZJdvN0YHeazyjFp8/oo8Cq4RqP/O4FwL3fCMY=
SHA256 hex / Cert (DANE * 0 1):96bcec06264976f37460779acf28c5a7cfe8a3c0aae11a8ffcee05c0bddf08c6
SHA256 hex / PublicKey (DANE * 1 1):0b9fa5a59eed715c26c1020c711b4f6ec42d58b0015e14337a39dad301c5afc3
SHA256 hex / Subject Public Key Information (SPKI):0b9fa5a59eed715c26c1020c711b4f6ec42d58b0015e14337a39dad301c5afc3
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:




 

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: ns01.fsvm.be, ns02.fsvm.be, ns03.fsvm.be

 

QNr.DomainTypeNS used
1
be
NS
d.root-servers.net (2001:500:2d::d)

Answer: a.nsset.be, b.nsset.be, c.nsset.be, d.nsset.be, y.nsset.be, z.nsset.be
2
ns01.fsvm.be: 193.190.62.7
NS
a.nsset.be (2001:678:9::1)

Answer: ns02.fsvm.be
193.190.62.8

Answer: ns03.fsvm.be
157.193.231.208

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
cd12078.fsvm.be
0

no CAA entry found
1
0
proxy03.fsvm.be



1
0
www.fsvm.be



1
0
fsvm.be
0

no CAA entry found
1
0

0

no CAA entry found
1
0

0

no CAA entry found
1
0
be
0

no CAA entry found
1
0

0

no CAA entry found
1
0

0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
fsvm.be
v=spf1 ip4:193.190.198.240 ip4:157.193.189.5 ip6:2001:6a8:3c80::240 include:_spf.fsvm.be ~all
ok
1
0
www.fsvm.be


1
0
cd12078.fsvm.be

ok
1
0
proxy03.fsvm.be


1
0
_acme-challenge.fsvm.be
_certbot_validation_placeholder_
missing entry or wrong length
1
0
_acme-challenge.www.fsvm.be

Name Error - The domain name does not exist
1
0
_acme-challenge.fsvm.be.fsvm.be

Name Error - The domain name does not exist
1
0
_acme-challenge.cd12078.fsvm.be

Name Error - The domain name does not exist
1
0
_acme-challenge.proxy03.fsvm.be

Name Error - The domain name does not exist
1
0
_acme-challenge.www.fsvm.be.fsvm.be

Name Error - The domain name does not exist
1
0
_acme-challenge.www.fsvm.be.www.fsvm.be

Name Error - The domain name does not exist
1
0
_acme-challenge.proxy03.fsvm.be.proxy03.fsvm.be

Name Error - The domain name does not exist
1
0
_acme-challenge.cd12078.fsvm.be.cd12078.fsvm.be

Name Error - The domain name does not exist
1
0

 

16. DomainService - Entries

TypeDomainPrefValueDNS-errornum AnswersStatusDescription
MX

fsvm.be
10
smtp2.fsvm.be
03ok

A


193.190.62.106
01ok

CNAME


00ok
MX

fsvm.be
20
smtp1.fsvm.be
03ok

A


193.190.62.71
01ok

CNAME


00ok
MX

fsvm.be
30
irc.bams.belnet.be
03ok

A


193.190.198.240
01ok

AAAA


2001:6a8:3c80::240
01ok

CNAME


00ok
SPF
TXT
fsvm.be

v=spf1 ip4:193.190.198.240 ip4:157.193.189.5 ip6:2001:6a8:3c80::240 include:_spf.fsvm.be ~all
ok

TXT
_spf.fsvm.be

v=spf1 mx
8Invalid record: Last element (except exp) must be "all" or "redirect".

MX
_spf.fsvm.be

128PermError: Domainname defined, but no MX entry found.
_dmarc
TXT
_dmarc.fsvm.be

v=DMARC1;p=none;sp=none;pct=100;fo=1;ruf=mailto:postmaster-dmarc-for@fsvm.be;rua=mailto:postmaster-dmarc-agg@fsvm.be
ok

				 
			

				 
			
17. Cipher Suites
Summary
DomainIPPortnum CipherstimeStd.ProtocolForward Secrecy
www.fsvm.be
193.190.62.74
443
3 Ciphers29.65 sec
0 without, 3 FS
100.00 %
Complete

1
3 Ciphers
3.00 Ciphers/Check		29.65 sec29.65 sec/Check
0 without, 3 FS
100.00 %

Details
DomainIPPortCipher (OpenSsl / IANA)
www.fsvm.be
193.190.62.74
443
ECDHE-ECDSA-CHACHA20-POLY1305
 (Recommended)
TLSv1.2
0xCC,0xA9
 FS
3 Ciphers, 

29.65 sec
TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256

ECDH
ECDSA
CHACHA20/POLY1305(256)
AEAD




ECDHE-ECDSA-AES256-GCM-SHA384
 (Recommended)
TLSv1.2
0xC0,0x2C
 FS

TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384

ECDH
ECDSA
AESGCM(256)
AEAD




ECDHE-ECDSA-AES128-GCM-SHA256
 (Recommended)
TLSv1.2
0xC0,0x2B
 FS

TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256

ECDH
ECDSA
AESGCM(128)
AEAD


				 
			
18. Portchecks



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



				 
			

				 
			

Permalink: https://check-your-website.server-daten.de/?i=8c074a23-2aaf-4689-8552-b866c4b6c7f4

				 
			


Last Result: https://check-your-website.server-daten.de/?q=fsvm.be - 2026-01-14 11:05:20

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

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

				 
			

				 
			



Jürgen Auer • Friedenstr. 37 • 10249 Berlin • +49(0)30 420 200 60 • info@sql-und-xml.de • 
USt-IdNr.: DE221734518

				 
			


Errors, ideas, questions? Use the 
Contact form • A project using

Server-Daten - Web Database solutions