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

0 in Queue, 0 of max. 8 Checks (17:01:04)
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 |

 

V

 

Connect failure - perhaps firewall

 

Checked:
10.06.2025 00:30:55

 

Older results

No older results found

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
mail.pixisys.eu
A
109.122.216.94
Budapest/Hungary (HU) - Rackforest Zrt.
No Hostname found
yes
1
0

AAAA

yes


www.mail.pixisys.eu

Name Error
yes
1
0
*.pixisys.eu
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes


*.mail.pixisys.eu
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 53148, Flags 256






1 RRSIG RR to validate DNSKEY RR found






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

eu
1 DS RR in the parent zone found






DS with Algorithm 8, KeyTag 35926, DigestType 2 and Digest ibnvBEWQTnxgdLW+zoI8PiZPvZHBA9EL3mA0EjQ85ww=






1 RRSIG RR to validate DS RR found






RRSIG-Owner eu., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 22.06.2025, 17:00:00 +, Signature-Inception: 09.06.2025, 16:00:00 +, KeyTag 53148, Signer-Name: (root)






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






2 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 15156, Flags 256






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






2 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner eu., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 15.06.2025, 19:30:33 +, Signature-Inception: 08.06.2025, 19:28:18 +, KeyTag 15156, Signer-Name: eu






RRSIG-Owner eu., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 15.06.2025, 19:30:33 +, Signature-Inception: 08.06.2025, 19:28:18 +, KeyTag 35926, Signer-Name: eu






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






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






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



Zone: pixisys.eu

pixisys.eu
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 "kjmirm6ton95eqcusadmn5ntt0vvmbjd" between the hashed NSEC3-owner "kjmhntss6tqc4fmg22q1nj5or10vd4a4" and the hashed NextOwner "kjmjtq2tg96du5ska6kii9l7vjdrqems". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner kjmhntss6tqc4fmg22q1nj5or10vd4a4.eu., Algorithm: 8, 2 Labels, original TTL: 600 sec, Signature-expiration: 16.06.2025, 12:02:04 +, Signature-Inception: 09.06.2025, 11:55:49 +, KeyTag 15156, Signer-Name: eu






DS-Query in the parent zone sends valid NSEC3 RR with the Hash "cs7nl1v9tgtkj2d4ipjvdfm81ohcdd0c" as Owner. That's the Hash of "eu" with the NextHashedOwnerName "cs7o73fd8i0tp1g4pjbdui5oa3bjs55j". So that domain name is the Closest Encloser of "pixisys.eu". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner cs7nl1v9tgtkj2d4ipjvdfm81ohcdd0c.eu., Algorithm: 8, 2 Labels, original TTL: 600 sec, Signature-expiration: 12.06.2025, 15:15:04 +, Signature-Inception: 05.06.2025, 14:53:40 +, KeyTag 15156, Signer-Name: eu






1 DNSKEY RR found






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






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner pixisys.eu., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 19.06.2025, 00:00:00 +, Signature-Inception: 29.05.2025, 00:00:00 +, KeyTag 7263, Signer-Name: pixisys.eu






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






Error: DNSKEY 7263 signs DNSKEY RRset, but no confirming DS RR in the parent zone found. No chain of trust created.



Zone: mail.pixisys.eu

mail.pixisys.eu
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 "gptj21qnm48sqcb4ujg1i0pfd61qtrh1" between the hashed NSEC3-owner "gptj21qnm48sqcb4ujg1i0pfd61qtrh1" and the hashed NextOwner "i5gp83gogq6el2nd5sjgjbhkivvt4v93". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: A, TXT, RRSIG Validated: RRSIG-Owner gptj21qnm48sqcb4ujg1i0pfd61qtrh1.pixisys.eu., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 19.06.2025, 00:00:00 +, Signature-Inception: 29.05.2025, 00:00:00 +, KeyTag 7263, Signer-Name: pixisys.eu






0 DNSKEY RR found












RRSIG Type 1 validates the A - Result: 109.122.216.94
Validated: RRSIG-Owner mail.pixisys.eu., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 19.06.2025, 00:00:00 +, Signature-Inception: 29.05.2025, 00:00:00 +, KeyTag 7263, Signer-Name: pixisys.eu






RRSIG Type 16 validates the TXT - Result: v=spf1 a ra=postmaster -all
Validated: RRSIG-Owner mail.pixisys.eu., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 19.06.2025, 00:00:00 +, Signature-Inception: 29.05.2025, 00:00:00 +, KeyTag 7263, Signer-Name: pixisys.eu






CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "gptj21qnm48sqcb4ujg1i0pfd61qtrh1" equal the hashed NSEC3-owner "gptj21qnm48sqcb4ujg1i0pfd61qtrh1" and the hashed NextOwner "i5gp83gogq6el2nd5sjgjbhkivvt4v93". 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, TXT, RRSIG Validated: RRSIG-Owner gptj21qnm48sqcb4ujg1i0pfd61qtrh1.pixisys.eu., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 19.06.2025, 00:00:00 +, Signature-Inception: 29.05.2025, 00:00:00 +, KeyTag 7263, Signer-Name: pixisys.eu






Status: Good. NoData-Proof required and found.






AAAA-Query sends a valid NSEC3 RR as result with the hashed query name "gptj21qnm48sqcb4ujg1i0pfd61qtrh1" equal the hashed NSEC3-owner "gptj21qnm48sqcb4ujg1i0pfd61qtrh1" and the hashed NextOwner "i5gp83gogq6el2nd5sjgjbhkivvt4v93". 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, TXT, RRSIG Validated: RRSIG-Owner gptj21qnm48sqcb4ujg1i0pfd61qtrh1.pixisys.eu., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 19.06.2025, 00:00:00 +, Signature-Inception: 29.05.2025, 00:00:00 +, KeyTag 7263, Signer-Name: pixisys.eu






Status: Good. NoData-Proof required and found.






TLSA-Query (_443._tcp.mail.pixisys.eu) sends a valid NSEC3 RR as result with the hashed owner name "gptj21qnm48sqcb4ujg1i0pfd61qtrh1" (unhashed: mail.pixisys.eu). So that's the Closest Encloser of the query name.
Bitmap: A, TXT, RRSIG Validated: RRSIG-Owner gptj21qnm48sqcb4ujg1i0pfd61qtrh1.pixisys.eu., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 19.06.2025, 00:00:00 +, Signature-Inception: 29.05.2025, 00:00:00 +, KeyTag 7263, Signer-Name: pixisys.eu






Status: Good. NXDomain-Proof required and found.






TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "aat4h137rqerghv0ia6oh1ciriep521n" (unhashed: _tcp.mail.pixisys.eu) with the owner "8ouo4arqskpe7dhtmprjnglir6sb7jb9" and the NextOwner "d5g8ls25viuql1iomiif7vut5o6g378t". So that NSEC3 confirms the not-existence of the Next Closer Name.
Bitmap: SRV, RRSIG Validated: RRSIG-Owner 8ouo4arqskpe7dhtmprjnglir6sb7jb9.pixisys.eu., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 19.06.2025, 00:00:00 +, Signature-Inception: 29.05.2025, 00:00:00 +, KeyTag 7263, Signer-Name: pixisys.eu






Status: Good. NXDomain-Proof required and found.






TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Wildcard expansion of the ClosestEncloser "v927uq37ap0v1352q00p7e2n58abaedi" (unhashed: *.mail.pixisys.eu) with the owner "thurop8m84vd8f2u9qa67sg8ceagmtmu" and the NextOwner "04lj91p7qo6rlbea0uuq8acboctvlh52". So that NSEC3 confirms the not-existence of the Wildcard expansion.
Bitmap: SRV, RRSIG Validated: RRSIG-Owner thurop8m84vd8f2u9qa67sg8ceagmtmu.pixisys.eu., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 19.06.2025, 00:00:00 +, Signature-Inception: 29.05.2025, 00:00:00 +, KeyTag 7263, Signer-Name: pixisys.eu






Status: Good. NXDomain-Proof required and found.






CAA-Query sends a valid NSEC3 RR as result with the hashed query name "gptj21qnm48sqcb4ujg1i0pfd61qtrh1" equal the hashed NSEC3-owner "gptj21qnm48sqcb4ujg1i0pfd61qtrh1" and the hashed NextOwner "i5gp83gogq6el2nd5sjgjbhkivvt4v93". 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, TXT, RRSIG Validated: RRSIG-Owner gptj21qnm48sqcb4ujg1i0pfd61qtrh1.pixisys.eu., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 19.06.2025, 00:00:00 +, Signature-Inception: 29.05.2025, 00:00:00 +, KeyTag 7263, Signer-Name: pixisys.eu






Status: Good. NoData-Proof required and found.



Zone: www.mail.pixisys.eu

www.mail.pixisys.eu
0 DS RR in the parent zone found






DS-Query in the parent zone sends valid NSEC3 RR with the Hash "gptj21qnm48sqcb4ujg1i0pfd61qtrh1" as Owner. That's the Hash of "mail.pixisys.eu" with the NextHashedOwnerName "i5gp83gogq6el2nd5sjgjbhkivvt4v93". So that domain name is the Closest Encloser of "www.mail.pixisys.eu". Opt-Out: False.
Bitmap: A, TXT, RRSIG Validated: RRSIG-Owner gptj21qnm48sqcb4ujg1i0pfd61qtrh1.pixisys.eu., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 19.06.2025, 00:00:00 +, Signature-Inception: 29.05.2025, 00:00:00 +, KeyTag 7263, Signer-Name: pixisys.eu






The ClosestEncloser says, that "*.mail.pixisys.eu" with the Hash "v927uq37ap0v1352q00p7e2n58abaedi" 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 "thurop8m84vd8f2u9qa67sg8ceagmtmu" and the Next Owner "04lj91p7qo6rlbea0uuq8acboctvlh52", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: False.
Bitmap: SRV, RRSIG Validated: RRSIG-Owner thurop8m84vd8f2u9qa67sg8ceagmtmu.pixisys.eu., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 19.06.2025, 00:00:00 +, Signature-Inception: 29.05.2025, 00:00:00 +, KeyTag 7263, Signer-Name: pixisys.eu

 

3. Name Servers

DomainNameserverNS-IP
www.mail.pixisys.eu
•  ns1.m.glbns.com

mail.pixisys.eu
•  ns1.m.glbns.com / ns1-be0.m.glbns.com
185.33.52.3
Budapest/Hungary (HU) - Docler Networks		•

• 
2a00:c760:80:d07:2011:ffff:b921:3403
Budapest/Hungary (HU) - Servergarden Kft.		•
pixisys.eu
•  ns1.m.glbns.com / ns1-be0.m.glbns.com
185.33.52.3
Budapest/Hungary (HU) - Docler Networks		•

• 
2a00:c760:80:d07:2011:ffff:b921:3403
Budapest/Hungary (HU) - Servergarden Kft.		•

•  ns2.m.glbns.com / ns2-be0.m.glbns.com
185.224.44.3
Budapest/Hungary (HU) - Microware Hungary KFT		•

• 
2a14:6940:800:d07:2011:ffff:0:3
Budapest/Hungary (HU) - Magyar Telekom plc.		•
eu
•  be.dns.eu
•

•  si.dns.eu
•

•  w.dns.eu / tld-all-ffm1@53028
•

•  x.dns.eu / ns-1.eu.de8.bind
•

•  y.dns.eu / s2.dex
•

 

4. SOA-Entries


Domain:eu
Zone-Name:eu
Primary:si.dns.eu
Mail:tech.eurid.eu
Serial:1113165986
Refresh:3600
Retry:1800
Expire:3600000
TTL:600
num Entries:2


Domain:eu
Zone-Name:eu
Primary:si.dns.eu
Mail:tech.eurid.eu
Serial:1113165988
Refresh:3600
Retry:1800
Expire:3600000
TTL:600
num Entries:3


Domain:pixisys.eu
Zone-Name:pixisys.eu
Primary:ns1.m.glbns.com
Mail:hostmaster.microware.hu
Serial:2025060206
Refresh:86400
Retry:1800
Expire:604800
TTL:3600
num Entries:4


Domain:mail.pixisys.eu
Zone-Name:pixisys.eu
Primary:ns1.m.glbns.com
Mail:hostmaster.microware.hu
Serial:2025060206
Refresh:86400
Retry:1800
Expire:604800
TTL:3600
num Entries:2


Domain:www.mail.pixisys.eu
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


:

:
DomainnameHttp-StatusredirectSec.G
• http://mail.pixisys.eu/
109.122.216.94
301
https://mail.pixisys.eu/
Html is minified: 109.46 %
0.060
A
Server: nginx
Date: Mon, 09 Jun 2025 22:31:50 GMT
Connection: keep-alive
Location: https://mail.pixisys.eu/
Content-Type: text/html
Content-Length: 162

• https://mail.pixisys.eu/
109.122.216.94
-102


1.110
V
ConnectionError (2, 0x80004005). Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. (109.122.216.94:443)

• http://mail.pixisys.eu/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
109.122.216.94
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0		502

Html is minified: 110.29 %
Other inline scripts (∑/total): 0/0		0.034
S
Bad Gateway
Visible Content:
Server: nginx
Date: Mon, 09 Jun 2025 22:31:51 GMT
Connection: keep-alive
Content-Type: text/html
Content-Length: 150

• https://109.122.216.94/
109.122.216.94
-102


1.114
V
ConnectionError (2, 0x80004005). Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. (109.122.216.94:443)

 

7. Comments


1. General Results, most used to calculate the result

Aname "mail.pixisys.eu" is subdomain, public suffix is ".eu", top-level-domain is ".eu", top-level-domain-type is "country-code", Country is European Union, tld-manager is "EURid vzw/asbl", num .eu-domains preloaded: 2724 (complete: 271405)
AGood: All ip addresses are public addresses
Warning: Only one ip address found: mail.pixisys.eu 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: mail.pixisys.eu has no ipv6 address.
AGood: No asked Authoritative Name Server had a timeout
ADNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
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
HFatal error: No https - result with http-status 200, no encryption
Vhttps://mail.pixisys.eu/ 109.122.216.94
-102

Connect failure - perhaps firewall
Vhttps://109.122.216.94/ 109.122.216.94
-102

Connect failure - perhaps firewall
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 mail.pixisys.eu, 1 ip addresses.
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.mail.pixisys.eu

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:: 7 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
AInfo:: 7 Queries complete, 6 with IPv6, 1 with IPv4.
Warning: Only some DNS Queries done via ipv6. IPv6 is the future, so the name servers of your name servers should have ipv6 addresses.
Ok (4 - 8):: An average of 3.5 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 2 different Name Servers found: ns1.m.glbns.com, ns2.m.glbns.com, 2 Name Servers included in Delegation: ns1.m.glbns.com, ns2.m.glbns.com, 2 Name Servers included in 1 Zone definitions: ns1.m.glbns.com, ns2.m.glbns.com, 1 Name Servers listed in SOA.Primary: ns1.m.glbns.com.
AGood: Only one SOA.Primary Name Server found.: ns1.m.glbns.com.
AGood: SOA.Primary Name Server included in the delegation set.: ns1.m.glbns.com.
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: ns1.m.glbns.com, ns2.m.glbns.com
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: 2 different Name Servers found
AGood: 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: glbns.com
Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: HU
AInfo: Ipv4-Subnet-list: 2 Name Servers, 1 different subnets (first Byte): 185., 2 different subnets (first two Bytes): 185.224., 185.33., 2 different subnets (first three Bytes): 185.224.44., 185.33.52.
AGood: Name Server IPv4-addresses from different subnet found:
AInfo: IPv6-Subnet-list: 2 Name Servers with IPv6, 2 different subnets (first block): 2a00:, 2a14:, 2 different subnets (first two blocks): 2a00:c760:, 2a14:6940:, 2 different subnets (first three blocks): 2a00:c760:0080:, 2a14:6940:0800:, 2 different subnets (first four blocks): 2a00:c760:0080:0d07:, 2a14:6940:0800:0d07:
AExcellent: Every Name Server IPv6-address starts with an unique Hex-block
AGood: Nameserver supports TCP connections: 2 good Nameserver
AGood: Nameserver supports Echo Capitalization: 2 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 2 good Nameserver
AGood: 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: be.dns.eu: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: SOA expected, but NOT found, NOERR expected, BADVER found, Version 0 expectend and found. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns1.m.glbns.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.
Nameserver doesn't pass all EDNS-Checks: si.dns.eu: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: SOA expected, but NOT found, NOERR expected, BADVER found, Version 0 expectend and found. CLIENTSUBNET: ok.
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://mail.pixisys.eu/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 109.122.216.94
502

Fatal: Check of /.well-known/acme-challenge/random-filename has a http status 500 - 599, Server Error. 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: 76716 milliseconds, 76.716 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: ns1.m.glbns.com, ns2.m.glbns.com

 

QNr.DomainTypeNS used
1
com
NS
d.root-servers.net (199.7.91.13)

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
ns1.m.glbns.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns1.dotroll.com, ns2.dotroll.com

Answer: ns1.dotroll.com
185.33.52.1, 2a00:c760:80:d07:2011:ffff:b921:3401

Answer: ns2.dotroll.com
185.224.44.1, 2a14:6940:800:d07:2011:ffff:0:1
3
ns2.m.glbns.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns1.dotroll.com, ns2.dotroll.com

Answer: ns1.dotroll.com
185.33.52.1, 2a00:c760:80:d07:2011:ffff:b921:3401

Answer: ns2.dotroll.com
185.224.44.1, 2a14:6940:800:d07:2011:ffff:0:1
4
ns1.m.glbns.com: 185.33.52.3
A
ns1.dotroll.com (2a00:c760:80:d07:2011:ffff:b921:3401)
5
ns1.m.glbns.com: 2a00:c760:80:d07:2011:ffff:b921:3403
AAAA
ns1.dotroll.com (2a00:c760:80:d07:2011:ffff:b921:3401)
6
ns2.m.glbns.com: 185.224.44.3
A
ns1.dotroll.com (2a00:c760:80:d07:2011:ffff:b921:3401)
7
ns2.m.glbns.com: 2a14:6940:800:d07:2011:ffff:0:3
AAAA
ns1.dotroll.com (2a00:c760:80:d07:2011:ffff:b921:3401)

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
mail.pixisys.eu
0

no CAA entry found
1
0
pixisys.eu
0

no CAA entry found
1
0
eu
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
pixisys.eu
v=spf1 mx ra=postmaster -all
ok
1
0
mail.pixisys.eu
v=spf1 a ra=postmaster -all
ok
1
0
_acme-challenge.mail.pixisys.eu

Name Error - The domain name does not exist
1
0
_acme-challenge.mail.pixisys.eu.pixisys.eu

Name Error - The domain name does not exist
1
0
_acme-challenge.mail.pixisys.eu.mail.pixisys.eu

Name Error - The domain name does not exist
1
0

 

16. DomainService - Entries

TypeDomainPrefValueDNS-errornum AnswersStatusDescription
SPF
TXT
mail.pixisys.eu

v=spf1 a ra=postmaster -all
ok

A
mail.pixisys.eu

109.122.216.94
ok

 

 

17. Cipher Suites

No results

 

18. Portchecks

DomainIPPortDescriptionResultAnswer
mail.pixisys.eu
109.122.216.94
21
FTP



mail.pixisys.eu
109.122.216.94
21
FTP



mail.pixisys.eu
109.122.216.94
22
SSH
open
SSH-2.0-OpenSSH_9.2p1 Debian-2+deb12u6

mail.pixisys.eu
109.122.216.94
22
SSH
open
SSH-2.0-OpenSSH_9.2p1 Debian-2+deb12u6
Bad: SSH without DNS SSHFP Record found
mail.pixisys.eu
109.122.216.94
25
SMTP
open
220 mail.pixisys.eu ESMTP ready

 

Answer EHLO: 250-mail.pixisys.eu 250-PIPELINING 250-SIZE 50000000 250-ETRN 250-ENHANCEDSTATUSCODES 250-8BITMIME 250 DSN

 

Answer AUTH LOGIN: (no AUTH option found)

mail.pixisys.eu
109.122.216.94
25
SMTP
open
220 mail.pixisys.eu ESMTP ready


Answer EHLO: 250-mail.pixisys.eu 250-PIPELINING 250-SIZE 50000000 250-ETRN 250-ENHANCEDSTATUSCODES 250-8BITMIME 250 DSN Fatal: No STARTTLS found. Encryption not possible

mail.pixisys.eu
109.122.216.94
53
DNS



mail.pixisys.eu
109.122.216.94
53
DNS



mail.pixisys.eu
109.122.216.94
110
POP3



mail.pixisys.eu
109.122.216.94
110
POP3



mail.pixisys.eu
109.122.216.94
143
IMAP



mail.pixisys.eu
109.122.216.94
143
IMAP



mail.pixisys.eu
109.122.216.94
465
SMTP (encrypted)



mail.pixisys.eu
109.122.216.94
465
SMTP (encrypted)



mail.pixisys.eu
109.122.216.94
587
SMTP (encrypted, submission)



mail.pixisys.eu
109.122.216.94
587
SMTP (encrypted, submission)



mail.pixisys.eu
109.122.216.94
993
IMAP (encrypted)



mail.pixisys.eu
109.122.216.94
993
IMAP (encrypted)



mail.pixisys.eu
109.122.216.94
995
POP3 (encrypted)



mail.pixisys.eu
109.122.216.94
995
POP3 (encrypted)



mail.pixisys.eu
109.122.216.94
1433
MS SQL



mail.pixisys.eu
109.122.216.94
1433
MS SQL



mail.pixisys.eu
109.122.216.94
2082
cPanel (http)



mail.pixisys.eu
109.122.216.94
2082
cPanel (http)



mail.pixisys.eu
109.122.216.94
2083
cPanel (https)



mail.pixisys.eu
109.122.216.94
2083
cPanel (https)



mail.pixisys.eu
109.122.216.94
2086
WHM (http)



mail.pixisys.eu
109.122.216.94
2086
WHM (http)



mail.pixisys.eu
109.122.216.94
2087
WHM (https)



mail.pixisys.eu
109.122.216.94
2087
WHM (https)



mail.pixisys.eu
109.122.216.94
2089
cPanel Licensing



mail.pixisys.eu
109.122.216.94
2089
cPanel Licensing



mail.pixisys.eu
109.122.216.94
2095
cPanel Webmail (http)



mail.pixisys.eu
109.122.216.94
2095
cPanel Webmail (http)



mail.pixisys.eu
109.122.216.94
2096
cPanel Webmail (https)



mail.pixisys.eu
109.122.216.94
2096
cPanel Webmail (https)



mail.pixisys.eu
109.122.216.94
2222
DirectAdmin (http)



mail.pixisys.eu
109.122.216.94
2222
DirectAdmin (http)



mail.pixisys.eu
109.122.216.94
2222
DirectAdmin (https)



mail.pixisys.eu
109.122.216.94
2222
DirectAdmin (https)



mail.pixisys.eu
109.122.216.94
3306
mySql



mail.pixisys.eu
109.122.216.94
3306
mySql



mail.pixisys.eu
109.122.216.94
5224
Plesk Licensing



mail.pixisys.eu
109.122.216.94
5224
Plesk Licensing



mail.pixisys.eu
109.122.216.94
5432
PostgreSQL



mail.pixisys.eu
109.122.216.94
5432
PostgreSQL



mail.pixisys.eu
109.122.216.94
8080
Ookla Speedtest (http)



mail.pixisys.eu
109.122.216.94
8080
Ookla Speedtest (http)



mail.pixisys.eu
109.122.216.94
8080
Ookla Speedtest (https)



mail.pixisys.eu
109.122.216.94
8080
Ookla Speedtest (https)



mail.pixisys.eu
109.122.216.94
8083
VestaCP http



mail.pixisys.eu
109.122.216.94
8083
VestaCP http



mail.pixisys.eu
109.122.216.94
8083
VestaCP https



mail.pixisys.eu
109.122.216.94
8083
VestaCP https



mail.pixisys.eu
109.122.216.94
8443
Plesk Administration (https)



mail.pixisys.eu
109.122.216.94
8443
Plesk Administration (https)



mail.pixisys.eu
109.122.216.94
8447
Plesk Installer + Updates



mail.pixisys.eu
109.122.216.94
8447
Plesk Installer + Updates



mail.pixisys.eu
109.122.216.94
8880
Plesk Administration (http)



mail.pixisys.eu
109.122.216.94
8880
Plesk Administration (http)



mail.pixisys.eu
109.122.216.94
10000
Webmin (http)



mail.pixisys.eu
109.122.216.94
10000
Webmin (http)



mail.pixisys.eu
109.122.216.94
10000
Webmin (https)



mail.pixisys.eu
109.122.216.94
10000
Webmin (https)



 

 

Permalink: https://check-your-website.server-daten.de/?i=afc6ec28-1d54-40dc-966f-9f50d6bb750c

 

Last Result: https://check-your-website.server-daten.de/?q=mail.pixisys.eu - 2025-06-10 00:30:55

 

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

 

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

 

 

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