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


 

 

A

 

Top config

 

Checked:
16.06.2019 23:51:36

 

Older results

No older results found

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
mail.noblemail.org
A
149.28.199.145
San Jose/California/US
Hostname: mail.noblemail.org
yes
1
0

AAAA

yes


www.mail.noblemail.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 25266, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 01.07.2019, 00:00:00 +, Signature-Inception: 10.06.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: 29.06.2019, 17:00:00 +, Signature-Inception: 16.06.2019, 16:00:00 +, KeyTag 25266, Signer-Name: (root)






Status: Good - Algorithmus 8 and DNSKEY with KeyTag 25266 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 33932, Flags 256






Public Key with Algorithm 7, KeyTag 50465, Flags 256






3 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner org., Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 30.06.2019, 15:30:14 +, Signature-Inception: 09.06.2019, 14:30:14 +, KeyTag 9795, Signer-Name: org






RRSIG-Owner org., Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 30.06.2019, 15:30:14 +, Signature-Inception: 09.06.2019, 14:30:14 +, KeyTag 17883, Signer-Name: org






RRSIG-Owner org., Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 30.06.2019, 15:30:14 +, Signature-Inception: 09.06.2019, 14:30:14 +, KeyTag 50465, 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 50465 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: noblemail.org

noblemail.org
1 DS RR in the parent zone found






1 RRSIG RR to validate DS RR found






RRSIG-Owner noblemail.org., Algorithm: 7, 2 Labels, original TTL: 86400 sec, Signature-expiration: 30.06.2019, 15:30:14 +, Signature-Inception: 09.06.2019, 14:30:14 +, KeyTag 50465, Signer-Name: org






Status: Good - Algorithmus 7 and DNSKEY with KeyTag 50465 used to validate the DS RRSet in the parent zone






2 DNSKEY RR found






Public Key with Algorithm 7, KeyTag 1628, Flags 256






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






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner noblemail.org., Algorithm: 7, 2 Labels, original TTL: 1800 sec, Signature-expiration: 16.07.2019, 00:00:00 +, Signature-Inception: 16.06.2019, 01:00:49 +, KeyTag 10461, Signer-Name: noblemail.org






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






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



Zone: mail.noblemail.org

mail.noblemail.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 "gbldrfg2hb0pnrculnn424ifr284epkd" between the hashed NSEC3-owner "gbldrfg2hb0pnrculnn424ifr284epkd" and the hashed NextOwner "glrm4v3k2pdsdq7qhavj7cqtnrdofuli". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: A, MX, TXT, SSHFP, RRSIG Validated: RRSIG-Owner gbldrfg2hb0pnrculnn424ifr284epkd.noblemail.org., Algorithm: 7, 3 Labels, original TTL: 1800 sec, Signature-expiration: 16.07.2019, 00:00:00 +, Signature-Inception: 16.06.2019, 01:00:49 +, KeyTag 1628, Signer-Name: noblemail.org






0 DNSKEY RR found












RRSIG Type 1 validates the A - Result: 149.28.199.145
Validated: RRSIG-Owner mail.noblemail.org., Algorithm: 7, 3 Labels, original TTL: 1800 sec, Signature-expiration: 16.07.2019, 00:00:00 +, Signature-Inception: 16.06.2019, 01:00:49 +, KeyTag 1628, Signer-Name: noblemail.org






RRSIG Type 16 validates the TXT - Result: v=spf1 mx -all
Validated: RRSIG-Owner mail.noblemail.org., Algorithm: 7, 3 Labels, original TTL: 1800 sec, Signature-expiration: 16.07.2019, 00:00:00 +, Signature-Inception: 16.06.2019, 01:00:49 +, KeyTag 1628, Signer-Name: noblemail.org






RRSIG Type 52 validates the TLSA - Result (_443._tcp.mail.noblemail.org): _443._tcp.mail.noblemail.org: CertUsage 3 (DANE-EE, Domain-issued certificate), Selector: 1 (SPKI, SubjectPublicKeyInfo), Matching: 1 (SHA2-256, 256 bit hash by SHA2), CertificateAssociationData: 4ee67315c685e3b6bca8e27d96ebd1a2b052cf6f0366de2eacaae75969d62cb5
Validated: RRSIG-Owner _443._tcp.mail.noblemail.org., Algorithm: 7, 5 Labels, original TTL: 1800 sec, Signature-expiration: 16.07.2019, 00:00:00 +, Signature-Inception: 16.06.2019, 01:00:49 +, KeyTag 1628, Signer-Name: noblemail.org






RRSIG Type 50, expiration 2019-07-16 00:00:00 + validates the NSEC3 RR that proves the not-existence of the CNAME RR.
Bitmap: A, MX, TXT, SSHFP, RRSIG






RRSIG Type 50, expiration 2019-07-16 00:00:00 + validates the NSEC3 RR that proves the not-existence of the AAAA RR.
Bitmap: A, MX, TXT, SSHFP, RRSIG






RRSIG Type 50, expiration 2019-07-16 00:00:00 + validates the NSEC3 RR that proves the not-existence of the CAA RR.
Bitmap: A, MX, TXT, SSHFP, RRSIG



Zone: www.mail.noblemail.org

www.mail.noblemail.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 "9ks3ecssnoq8093905ipca1fc6m8dfa9" between the hashed NSEC3-owner "8ri8c4heujv7jqugue9tfjntofabntdd" and the hashed NextOwner "9n317fetlflfdmeihka1cd9m8m7mai6s". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: TXT, RRSIG Validated: RRSIG-Owner 8ri8c4heujv7jqugue9tfjntofabntdd.noblemail.org., Algorithm: 7, 3 Labels, original TTL: 1800 sec, Signature-expiration: 16.07.2019, 00:00:00 +, Signature-Inception: 16.06.2019, 01:00:49 +, KeyTag 1628, Signer-Name: noblemail.org

 

3. Name Servers

DomainNameserverNS-IP
www.mail.noblemail.org
  ns1.mail.noblemail.org

mail.noblemail.org
  ns1.mail.noblemail.org
149.28.199.145
San Jose/California/US

noblemail.org
  ns1.mail.noblemail.org


  ns2.mail.noblemail.org

org
  a0.org.afilias-nst.info / ns000b.app30.mia2.afilias-nst.info


  a2.org.afilias-nst.info / 2.fra.pch


  b0.org.afilias-nst.org / ns000b.app29.ams2.afilias-nst.info


  b2.org.afilias-nst.org / 4.fra.pch


  c0.org.afilias-nst.info / ns000b.app13.ams2.afilias-nst.info


  d0.org.afilias-nst.org / app1.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:2013511798
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:6


Domain:noblemail.org
Zone-Name:
Primary:ns1.mail.noblemail.org
Mail:hostmaster.mail.noblemail.org
Serial:2019061600
Refresh:7200
Retry:1800
Expire:1209600
TTL:1800
num Entries:2


Domain:mail.noblemail.org
Zone-Name:
Primary:ns1.mail.noblemail.org
Mail:hostmaster.mail.noblemail.org
Serial:2019061600
Refresh:7200
Retry:1800
Expire:1209600
TTL:1800
num Entries:1


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


:

:
DomainnameHttp-StatusredirectSec.G
• http://mail.noblemail.org/
149.28.199.145
301
https://mail.noblemail.org/

0.337
A
Server: nginx
Date: Sun, 16 Jun 2019 21:52:21 GMT
Content-Type: text/html
Content-Length: 178
Connection: close
Location: https://mail.noblemail.org/

• https://mail.noblemail.org/
149.28.199.145
200


1.750
A
Server: nginx
Date: Sun, 16 Jun 2019 21:52:22 GMT
Content-Type: text/html
Content-Length: 700
Last-Modified: Thu, 10 Jan 2019 11:13:19 GMT
Connection: close
ETag: "5c3728cf-2bc"
Strict-Transport-Security: max-age=15768000
Accept-Ranges: bytes

• http://mail.noblemail.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
149.28.199.145
404


0.337
A
Not Found
Visible Content:
Server: nginx
Date: Sun, 16 Jun 2019 21:52:23 GMT
Content-Type: text/html
Content-Length: 162
Connection: close

 

7. Comments


1. General Results, most used to calculate the result

Aname "mail.noblemail.org" is subdomain, public suffix is "org", top-level-domain-type is "generic", tld-manager is "Public Interest Registry (PIR)"
AGood: All ip addresses are public addresses
AGood: No asked Authoritative Name Server had a timeout
ADNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
Ahttps://mail.noblemail.org/ 149.28.199.145


Good: Valid DANE - entry found: signed Data _443._tcp.mail.noblemail.org: CertUsage 3 (DANE-EE, Domain-issued certificate), Selector 1 (SPKI, SubjectPublicKeyInfo), Matching 1 (SHA2-256, 256 bit hash by SHA2), CertificateAssociationData: 4ee67315c685e3b6bca8e27d96ebd1a2b052cf6f0366de2eacaae75969d62cb5 confirms the Certificate with the same value
AGood: destination is https
AGood - only one version with Http-Status 200
AGood: one preferred version: non-www is preferred
AGood: every https has a Strict Transport Security Header
AGood: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):0 complete Content-Type - header (2 urls)
https://mail.noblemail.org/ 149.28.199.145


Url with incomplete Content-Type - header - missing charset
http://mail.noblemail.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 149.28.199.145


Url with incomplete Content-Type - header - missing charset
Ahttp://mail.noblemail.org/ 149.28.199.145
301
https://mail.noblemail.org/
Correct redirect http - https with the same domain name
BWarning: HSTS max-age is too short - minimum 31536000 = 365 days required, 15768000 seconds = 182 days found

2. Header-Checks (Cross-Origin-* headers are alpha - started 2024-06-05)


3. DNS- and NameServer - Checks

AGood: Nameserver supports TCP connections: 1 good Nameserver
AGood: Nameserver supports Echo Capitalization: 1 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 1 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 1 good Nameserver
Nameserver doesn't pass all EDNS-Checks: ns1.mail.noblemail.org: 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.
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

AGood: 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.
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: 52380 milliseconds, 52.380 seconds

 

8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
mail.noblemail.org
149.28.199.145
443
ok
Tls12
DiffieHellman
2048
Aes128
128
Sha256
supported
ok
mail.noblemail.org
149.28.199.145
443
ok
Tls12

DiffieHellman
2048
Aes128
128
Sha256
supported
ok
 
no Tls.1.2
no Tls.1.1
no Tls.1.0

no Tls.1.2
no Tls.1.1
no Tls.1.0
Chain - incomplete

1CN=mail.noblemail.org


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

 

9. Certificates

1.
1.
CN=mail.noblemail.org
20.03.2019
18.06.2019
1998 days expired
mail.noblemail.org, noblemail.org, www.noblemail.org - 3 entries
1.
1.
CN=mail.noblemail.org
20.03.2019

18.06.2019
1998 days expired


mail.noblemail.org, noblemail.org, www.noblemail.org - 3 entries

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:032D691CCF49EF116BCD15A896963D1D5198
Thumbprint:0E1F942A1E660AF5A787A79679C3AF03DB67901C
SHA256 / Certificate:b9iUKIm6Dk1flaXKljJyWuolesx3LSId7bmO0J/Wkqw=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):4ee67315c685e3b6bca8e27d96ebd1a2b052cf6f0366de2eacaae75969d62cb5
SHA256 hex / Subject Public Key Information (SPKI):4ee67315c685e3b6bca8e27d96ebd1a2b052cf6f0366de2eacaae75969d62cb5
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)




2.
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
17.03.2016
17.03.2021
1360 days expired


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

17.03.2021
1360 days expired




KeyalgorithmRSA 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:




3.
CN=DST Root CA X3, O=Digital Signature Trust Co.
30.09.2000
30.09.2021
1163 days expired


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

30.09.2021
1163 days expired




KeyalgorithmRSA 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)

Small Code Update - wait one minute

 

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

DomainnameflagNameValue∑ Queries∑ Timeout
mail.noblemail.org
0

no CAA entry found
1
0
noblemail.org
0

no CAA entry found
1
0
org
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
noblemail.org
v=spf1 mx -all
ok
1
0
mail.noblemail.org
v=spf1 mx -all
ok
1
0
_acme-challenge.mail.noblemail.org

Name Error - The domain name does not exist
1
0
_acme-challenge.mail.noblemail.org.noblemail.org

Name Error - The domain name does not exist
1
0
_acme-challenge.mail.noblemail.org.mail.noblemail.org

Name Error - The domain name does not exist
1
0

 

16. DomainService - Entries

No DomainServiceEntries entries found

 

 

17. Cipher Suites

No Ciphers found

 

18. Portchecks

No Port informations found. The feature is new (startet 2019-07-09), so recheck this domain.

 

 

Permalink: https://check-your-website.server-daten.de/?i=d2d41b17-689c-4e84-872f-75f7d8c57ffd

 

Last Result: https://check-your-website.server-daten.de/?q=mail.noblemail.org - 2019-06-16 23:51:36

 

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.noblemail.org" target="_blank">Check this Site: mail.noblemail.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=mail.noblemail.org