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



X

DNS-problem - authoritative Nameserver refused, not defined or timeout

Checked:
05.08.2022 06:49:40


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
cms.whaaatapp.com
A
195.15.236.42
Geneva/Switzerland (CH) - Infomaniak Network Management
No Hostname found
yes
1
0

AAAA

yes


www.cms.whaaatapp.com

Name Error
yes
1
0
*.whaaatapp.com
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes


*.cms.whaaatapp.com
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



2 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 20826, Flags 256



1 RRSIG RR to validate DNSKEY RR found



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



DS with Algorithm 8, KeyTag 30909, DigestType 2 and Digest 4tPJFvbe6scylOgmj7WIUESoM/xUWViPSpGEz8QaV2Y=



1 RRSIG RR to validate DS RR found



RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 17.08.2022, 21:00:00 +, Signature-Inception: 04.08.2022, 20:00:00 +, KeyTag 20826, Signer-Name: (root)



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



2 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 32298, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 18.08.2022, 18:24:21 +, Signature-Inception: 03.08.2022, 18:19:21 +, KeyTag 30909, Signer-Name: com



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



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

Zone: whaaatapp.com
whaaatapp.com
1 DS RR in the parent zone found



DS with Algorithm 13, KeyTag 7367, DigestType 2 and Digest 2wCfLRsbuJ76/zDmTUGxrGhZzBIvyyO8KXQbYa+8Qfs=



1 RRSIG RR to validate DS RR found



RRSIG-Owner whaaatapp.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 10.08.2022, 05:44:51 +, Signature-Inception: 03.08.2022, 04:34:51 +, KeyTag 32298, Signer-Name: com



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



2 DNSKEY RR found



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



Public Key with Algorithm 13, KeyTag 27084, Flags 256



2 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner whaaatapp.com., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 25.08.2022, 23:25:29 +, Signature-Inception: 04.08.2022, 23:12:19 +, KeyTag 7367, Signer-Name: whaaatapp.com



RRSIG-Owner whaaatapp.com., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 25.08.2022, 23:25:29 +, Signature-Inception: 04.08.2022, 23:12:19 +, KeyTag 27084, Signer-Name: whaaatapp.com



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



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



Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 7367, DigestType 2 and Digest "2wCfLRsbuJ76/zDmTUGxrGhZzBIvyyO8KXQbYa+8Qfs=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: cms.whaaatapp.com
cms.whaaatapp.com
0 DS RR in the parent zone found



DS-Query in the parent zone has a valid NSEC RR as result with the domain name between the NSEC-Owner "cms.whaaatapp.com" and the NextOwner "www.whaaatapp.com". So the parent zone confirmes the non-existence of a DS RR.
Bitmap: A, RRSIG, NSEC



0 DNSKEY RR found






RRSIG Type 1 validates the A - Result: 195.15.236.42
Validated: RRSIG-Owner cms.whaaatapp.com., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 24.08.2022, 07:44:04 +, Signature-Inception: 04.08.2022, 10:53:42 +, KeyTag 27084, Signer-Name: whaaatapp.com



CNAME-Query sends a valid NSEC RR as result with the query name "cms.whaaatapp.com" equal the NSEC-owner "cms.whaaatapp.com" and the NextOwner "www.whaaatapp.com". 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, RRSIG, NSEC Validated: RRSIG-Owner cms.whaaatapp.com., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 21.08.2022, 12:07:59 +, Signature-Inception: 04.08.2022, 07:26:05 +, KeyTag 27084, Signer-Name: whaaatapp.com



Status: Good. NoData-Proof required and found.



TXT-Query sends a valid NSEC RR as result with the query name "cms.whaaatapp.com" equal the NSEC-owner "cms.whaaatapp.com" and the NextOwner "www.whaaatapp.com". So the zone confirmes the not-existence of that TXT RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, RRSIG, NSEC Validated: RRSIG-Owner cms.whaaatapp.com., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 21.08.2022, 12:07:59 +, Signature-Inception: 04.08.2022, 07:26:05 +, KeyTag 27084, Signer-Name: whaaatapp.com



Status: Good. NoData-Proof required and found.



AAAA-Query sends a valid NSEC RR as result with the query name "cms.whaaatapp.com" equal the NSEC-owner "cms.whaaatapp.com" and the NextOwner "www.whaaatapp.com". 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, RRSIG, NSEC Validated: RRSIG-Owner cms.whaaatapp.com., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 21.08.2022, 12:07:59 +, Signature-Inception: 04.08.2022, 07:26:05 +, KeyTag 27084, Signer-Name: whaaatapp.com



Status: Good. NoData-Proof required and found.



TLSA-Query (_443._tcp.cms.whaaatapp.com) sends a valid NSEC RR as result with the owner name cms.whaaatapp.com. So that's the Closest Encloser of the query name. TLSA-Query sends a valid NSEC RR as result and covers the Wildcard expansion of the ClosestEncloser with the owner "cms.whaaatapp.com" and the NextOwner "www.whaaatapp.com". So that NSEC confirms the not-existence of the Wildcard expansion. TLSA-Query (_443._tcp.cms.whaaatapp.com) sends a valid NSEC RR as result with the query name "_443._tcp.cms.whaaatapp.com" between the NSEC-owner "cms.whaaatapp.com" and the NextOwner "www.whaaatapp.com". So the zone confirmes the not-existence of that TLSA RR.TLSA-Query (_443._tcp.cms.whaaatapp.com) sends a valid NSEC RR as result with the parent Wildcard "*._tcp.cms.whaaatapp.com" between the NSEC-owner "cms.whaaatapp.com" and the NextOwner "www.whaaatapp.com". So the zone confirmes the not-existence of that Wildcard-expansion.
Bitmap: A, RRSIG, NSEC Validated: RRSIG-Owner cms.whaaatapp.com., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 21.08.2022, 12:07:59 +, Signature-Inception: 04.08.2022, 07:26:05 +, KeyTag 27084, Signer-Name: whaaatapp.com



Status: Good. NXDomain-Proof required and found.



CAA-Query sends a valid NSEC RR as result with the query name "cms.whaaatapp.com" equal the NSEC-owner "cms.whaaatapp.com" and the NextOwner "www.whaaatapp.com". 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, RRSIG, NSEC Validated: RRSIG-Owner cms.whaaatapp.com., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 21.08.2022, 12:07:59 +, Signature-Inception: 04.08.2022, 07:26:05 +, KeyTag 27084, Signer-Name: whaaatapp.com



Status: Good. NoData-Proof required and found.

Zone: www.cms.whaaatapp.com
www.cms.whaaatapp.com
0 DS RR in the parent zone found



DS-Query in the parent zone has a valid NSEC RR as result with the domain name between the NSEC-Owner "cms.whaaatapp.com" and the NextOwner "www.whaaatapp.com". So the parent zone confirmes the non-existence of a DS RR.
Bitmap: A, RRSIG, NSEC


3. Name Servers

DomainNameserverNS-IP
www.cms.whaaatapp.com
  ns41.infomaniak.com

cms.whaaatapp.com
  ns41.infomaniak.com
83.166.143.74
Vevey/Vaud/Switzerland (CH) - Infomaniak Network SA


 
2001:1600:0:aaaa::3
Geneva/Switzerland (CH) - Infomaniak Network SA

whaaatapp.com
  ns41.infomaniak.com
83.166.143.74
Vevey/Vaud/Switzerland (CH) - Infomaniak Network SA


 
2001:1600:0:aaaa::3
Geneva/Switzerland (CH) - Infomaniak Network SA


  ns42.infomaniak.com
83.166.143.75
Vevey/Vaud/Switzerland (CH) - Infomaniak Network SA


 
2001:1600:0:aaaa::4
Geneva/Switzerland (CH) - Infomaniak Network SA

com
  a.gtld-servers.net / nnn1-stk4


  b.gtld-servers.net / nnn1-elpar7


  c.gtld-servers.net / nnn1-stk4


  d.gtld-servers.net / nnn1-stk4


  e.gtld-servers.net / nnn1-stk4


  f.gtld-servers.net / nnn1-fra5


  g.gtld-servers.net / nnn1-fra5


  h.gtld-servers.net / nnn1-fra5


  i.gtld-servers.net / nnn1-fra5


  j.gtld-servers.net / nnn1-lon5


  k.gtld-servers.net / nnn1-lon5


  l.gtld-servers.net / nnn1-lon5


  m.gtld-servers.net / nnn1-lon5


4. SOA-Entries


Domain:com
Zone-Name:com
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1659674949
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:2


Domain:com
Zone-Name:com
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1659674964
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:11


Domain:whaaatapp.com
Zone-Name:whaaatapp.com
Primary:ns41.infomaniak.com
Mail:hostmaster.infomaniak.ch
Serial:2022080415
Refresh:10800
Retry:3600
Expire:605800
TTL:3600
num Entries:4


Domain:cms.whaaatapp.com
Zone-Name:whaaatapp.com
Primary:ns41.infomaniak.com
Mail:hostmaster.infomaniak.ch
Serial:2022080415
Refresh:10800
Retry:3600
Expire:605800
TTL:3600
num Entries:2


Domain:www.cms.whaaatapp.com
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://cms.whaaatapp.com/
195.15.236.42
302
http://cms.whaaatapp.com/./admin
Html is minified: 100.00 %
0.066
D
Content-Security-Policy: script-src 'self' 'unsafe-eval';worker-src 'self' blob:;child-src 'self' blob:;img-src 'self' data: blob: https://cdn.directus.io;media-src 'self' https://cdn.directus.io;connect-src 'self' https://*;default-src 'self';base-uri 'self';block-all-mixed-content;font-src 'self' https: data:;frame-ancestors 'self';object-src 'none';script-src-attr 'none';style-src 'self' https: 'unsafe-inline'
X-Powered-By: Directus
Access-Control-Allow-Origin: *
Access-Control-Allow-Credentials: true
Access-Control-Expose-Headers: Content-Range
Location: ./admin
Vary: Accept
Content-Type: text/plain; charset=utf-8
Content-Length: 29
Date: Fri, 05 Aug 2022 04:50:27 GMT
Connection: close

• http://cms.whaaatapp.com/./admin

200

Html is minified: 109.07 %
0.096
H
Content-Security-Policy: script-src 'self' 'unsafe-eval';worker-src 'self' blob:;child-src 'self' blob:;img-src 'self' data: blob: https://cdn.directus.io;media-src 'self' https://cdn.directus.io;connect-src 'self' https://*;default-src 'self';base-uri 'self';block-all-mixed-content;font-src 'self' https: data:;frame-ancestors 'self';object-src 'none';script-src-attr 'none';style-src 'self' https: 'unsafe-inline'
X-Powered-By: Directus
Access-Control-Allow-Origin: *
Access-Control-Allow-Credentials: true
Access-Control-Expose-Headers: Content-Range
Cache-Control: no-cache
Content-Type: text/html; charset=utf-8
Content-Length: 1708
ETag: W/"6ac-zZ4nwnwVlrogp304NcqCE306c4k"
Date: Fri, 05 Aug 2022 04:50:29 GMT
Connection: close

• https://cms.whaaatapp.com/
195.15.236.42
-2

1.074
V
ConnectFailure - Unable to connect to the remote server

• http://cms.whaaatapp.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
195.15.236.42
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
404

Html is minified: 100.00 %
0.080
A
Not Found
Visible Content: {"errors":[{"message":"Route /.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de doesn't exist.","extensions":{"code":"ROUTE_NOT_FOUND"}}]}
Content-Security-Policy: script-src 'self' 'unsafe-eval';worker-src 'self' blob:;child-src 'self' blob:;img-src 'self' data: blob: https://cdn.directus.io;media-src 'self' https://cdn.directus.io;connect-src 'self' https://*;default-src 'self';base-uri 'self';block-all-mixed-content;font-src 'self' https: data:;frame-ancestors 'self';object-src 'none';script-src-attr 'none';style-src 'self' https: 'unsafe-inline'
X-Powered-By: Directus
Access-Control-Allow-Origin: *
Access-Control-Allow-Credentials: true
Access-Control-Expose-Headers: Content-Range
Content-Type: application/json; charset=utf-8
Content-Length: 158
ETag: W/"9e-F3VdS5enD668DToH8M8AnEvfBzU"
Date: Fri, 05 Aug 2022 04:50:28 GMT
Connection: close

• https://195.15.236.42/
195.15.236.42
-2

1.090
V
ConnectFailure - Unable to connect to the remote server

7. Comments


1. General Results, most used to calculate the result

Aname "cms.whaaatapp.com" is subdomain, public suffix is ".com", top-level-domain is ".com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .com-domains preloaded: 63591 (complete: 175327)
Agood: All ip addresses are public addresses
Warning: Only one ip address found: cms.whaaatapp.com 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: cms.whaaatapp.com 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 - only one version with Http-Status 200
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.
AGood: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
Dhttp://cms.whaaatapp.com/ 195.15.236.42
302
http://cms.whaaatapp.com/./admin
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
HFatal error: http result with http-status 200, no encryption. Add a redirect http ⇒ https, so every connection is secure. 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.
Vhttps://cms.whaaatapp.com/ 195.15.236.42
-2

connect failure - perhaps firewall
Vhttps://195.15.236.42/ 195.15.236.42
-2

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 cms.whaaatapp.com, 1 ip addresses.

2. DNS- and NameServer - Checks

AInfo:: 9 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
AInfo:: 9 Queries complete, 9 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
Ok (4 - 8):: An average of 4.5 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 2 different Name Servers found: ns41.infomaniak.com, ns42.infomaniak.com, 2 Name Servers included in Delegation: ns41.infomaniak.com, ns42.infomaniak.com, 2 Name Servers included in 1 Zone definitions: ns41.infomaniak.com, ns42.infomaniak.com, 1 Name Servers listed in SOA.Primary: ns41.infomaniak.com.
AGood: Only one SOA.Primary Name Server found.: ns41.infomaniak.com.
AGood: SOA.Primary Name Server included in the delegation set.: ns41.infomaniak.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: ns41.infomaniak.com, ns42.infomaniak.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: infomaniak.com
Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: CH
AInfo: Ipv4-Subnet-list: 2 Name Servers, 1 different subnets (first Byte): 83., 1 different subnets (first two Bytes): 83.166., 1 different subnets (first three Bytes): 83.166.143.
XFatal: All Name Server IPv4 addresses from the same subnet. Check https://www.iana.org/help/nameserver-requirements to learn some basics about name server configurations. If you manage these name servers, fix it. If it's your provider, change your provider.:
AInfo: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2001:, 1 different subnets (first two blocks): 2001:1600:, 1 different subnets (first three blocks): 2001:1600:0000:, 1 different subnets (first four blocks): 2001:1600:0000:aaaa:
Fatal: All Name Server IPv6 addresses from the same subnet.
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: ns41.infomaniak.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.
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.

3. 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.
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: 60590 milliseconds, 60.590 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)

Issuerlast 7 daysactivenum Certs
CN=R3, O=Let's Encrypt, C=US
0
1
2

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
3989430563
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-07-26 10:00:54
2022-10-24 10:00:53
cms.whaaatapp.com - 1 entries


3774004520
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-05-27 08:10:37
2022-08-25 08:10:36
cms.whaaatapp.com - 1 entries



2. Source crt.sh - old and new certificates, sometimes very slow - only certificates with "not after" > of the last months are listed

Issuerlast 7 daysactivenum Certs
CN=R3, O=Let's Encrypt, C=US
0 /0 new
1
2

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
7202803718
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-07-26 08:00:54
2022-10-24 08:00:53
cms.whaaatapp.com
1 entries


6811832930
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-05-27 06:10:37
2022-08-25 06:10:36
cms.whaaatapp.com
1 entries



11. Html-Content - Entries

No Html-Content entries found. Only checked if https + status 200/401/403/404


12. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: ns41.infomaniak.com, ns42.infomaniak.com

QNr.DomainTypeNS used
1
com
NS
b.root-servers.net (2001:500:200::b)

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

Answer: ns1.infomaniak.ch, ns2.infomaniak.ch
3
ns42.infomaniak.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns1.infomaniak.ch, ns2.infomaniak.ch
4
ch
NS
l.root-servers.net (2001:500:9f::42)

Answer: a.nic.ch, b.nic.ch, d.nic.ch, e.nic.ch, f.nic.ch
5
ns1.infomaniak.ch: 2001:1600:0:aaaa::a, 84.16.66.66
NS
a.nic.ch (2001:620:0:ff::56)

Answer: ns2.infomaniak.ch
2001:1600:0:aaaa::b, 84.16.67.66
6
ns41.infomaniak.com: 83.166.143.74
A
ns1.infomaniak.ch (2001:1600:0:aaaa::a)
7
ns41.infomaniak.com: 2001:1600:0:aaaa::3
AAAA
ns1.infomaniak.ch (2001:1600:0:aaaa::a)
8
ns42.infomaniak.com: 83.166.143.75
A
ns1.infomaniak.ch (2001:1600:0:aaaa::a)
9
ns42.infomaniak.com: 2001:1600:0:aaaa::4
AAAA
ns1.infomaniak.ch (2001:1600:0:aaaa::a)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
cms.whaaatapp.com
0

no CAA entry found
1
0
whaaatapp.com
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
whaaatapp.com
google-site-verification=Qv1apWHMiFvlvWA-fsIsYyDHs3u7xsWOzf66DO6AynQ
ok
1
0
whaaatapp.com
v=spf1 include:spf.infomaniak.ch -all
ok
1
0
cms.whaaatapp.com

ok
1
0
_acme-challenge.cms.whaaatapp.com

Name Error - The domain name does not exist
1
0
_acme-challenge.cms.whaaatapp.com.whaaatapp.com

Name Error - The domain name does not exist
1
0
_acme-challenge.cms.whaaatapp.com.cms.whaaatapp.com

Name Error - The domain name does not exist
1
0


15. DomainService - Entries (SSHFP Check is new - 2022-09-24, may be incomplete, alpha, some results are required)

No DomainServiceEntries entries found



16. Cipher Suites

No results


17. Portchecks

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



Permalink: https://check-your-website.server-daten.de/?i=d550263a-b9e8-4fb2-b65d-4087c5de5eed


Last Result: https://check-your-website.server-daten.de/?q=cms.whaaatapp.com - 2022-08-05 06:49:40


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

<a href="https://check-your-website.server-daten.de/?q=cms.whaaatapp.com" target="_blank">Check this Site: cms.whaaatapp.com</a>

Do you really want to support this project? Donate: Check-your-website, IBAN DE98 1001 0010 0575 2211 07, SWIFT/BIC PBNKDEFF, Euro