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

...

skip EDNS-Check

skip Content-Check

check links

Top config

Checked:
08.09.2019 05:42:52

Older results

No older results found

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
git.mamago.org	A	178.79.153.73 London/England/United Kingdom (GB) - Linode Hostname: www.mamago.org	yes	1	0
	AAAA		yes
www.git.mamago.org		Name Error	yes	1	0

2. DNSSEC

Zone (*)	DNSSEC - Informations

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


	• Status: Valid because published


	2 DNSKEY RR found


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


	Public Key with Algorithm 8, KeyTag 59944, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 20.09.2019, 00:00:00 +, Signature-Inception: 30.08.2019, 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: org
org	2 DS RR in the parent zone found


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner org., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 20.09.2019, 17:00:00 +, Signature-Inception: 07.09.2019, 16:00:00 +, KeyTag 59944, Signer-Name: (root)


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


	4 DNSKEY RR found


	Public Key with Algorithm 7, KeyTag 9795, Flags 257 (SEP = Secure Entry Point)


	Public Key with Algorithm 7, KeyTag 17883, Flags 257 (SEP = Secure Entry Point)


	Public Key with Algorithm 7, KeyTag 44078, Flags 256


	Public Key with Algorithm 7, KeyTag 47612, Flags 256


	3 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner org., Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 22.09.2019, 15:29:24 +, Signature-Inception: 01.09.2019, 14:29:24 +, KeyTag 9795, Signer-Name: org


	RRSIG-Owner org., Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 22.09.2019, 15:29:24 +, Signature-Inception: 01.09.2019, 14:29:24 +, KeyTag 17883, Signer-Name: org


	RRSIG-Owner org., Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 22.09.2019, 15:29:24 +, Signature-Inception: 01.09.2019, 14:29:24 +, KeyTag 47612, Signer-Name: org


	• Status: Good - Algorithmus 7 and DNSKEY with KeyTag 9795 used to validate the DNSKEY RRSet


	• Status: Good - Algorithmus 7 and DNSKEY with KeyTag 17883 used to validate the DNSKEY RRSet


	• Status: Good - Algorithmus 7 and DNSKEY with KeyTag 47612 used to validate the DNSKEY RRSet


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


	• Status: Valid Chain of trust. Parent-DS with Algorithm 7, KeyTag 9795, DigestType 2 and Digest "OSKzG286TqkrGet7UhIPAx/Y4F/wsDuvz5+JG/5/+OU=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: mamago.org
mamago.org	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 "ksk45tqb06g1mg5at2nuhgqfs7ih6aag" between the hashed NSEC3-owner "ksjuvkg50thoksksdvrpiei7i1a2lb6f" and the hashed NextOwner "kskc9bt85bq9gm9tmfhq7hkig7jq5e6t". So the parent zone confirmes the not-existence of a DS RR. Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner ksjuvkg50thoksksdvrpiei7i1a2lb6f.org., Algorithm: 7, 2 Labels, original TTL: 86400 sec, Signature-expiration: 22.09.2019, 15:29:24 +, Signature-Inception: 01.09.2019, 14:29:24 +, KeyTag 47612, Signer-Name: org


	0 DNSKEY RR found




Zone: git.mamago.org
git.mamago.org	0 DS RR in the parent zone found


	0 DNSKEY RR found




Zone: www.git.mamago.org
www.git.mamago.org	0 DS RR in the parent zone found

3. Name Servers

Domain	Nameserver	NS-IP
www.git.mamago.org	• ns1.linode.com
git.mamago.org	• ns1.linode.com / 67m29	162.159.27.72 Ashburn/Virginia/United States (US) - Cloudflare, Inc.	•
	•	2400:cb00:2049:1::a29f:1a63 Columbus/North Carolina/United States (US) - CLOUDFLARE	•
mamago.org	• ns1.linode.com / 67m5		•
	• ns2.linode.com / 67m2		•
	• ns3.linode.com / 67m24		•
	• ns4.linode.com / 67m17		•
org	• a0.org.afilias-nst.info / ns000b.app8.mia2.afilias-nst.info		•
	• a2.org.afilias-nst.info / 2.ber.pch		•
	• b0.org.afilias-nst.org / ns000b.app22.ams2.afilias-nst.info		•
	• b2.org.afilias-nst.org / 5.fra.pch		•
	• c0.org.afilias-nst.info / ns000a.app2.ams2.afilias-nst.info		•
	• d0.org.afilias-nst.org / app21.iad1.hosts.meta.redstone.afilias-nst.info-2		•

4. SOA-Entries

Domain:	org
Zone-Name:
Primary:	a0.org.afilias-nst.info
Mail:	noc.afilias-nst.info
Serial:	2013618797
Refresh:	1800
Retry:	900
Expire:	604800
TTL:	86400
num Entries:	6

Domain:	mamago.org
Zone-Name:
Primary:	ns1.linode.com
Mail:	webmaster.mamago.org
Serial:	2019090794
Refresh:	14400
Retry:	14400
Expire:	1209600
TTL:	86400
num Entries:	4

Domain:	git.mamago.org
Zone-Name:
Primary:	ns1.linode.com
Mail:	webmaster.mamago.org
Serial:	2019090794
Refresh:	14400
Retry:	14400
Expire:	1209600
TTL:	86400
num Entries:	2

Domain:	www.git.mamago.org
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:	1

5. Screenshots

No Screenshot listed, because no screenshot found. Perhaps the check is too old, the feature startet 2019-12-23.

6. Url-Checks

show header:

Domainname	Http-Status	redirect	Sec.	G
• http://git.mamago.org/ 178.79.153.73	301	https://git.mamago.org/	0.067	A
Server: nginx/1.10.3 (Ubuntu)
Date: Sun, 08 Sep 2019 03:43:29 GMT
Content-Type: text/html
Content-Length: 194
Connection: close
Location: https://git.mamago.org/

• https://git.mamago.org/ 178.79.153.73	200		3.297	A
Server: nginx/1.10.3 (Ubuntu)
Date: Sun, 08 Sep 2019 03:43:29 GMT
Content-Type: text/html; charset=UTF-8
Transfer-Encoding: chunked
Connection: close
Last-Modified: Sun, 08 Sep 2019 03:43:29 GMT
Expires: Sun, 08 Sep 2019 03:48:29 GMT
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload

• http://git.mamago.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 178.79.153.73	404		0.070	A
Not Found
Visible Content:
Server: nginx/1.10.3 (Ubuntu)
Date: Sun, 08 Sep 2019 03:43:32 GMT
Content-Type: text/html
Content-Length: 178
Connection: close

7. Comments

	1. General Results, most used to calculate the result
A	name "git.mamago.org" is subdomain, public suffix is "org", top-level-domain-type is "generic", tld-manager is "Public Interest Registry (PIR)"
A	Good: All ip addresses are public addresses
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
A	Good: destination is https
A	Good - only one version with Http-Status 200
A	Good: one preferred version: non-www is preferred
A	Good: every https has a Strict Transport Security Header
A	Good: HSTS max-age is long enough, 31536000 seconds = 365 days
A	Good: HSTS has includeSubdomains - directive
A	Good: HSTS has preload directive
	Warning: HSTS preload sent, but not in Preload-List. Never send a preload directive if you don't know what preload means. Check https://hstspreload.org/ to learn the basics about the Google-Preload list. If you send a preload directive, you should immediately add your domain to the HSTS preload list via https://hstspreload.org/ . If Google accepts the domain, so the status is "pending": Note that new entries are hardcoded into the Chrome source code and can take several months before they reach the stable version. So you will see this message some months. If you don't want that or if you don't understand "preload", but if you send a preload directive and if you have correct A-redirects, everybody can add your domain to that list. Then you may have problems, it's not easy to undo that. So if you don't want your domain preloaded, remove the preload directive.
	HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
A	Good: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):1 complete Content-Type - header (2 urls)
	http://git.mamago.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 178.79.153.73			Url with incomplete Content-Type - header - missing charset
A	http://git.mamago.org/ 178.79.153.73	301	https://git.mamago.org/	Correct redirect http - https with the same domain name
	2. Header-Checks (Cross-Origin-* headers are alpha - started 2024-06-05)
	3. DNS- and NameServer - Checks
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: ns1.linode.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
A	Good: All checks /.well-known/acme-challenge/random-filename without redirects answer with the expected http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 challenge should work. If it doesn't work: Check your vHost configuration (apachectl -S, httpd -S, nginx -T). Every combination of port and ServerName / ServerAlias (Apache) or Server (Nginx) must be unique. Merge duplicated entries in one vHost. If you use an IIS, extensionless files must be allowed in the /.well-known/acme-challenge subdirectory. Create a web.config in that directory. Content: <configuration><system.webServer><staticContent><mimeMap fileExtension="." mimeType="text/plain" /></staticContent></system.webServer></configuration>. If you have a redirect http ⇒ https, that's ok, Letsencrypt follows such redirects to port 80 / 443 (same or other server). There must be a certificate. But the certificate may be expired, self signed or with a not matching domain name. Checking the validation file Letsencrypt ignores such certificate errors. 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: 46920 milliseconds, 46.920 seconds

8. Connections

Domain

Port

Cert.

Protocol

KeyExchange

Strength

Cipher

Strength

HashAlgorithm

OCSP stapling

Domain/KeyExchange

IP/Strength

Port/Cipher

Cert./Strength

Protocol/HashAlgorithm

OCSP stapling

git.mamago.org

178.79.153.73

443

Tls12

ECDH Ephermal

256

Aes256

256

Sha384

error checking OCSP stapling

git.mamago.org

178.79.153.73

443

Tls12

ECDH Ephermal

256

Aes256

256

Sha384

error checking OCSP stapling

no Tls.1.2
no Tls.1.1
no Tls.1.0

Chain - incomplete	1	CN=git.mamago.org
	2	CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US

9. Certificates

CN=git.mamago.org

08.09.2019

07.12.2019
1823 days expired

git.mamago.org - 1 entry

CN=git.mamago.org

08.09.2019

07.12.2019
1823 days expired

git.mamago.org - 1 entry

Keyalgorithm	RSA encryption (2048 bit)
Signatur:	SHA256 With RSA-Encryption
Serial Number:	032B4816255EE46673E5605D5B9CFC1990B5
Thumbprint:	CBEA98E0F42565C9B14AB29C92740A64B3F24DAC
SHA256 / Certificate:	uZJdKdfBTuNItISh6lGGr1IXrSNb3KXIWSQ1/1PqZvQ=
SHA256 hex / Cert (DANE * 0 1):	e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):	9248c4a4bbe69cd396e847041203e26a9668349e7c7d482ab19dfff03fdc8a18
SHA256 hex / Subject Public Key Information (SPKI):	9248c4a4bbe69cd396e847041203e26a9668349e7c7d482ab19dfff03fdc8a18
SPKI checked via https://v1.pwnedkeys.com/spki-hash:	Good: Key isn't compromised
OCSP - Url:	http://ocsp.int-x3.letsencrypt.org
OCSP - must staple:	no
Certificate Transparency:	yes
Enhanced Key Usage:	Server Authentication (1.3.6.1.5.5.7.3.1), Client Authentication (1.3.6.1.5.5.7.3.2)

CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US

17.03.2016

17.03.2021
1357 days expired

CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US

17.03.2016

17.03.2021
1357 days expired

Keyalgorithm	RSA encryption (2048 bit)
Signatur:	SHA256 With RSA-Encryption
Serial Number:	0A0141420000015385736A0B85ECA708
Thumbprint:	E6A3B45B062D509B3382282D196EFE97D5956CCB
SHA256 / Certificate:	JYR9Zo608E/dQLErawdAxWfafQJDCOtsLJb+QdneIY0=
SHA256 hex / Cert (DANE * 0 1):	25847d668eb4f04fdd40b12b6b0740c567da7d024308eb6c2c96fe41d9de218d
SHA256 hex / PublicKey (DANE * 1 1):	60b87575447dcba2a36b7d11ac09fb24a9db406fee12d2cc90180517616e8a18
SHA256 hex / Subject Public Key Information (SPKI):	60b87575447dcba2a36b7d11ac09fb24a9db406fee12d2cc90180517616e8a18
SPKI checked via https://v1.pwnedkeys.com/spki-hash:	Good: Key isn't compromised
OCSP - Url:	http://isrg.trustid.ocsp.identrust.com
OCSP - must staple:	no
Certificate Transparency:	no
Enhanced Key Usage:

CN=DST Root CA X3, O=Digital Signature Trust Co.

30.09.2000

30.09.2021
1160 days expired

CN=DST Root CA X3, O=Digital Signature Trust Co.

30.09.2000

30.09.2021
1160 days expired

Keyalgorithm	RSA encryption (2048 bit)
Signatur:	SHA-1 with RSA Encryption
Serial Number:	44AFB080D6A327BA893039862EF8406B
Thumbprint:	DAC9024F54D8F6DF94935FB1732638CA6AD77C13
SHA256 / Certificate:	BocmAzGnJAPZCfEF5pvPDTLhvSST/8bZIG0RvNZ3Bzk=
SHA256 hex / Cert (DANE * 0 1):	0687260331a72403d909f105e69bcf0d32e1bd2493ffc6d9206d11bcd6770739
SHA256 hex / PublicKey (DANE * 1 1):	563b3caf8cfef34c2335caf560a7a95906e8488462eb75ac59784830df9e5b2b
SHA256 hex / Subject Public Key Information (SPKI):	563b3caf8cfef34c2335caf560a7a95906e8488462eb75ac59784830df9e5b2b
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

Summary

No data found or small Code-update

Details

Small Code Update - wait one minute

12. Html-Parsing via https://validator.nu/ / https://validator.w3.org/nu/ (started 2024-09-28, 09:00, alpha)

Unfortunately, there are differences between the first used validator.nu and validator.w3.org/nu/ - switched to validator.w3.org/nu/. Looks like some error messages (link - fetchpriority attribute) of validator.nu are obsolete, not seen in the w3.org-version and not found in the current specification: link may have a fetchpriority attribute.

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. The feature is new (2020-05-07), so recheck this domain.

14. CAA - Entries

Domainname	Value	∑ Queries
git.mamago.org	no CAA entry found	1
mamago.org	no CAA entry found	1
org	no CAA entry found	1

15. TXT - Entries

Domainname	Status	∑ Queries
mamago.org	ok	1
git.mamago.org	ok	1
_acme-challenge.git.mamago.org	Name Error - The domain name does not exist	1
_acme-challenge.git.mamago.org.mamago.org	Name Error - The domain name does not exist	1
_acme-challenge.git.mamago.org.git.mamago.org	Name Error - The domain name does not exist	1

16. DomainService - Entries

No DomainServiceEntries entries found

17. Cipher Suites

No Ciphers found

18. Portchecks

Domain	IP	Port	Description
git.mamago.org	178.79.153.73	21	FTP

git.mamago.org	178.79.153.73	21	FTP
git.mamago.org	178.79.153.73	22	SSH

git.mamago.org	178.79.153.73	22	SSH
git.mamago.org	178.79.153.73	25	SMTP

git.mamago.org	178.79.153.73	25	SMTP
git.mamago.org	178.79.153.73	53	DNS

git.mamago.org	178.79.153.73	53	DNS
git.mamago.org	178.79.153.73	110	POP3

git.mamago.org	178.79.153.73	110	POP3
git.mamago.org	178.79.153.73	143	IMAP

git.mamago.org	178.79.153.73	143	IMAP
git.mamago.org	178.79.153.73	465	SMTP (encrypted)

git.mamago.org	178.79.153.73	465	SMTP (encrypted)
git.mamago.org	178.79.153.73	587	SMTP (encrypted, submission)

git.mamago.org	178.79.153.73	587	SMTP (encrypted, submission)
git.mamago.org	178.79.153.73	993	IMAP (encrypted)

git.mamago.org	178.79.153.73	993	IMAP (encrypted)
git.mamago.org	178.79.153.73	995	POP3 (encrypted)

git.mamago.org	178.79.153.73	995	POP3 (encrypted)
git.mamago.org	178.79.153.73	1433	MS SQL

git.mamago.org	178.79.153.73	1433	MS SQL
git.mamago.org	178.79.153.73	2082	cPanel (http)

git.mamago.org	178.79.153.73	2082	cPanel (http)
git.mamago.org	178.79.153.73	2083	cPanel (https)

git.mamago.org	178.79.153.73	2083	cPanel (https)
git.mamago.org	178.79.153.73	2086	WHM (http)

git.mamago.org	178.79.153.73	2086	WHM (http)
git.mamago.org	178.79.153.73	2087	WHM (https)

git.mamago.org	178.79.153.73	2087	WHM (https)
git.mamago.org	178.79.153.73	2089	cPanel Licensing

git.mamago.org	178.79.153.73	2089	cPanel Licensing
git.mamago.org	178.79.153.73	2095	cPanel Webmail (http)

git.mamago.org	178.79.153.73	2095	cPanel Webmail (http)
git.mamago.org	178.79.153.73	2096	cPanel Webmail (https)

git.mamago.org	178.79.153.73	2096	cPanel Webmail (https)
git.mamago.org	178.79.153.73	2222	DirectAdmin (http)

git.mamago.org	178.79.153.73	2222	DirectAdmin (http)
git.mamago.org	178.79.153.73	2222	DirectAdmin (https)

git.mamago.org	178.79.153.73	2222	DirectAdmin (https)
git.mamago.org	178.79.153.73	3306	mySql

git.mamago.org	178.79.153.73	3306	mySql
git.mamago.org	178.79.153.73	5224	Plesk Licensing

git.mamago.org	178.79.153.73	5224	Plesk Licensing
git.mamago.org	178.79.153.73	5432	PostgreSQL

git.mamago.org	178.79.153.73	5432	PostgreSQL
git.mamago.org	178.79.153.73	8080	Ookla Speedtest (http)

git.mamago.org	178.79.153.73	8080	Ookla Speedtest (http)
git.mamago.org	178.79.153.73	8080	Ookla Speedtest (https)

git.mamago.org	178.79.153.73	8080	Ookla Speedtest (https)
git.mamago.org	178.79.153.73	8083	VestaCP http

git.mamago.org	178.79.153.73	8083	VestaCP http
git.mamago.org	178.79.153.73	8083	VestaCP https

git.mamago.org	178.79.153.73	8083	VestaCP https
git.mamago.org	178.79.153.73	8443	Plesk Administration (https)

git.mamago.org	178.79.153.73	8443	Plesk Administration (https)
git.mamago.org	178.79.153.73	8447	Plesk Installer + Updates

git.mamago.org	178.79.153.73	8447	Plesk Installer + Updates
git.mamago.org	178.79.153.73	8880	Plesk Administration (http)

git.mamago.org	178.79.153.73	8880	Plesk Administration (http)
git.mamago.org	178.79.153.73	10000	Webmin (http)

git.mamago.org	178.79.153.73	10000	Webmin (http)
git.mamago.org	178.79.153.73	10000	Webmin (https)

git.mamago.org	178.79.153.73	10000	Webmin (https)

Permalink: https://check-your-website.server-daten.de/?i=21fb7e40-8e7b-470b-8117-763f46b2caf4

Last Result: https://check-your-website.server-daten.de/?q=git.mamago.org - 2019-09-08 05:42:52

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

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