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

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


	2 DNSKEY RR found


	Public Key with Algorithm 8, KeyTag 20038, Flags 256


	Public Key with Algorithm 8, KeyTag 20326, 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: 30.09.2024, 00:00:00 +, Signature-Inception: 09.09.2024, 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	2 DS RR in the parent zone found


	DS with Algorithm 8, KeyTag 12664, DigestType 2 and Digest dRQemxGIqVp6hVv0fieKdCpePy3e7Y6ZXXSdSPLw5y0=


	DS with Algorithm 8, KeyTag 52756, DigestType 2 and Digest VIWsM918ftI36ipL0mlzHIFpYP4YEEICRIS1zspuzJ8=


	1 RRSIG RR to validate DS RR found


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


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


	5 DNSKEY RR found


	Public Key with Algorithm 8, KeyTag 3303, Flags 256


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


	Public Key with Algorithm 8, KeyTag 23343, Flags 256


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


	Public Key with Algorithm 8, KeyTag 64521, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner be., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 06.10.2024, 15:39:18 +, Signature-Inception: 20.06.2024, 10:31:50 +, KeyTag 52756, Signer-Name: be


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


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

Zone: surfgate.be
surfgate.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 "clqh12vb2u48evv5gttfjh97imsfercd" between the hashed NSEC3-owner "clqg64cjusrvscdkqgekqbffve67oper" and the hashed NextOwner "clqkepsa4j8aq7aehtdddogjorf82huu". So the parent zone confirmes the not-existence of a DS RR. Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner clqg64cjusrvscdkqgekqbffve67oper.be., Algorithm: 8, 2 Labels, original TTL: 600 sec, Signature-expiration: 01.10.2024, 07:57:30 +, Signature-Inception: 09.09.2024, 09:11:14 +, KeyTag 23343, 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 "surfgate.be". Opt-Out: True. Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner pdrpqgs0t19r8qul7c2h4bhnb7agh1b8.be., Algorithm: 8, 2 Labels, original TTL: 600 sec, Signature-expiration: 03.10.2024, 00:29:19 +, Signature-Inception: 12.09.2024, 12:09:18 +, KeyTag 23343, Signer-Name: be


	The ClosestEncloser says, that "*.be" with the Hash "e43ka3mngvd2bo0ud2smavr3i9i60edb" is a possible Wildcard of the DS Query Name. But the DS-Query in the parent zone sends a valid NSEC3 RR With the owner "e43jlmfjm7b0ob359cku1oek7gqqrdgd" and the Next Owner "e43kejdv5nitcur0e43htlagrlhjpv44", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: True Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner e43jlmfjm7b0ob359cku1oek7gqqrdgd.be., Algorithm: 8, 2 Labels, original TTL: 600 sec, Signature-expiration: 01.10.2024, 05:53:40 +, Signature-Inception: 08.09.2024, 16:47:15 +, KeyTag 23343, Signer-Name: be

Zone: www.surfgate.be
www.surfgate.be	0 DS RR in the parent zone found


	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 "www.surfgate.be". Opt-Out: True. Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner pdrpqgs0t19r8qul7c2h4bhnb7agh1b8.be., Algorithm: 8, 2 Labels, original TTL: 600 sec, Signature-expiration: 03.10.2024, 00:29:19 +, Signature-Inception: 12.09.2024, 12:09:18 +, KeyTag 23343, Signer-Name: be


	The ClosestEncloser says, that "*.be" with the Hash "e43ka3mngvd2bo0ud2smavr3i9i60edb" is a possible Wildcard of the DS Query Name. But the DS-Query in the parent zone sends a valid NSEC3 RR With the owner "e43jlmfjm7b0ob359cku1oek7gqqrdgd" and the Next Owner "e43kejdv5nitcur0e43htlagrlhjpv44", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: True Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner e43jlmfjm7b0ob359cku1oek7gqqrdgd.be., Algorithm: 8, 2 Labels, original TTL: 600 sec, Signature-expiration: 01.10.2024, 05:53:40 +, Signature-Inception: 08.09.2024, 16:47:15 +, KeyTag 23343, Signer-Name: be

3. Name Servers

Domain	Nameserver
www.surfgate.be	• a.nsset.be
surfgate.be	• a.nsset.be
be	• a.nsset.be / antwerpen2.ns.prodng.dc3.be	•
	• b.nsset.be / amsterdam2.ns.prodng.dc3.be	•
	• c.nsset.be / london1.ns.prodng.dc3.be	•
	• d.nsset.be / brussels2.ns.prodng.dc3.be	•
	• y.nsset.be / dns3.sesto1	•
	• 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:	1028152157
Refresh:	3600
Retry:	1800
Expire:	2419200
TTL:	600
num Entries:	6

Domain:	surfgate.be
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:	1

Domain:	www.surfgate.be
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 "surfgate.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: 1350 (complete: 245733)
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.surfgate.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
A
A
A	Info:: 6 different Name Servers found: a.nsset.be, b.nsset.be, c.nsset.be, d.nsset.be, y.nsset.be, z.nsset.be, 6 Name Servers included in Delegation: a.nsset.be, b.nsset.be, c.nsset.be, d.nsset.be, y.nsset.be, z.nsset.be, 6 Name Servers included in 1 Zone definitions: a.nsset.be, b.nsset.be, c.nsset.be, d.nsset.be, y.nsset.be, z.nsset.be, 1 Name Servers listed in SOA.Primary: a.nsset.be.
A	Good: Only one SOA.Primary Name Server found.: a.nsset.be.
A	Good: SOA.Primary Name Server included in the delegation set.: a.nsset.be.
A	Good: All Name Server Domain Names have a Public Suffix.
A
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: a.nsset.be: 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: a.nsset.be: 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: 21534 milliseconds, 21.534 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)

Issuer				last 7 days	active	num Certs
CN=Sectigo ECC Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, C=GB, ST=Greater Manchester				0	0	1

CertSpotter-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
6676893960 leaf cert	CN=Sectigo ECC Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, C=GB, ST=Greater Manchester	2024-02-02 00:00:00	2025-02-01 23:59:59	*.surfgate.be, surfgate.be - 2 entries

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=Sectigo ECC Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, C=GB, ST=Greater Manchester				0	0	1

CRT-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
11945164605 leaf cert	CN=Sectigo ECC Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, C=GB, ST=Greater Manchester	2024-02-01 23:00:00	2025-02-01 22:59:59	*.surfgate.be, surfgate.be 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/

Small Code update, wait one minute

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers:

No NameServer - IP address - Informations found

14. CAA - Entries

Domainname	flag	Name	Value	∑ Queries	∑ Timeout
be	0		no CAA entry found	1	0

15. TXT - Entries

No TXT entries found

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=47e9ad04-793f-4c38-81d7-23a68e6f0208

Last Result: https://check-your-website.server-daten.de/?q=surfgate.be - 2024-09-16 11:52:48

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

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