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



Q

http sent over port 443

Checked:
07.04.2021 19:47:17


Older results


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
jdfbi.jdfvms.com
A
35.210.23.244
Brussels/Brussels Capital/Belgium (BE) - Google LLC
Hostname: 244.23.210.35.bc.googleusercontent.com
yes
1
0

AAAA

yes


www.jdfbi.jdfvms.com

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



AAAA
Name Error
yes



CNAME
Name Error
yes


*.jdfbi.jdfvms.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



3 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 14631, Flags 256



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



Public Key with Algorithm 8, KeyTag 42351, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 22.04.2021, 00:00:00 +, Signature-Inception: 01.04.2021, 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: 20.04.2021, 17:00:00 +, Signature-Inception: 07.04.2021, 16:00:00 +, KeyTag 14631, Signer-Name: (root)



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



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 15.04.2021, 18:24:21 +, Signature-Inception: 31.03.2021, 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: jdfvms.com
jdfvms.com
1 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 37121, DigestType 2 and Digest RyeoYz/mW/YLyV74OjLHs+XxASI+CErpMRsjZKrErpE=



1 RRSIG RR to validate DS RR found



RRSIG-Owner jdfvms.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 11.04.2021, 05:11:00 +, Signature-Inception: 04.04.2021, 04:01:00 +, KeyTag 58540, Signer-Name: com



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



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 33106, Flags 256



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



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner jdfvms.com., Algorithm: 8, 2 Labels, original TTL: 300 sec, Signature-expiration: 26.04.2021, 16:04:31 +, Signature-Inception: 04.04.2021, 16:04:31 +, KeyTag 37121, Signer-Name: jdfvms.com



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



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 37121, DigestType 2 and Digest "RyeoYz/mW/YLyV74OjLHs+XxASI+CErpMRsjZKrErpE=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: jdfbi.jdfvms.com
jdfbi.jdfvms.com
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 "f3347sq9dj98bj995fum5kgkl11qa191" between the hashed NSEC3-owner "f3347sq9dj98bj995fum5kgkl11qa191" and the hashed NextOwner "ftveaneotpc95153a2lmn3giv5g638s8". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: A, RRSIG Validated: RRSIG-Owner f3347sq9dj98bj995fum5kgkl11qa191.jdfvms.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 26.04.2021, 16:04:31 +, Signature-Inception: 04.04.2021, 16:04:31 +, KeyTag 33106, Signer-Name: jdfvms.com



0 DNSKEY RR found






RRSIG Type 1 validates the A - Result: 35.210.23.244
Validated: RRSIG-Owner jdfbi.jdfvms.com., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 26.04.2021, 16:04:31 +, Signature-Inception: 04.04.2021, 16:04:31 +, KeyTag 33106, Signer-Name: jdfvms.com



CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "f3347sq9dj98bj995fum5kgkl11qa191" equal the hashed NSEC3-owner "f3347sq9dj98bj995fum5kgkl11qa191" and the hashed NextOwner "ftveaneotpc95153a2lmn3giv5g638s8". 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 Validated: RRSIG-Owner f3347sq9dj98bj995fum5kgkl11qa191.jdfvms.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 26.04.2021, 16:04:31 +, Signature-Inception: 04.04.2021, 16:04:31 +, KeyTag 33106, Signer-Name: jdfvms.com



Status: Good. NoData-Proof required and found.



TXT-Query sends a valid NSEC3 RR as result with the hashed query name "f3347sq9dj98bj995fum5kgkl11qa191" equal the hashed NSEC3-owner "f3347sq9dj98bj995fum5kgkl11qa191" and the hashed NextOwner "ftveaneotpc95153a2lmn3giv5g638s8". 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 Validated: RRSIG-Owner f3347sq9dj98bj995fum5kgkl11qa191.jdfvms.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 26.04.2021, 16:04:31 +, Signature-Inception: 04.04.2021, 16:04:31 +, KeyTag 33106, Signer-Name: jdfvms.com



Status: Good. NoData-Proof required and found.



AAAA-Query sends a valid NSEC3 RR as result with the hashed query name "f3347sq9dj98bj995fum5kgkl11qa191" equal the hashed NSEC3-owner "f3347sq9dj98bj995fum5kgkl11qa191" and the hashed NextOwner "ftveaneotpc95153a2lmn3giv5g638s8". 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 Validated: RRSIG-Owner f3347sq9dj98bj995fum5kgkl11qa191.jdfvms.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 26.04.2021, 16:04:31 +, Signature-Inception: 04.04.2021, 16:04:31 +, KeyTag 33106, Signer-Name: jdfvms.com



Status: Good. NoData-Proof required and found.



TLSA-Query (_443._tcp.jdfbi.jdfvms.com) sends a valid NSEC3 RR as result with the hashed owner name "f3347sq9dj98bj995fum5kgkl11qa191" (unhashed: jdfbi.jdfvms.com). So that's the Closest Encloser of the query name.
Bitmap: A, RRSIG Validated: RRSIG-Owner f3347sq9dj98bj995fum5kgkl11qa191.jdfvms.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 26.04.2021, 16:04:31 +, Signature-Inception: 04.04.2021, 16:04:31 +, KeyTag 33106, Signer-Name: jdfvms.com



Status: Good. NXDomain-Proof required and found.



TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "0rdmbtr28bcl5k3b1q98t1pvbg667n1q" (unhashed: _tcp.jdfbi.jdfvms.com) with the owner "rmgkq7sbepoa642vl6im7icoh1up37g2" and the NextOwner "7fcujnmct60hga8nal3l1vt6eeplaa5r". So that NSEC3 confirms the not-existence of the Next Closer Name.
Bitmap: CNAME, RRSIG Validated: RRSIG-Owner rmgkq7sbepoa642vl6im7icoh1up37g2.jdfvms.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 26.04.2021, 16:04:31 +, Signature-Inception: 04.04.2021, 16:04:31 +, KeyTag 33106, Signer-Name: jdfvms.com



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 "en2nl76en6vd6mvfch9n4ehngmnh1rvt" (unhashed: *.jdfbi.jdfvms.com) with the owner "7fcujnmct60hga8nal3l1vt6eeplaa5r" and the NextOwner "f3347sq9dj98bj995fum5kgkl11qa191". So that NSEC3 confirms the not-existence of the Wildcard expansion.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner 7fcujnmct60hga8nal3l1vt6eeplaa5r.jdfvms.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 26.04.2021, 16:04:31 +, Signature-Inception: 04.04.2021, 16:04:31 +, KeyTag 33106, Signer-Name: jdfvms.com



Status: Good. NXDomain-Proof required and found.



CAA-Query sends a valid NSEC3 RR as result with the hashed query name "f3347sq9dj98bj995fum5kgkl11qa191" equal the hashed NSEC3-owner "f3347sq9dj98bj995fum5kgkl11qa191" and the hashed NextOwner "ftveaneotpc95153a2lmn3giv5g638s8". 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 Validated: RRSIG-Owner f3347sq9dj98bj995fum5kgkl11qa191.jdfvms.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 26.04.2021, 16:04:31 +, Signature-Inception: 04.04.2021, 16:04:31 +, KeyTag 33106, Signer-Name: jdfvms.com



Status: Good. NoData-Proof required and found.

Zone: www.jdfbi.jdfvms.com
www.jdfbi.jdfvms.com
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 "dpd3jrjv7fbp4a59t9hk0ru20fa2f9sd" between the hashed NSEC3-owner "7fcujnmct60hga8nal3l1vt6eeplaa5r" and the hashed NextOwner "f3347sq9dj98bj995fum5kgkl11qa191". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner 7fcujnmct60hga8nal3l1vt6eeplaa5r.jdfvms.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 26.04.2021, 16:04:31 +, Signature-Inception: 04.04.2021, 16:04:31 +, KeyTag 33106, Signer-Name: jdfvms.com



Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner 7fcujnmct60hga8nal3l1vt6eeplaa5r.jdfvms.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 26.04.2021, 16:04:31 +, Signature-Inception: 04.04.2021, 16:04:31 +, KeyTag 33106, Signer-Name: jdfvms.com



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "f3347sq9dj98bj995fum5kgkl11qa191" as Owner. That's the Hash of "jdfbi.jdfvms.com" with the NextHashedOwnerName "ftveaneotpc95153a2lmn3giv5g638s8". So that domain name is the Closest Encloser of "www.jdfbi.jdfvms.com". Opt-Out: False.
Bitmap: A, RRSIG Validated: RRSIG-Owner f3347sq9dj98bj995fum5kgkl11qa191.jdfvms.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 26.04.2021, 16:04:31 +, Signature-Inception: 04.04.2021, 16:04:31 +, KeyTag 33106, Signer-Name: jdfvms.com



The ClosestEncloser says, that "*.jdfbi.jdfvms.com" with the Hash "en2nl76en6vd6mvfch9n4ehngmnh1rvt" 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 "7fcujnmct60hga8nal3l1vt6eeplaa5r" and the Next Owner "f3347sq9dj98bj995fum5kgkl11qa191", 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: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS Validated: RRSIG-Owner 7fcujnmct60hga8nal3l1vt6eeplaa5r.jdfvms.com., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 26.04.2021, 16:04:31 +, Signature-Inception: 04.04.2021, 16:04:31 +, KeyTag 33106, Signer-Name: jdfvms.com


3. Name Servers

DomainNameserverNS-IP
www.jdfbi.jdfvms.com
  ns-cloud-e1.googledomains.com

jdfbi.jdfvms.com
  ns-cloud-e1.googledomains.com
216.239.32.110
Montreal/Quebec/Canada (CA) - Google LLC


 
2001:4860:4802:32::6e
Montreal/Quebec/Canada (CA) - Google LLC

jdfvms.com
  ns-cloud-e1.googledomains.com
216.239.32.110
Montreal/Quebec/Canada (CA) - Google LLC


 
2001:4860:4802:32::6e
Montreal/Quebec/Canada (CA) - Google LLC


  ns-cloud-e2.googledomains.com
216.239.34.110
Montreal/Quebec/Canada (CA) - Google LLC


 
2001:4860:4802:34::6e
Montreal/Quebec/Canada (CA) - Google LLC


  ns-cloud-e3.googledomains.com
216.239.36.110
Montreal/Quebec/Canada (CA) - Google LLC


 
2001:4860:4802:36::6e
Montreal/Quebec/Canada (CA) - Google LLC


  ns-cloud-e4.googledomains.com
216.239.38.110
Montreal/Quebec/Canada (CA) - Google LLC


 
2001:4860:4802:38::6e
Montreal/Quebec/Canada (CA) - Google LLC

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


  b.gtld-servers.net / nnn1-eltxl2


  c.gtld-servers.net / nnn1-was1


T  d.gtld-servers.net / nnn1-was1


  e.gtld-servers.net / nnn1-was1


  f.gtld-servers.net / nnn1-ams6


  g.gtld-servers.net / nnn1-ams6


  h.gtld-servers.net / nnn1-ams6


  i.gtld-servers.net / nnn1-ams6


  j.gtld-servers.net / nnn1-ein1


  k.gtld-servers.net / nnn1-ein1


  l.gtld-servers.net / nnn1-ein1


  m.gtld-servers.net / nnn1-ein1


4. SOA-Entries


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


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


Domain:jdfvms.com
Zone-Name:jdfvms.com
Primary:ns-cloud-e1.googledomains.com
Mail:cloud-dns-hostmaster.google.com
Serial:12
Refresh:21600
Retry:3600
Expire:259200
TTL:300
num Entries:8


Domain:jdfbi.jdfvms.com
Zone-Name:jdfvms.com
Primary:ns-cloud-e1.googledomains.com
Mail:cloud-dns-hostmaster.google.com
Serial:12
Refresh:21600
Retry:3600
Expire:259200
TTL:300
num Entries:2


Domain:www.jdfbi.jdfvms.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://jdfbi.jdfvms.com/
35.210.23.244 No GZip used - 2532 / 11137 - 22.74 % possible
200

Html is minified: 157.97 %
0.057
H
Content-Type: text/html;charset=UTF-8
Transfer-Encoding: chunked
Date: Wed, 07 Apr 2021 17:48:25 GMT
Connection: close

• https://jdfbi.jdfvms.com/
35.210.23.244
-4

0.110
W
SendFailure - The underlying connection was closed: An unexpected error occurred on a send.

• http://jdfbi.jdfvms.com:443/
35.210.23.244 No GZip used - 2532 / 11137 - 22.74 % possible
200

Html is minified: 157.97 %
0.053
Q
Visible Content: Home Documentation Configuration Examples Wiki Mailing Lists Find Help Apache Tomcat/9.0.44 If you're seeing this, you've successfully installed Tomcat. Congratulations! Recommended Reading: Security Considerations How-To Manager Application How-To Clustering/Session Replication How-To Server Status Manager App Host Manager Developer Quick Start Tomcat Setup First Web Application Realms & AAA JDBC DataSources Examples Servlet Specifications Tomcat Versions Managing Tomcat For security, access to the manager webapp is restricted. Users are defined in: $CATALINA_HOME/conf/tomcat-users.xml In Tomcat 9.0 access to the manager application is split between different users.   Read more... Release Notes Changelog Migration Guide Security Notices Documentation Tomcat 9.0 Documentation Tomcat 9.0 Configuration Tomcat Wiki Find additional important configuration information in: $CATALINA_HOME/RUNNING.txt Developers may be interested in: Tomcat 9.0 Bug Database Tomcat 9.0 JavaDocs Tomcat 9.0 Git Repository at GitHub Getting Help FAQ and Mailing Lists The following mailing lists are available: tomcat-announce Important announcements, releases, security vulnerability notifications. (Low volume). tomcat-users User support and discussion taglibs-user User support and discussion for Apache Taglibs tomcat-dev Development mailing list, including commit messages Other Downloads Tomcat Connectors Tomcat Native Taglibs Deployer Other Documentation Tomcat Connectors mod_jk Documentation Tomcat Native Deployer Get Involved Overview Source Repositories Mailing Lists Wiki Miscellaneous Contact Legal Sponsorship Thanks Apache Software Foundation Who We Are Heritage Apache Home Resources Copyright ©1999-2021 Apache Software Foundation. All Rights Reserved
Content-Type: text/html;charset=UTF-8
Transfer-Encoding: chunked
Date: Wed, 07 Apr 2021 17:48:25 GMT
Connection: close

• http://jdfbi.jdfvms.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
35.210.23.244
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 1/254
404

Html is minified: 153.62 %
0.057
A
Visible Content: HTTP Status 404 – Not Found Type Status Report Message The requested resource [/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de] is not available Description The origin server did not find a current representation for the target resource or is not willing to disclose that one exists. Apache Tomcat/9.0.44
Content-Type: text/html;charset=utf-8
Content-Language: en
Content-Length: 828
Date: Wed, 07 Apr 2021 17:48:25 GMT
Connection: close

• https://35.210.23.244/
35.210.23.244
-4

0.096
W
SendFailure - The underlying connection was closed: An unexpected error occurred on a send.

7. Comments


1. General Results, most used to calculate the result

Aname "jdfbi.jdfvms.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: 57967 (complete: 151507)
Agood: All ip addresses are public addresses
Warning: Only one ip address found: jdfbi.jdfvms.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: jdfbi.jdfvms.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: 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)
CError - more then one version with Http-Status 200. After all redirects, all users (and search engines) should see the same https url: Non-www or www, but not both with http status 200.
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.
Qhttp://jdfbi.jdfvms.com:443/ 35.210.23.244
200

Misconfiguration: http sent over port 443. Wrong port forwarding port 443 to port 80 or wrong vHost definition. If you use a virtual Host <VirtualHost ip-address:443>, try <VirtualHost *:443>.
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 jdfbi.jdfvms.com, 1 ip addresses.

2. DNS- and NameServer - Checks

AInfo:: 13 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers.
AInfo:: 13 Queries complete, 13 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
Ok (4 - 8):: An average of 3.3 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 4 different Name Servers found: ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com, 4 Name Servers included in Delegation: ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com, 4 Name Servers included in 1 Zone definitions: ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com, 1 Name Servers listed in SOA.Primary: ns-cloud-e1.googledomains.com.
AGood: Only one SOA.Primary Name Server found.: ns-cloud-e1.googledomains.com.
AGood: SOA.Primary Name Server included in the delegation set.: ns-cloud-e1.googledomains.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: ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.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: 4 different Name Servers found
AGood: All name servers have ipv4- and ipv6-addresses.: 4 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.: 4 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: googledomains.com
Warning: All Name Servers from the same Country / IP location.: 4 Name Servers, 1 Countries: CA
AInfo: Ipv4-Subnet-list: 4 Name Servers, 1 different subnets (first Byte): 216., 1 different subnets (first two Bytes): 216.239., 4 different subnets (first three Bytes): 216.239.32., 216.239.34., 216.239.36., 216.239.38.
AGood: Name Server IPv4-addresses from different subnet found:
AInfo: IPv6-Subnet-list: 4 Name Servers with IPv6, 1 different subnets (first block): 2001:, 1 different subnets (first two blocks): 2001:4860:, 1 different subnets (first three blocks): 2001:4860:4802:, 4 different subnets (first four blocks): 2001:4860:4802:0032:, 2001:4860:4802:0034:, 2001:4860:4802:0036:, 2001:4860:4802:0038:
AGood: Name Server IPv6 addresses from different subnets found.
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
XNameserver Timeout checking EDNS512: d.gtld-servers.net
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: ns-cloud-e1.googledomains.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: 86483 milliseconds, 86.483 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
1

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
2237751381
leaf cert
CN=R3, O=Let's Encrypt, C=US
2021-01-22 16:57:10
2021-04-22 16:57:10
jdfbi.jdfvms.com - 1 entries



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

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

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
3966985305
leaf cert
CN=R3, O=Let's Encrypt, C=US
2021-01-22 15:57:10
2021-04-22 14:57:10
jdfbi.jdfvms.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: ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com

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

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
ns-cloud-e1.googledomains.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns5.googledomains.com, ns6.googledomains.com, ns7.googledomains.com, ns8.googledomains.com

Answer: ns5.googledomains.com
2001:4860:4802:32::a, 216.239.32.10

Answer: ns6.googledomains.com
2001:4860:4802:34::a, 216.239.34.10

Answer: ns7.googledomains.com
2001:4860:4802:36::a, 216.239.36.10

Answer: ns8.googledomains.com
2001:4860:4802:38::a, 216.239.38.10
3
ns-cloud-e2.googledomains.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns5.googledomains.com, ns6.googledomains.com, ns7.googledomains.com, ns8.googledomains.com

Answer: ns5.googledomains.com
2001:4860:4802:32::a, 216.239.32.10

Answer: ns6.googledomains.com
2001:4860:4802:34::a, 216.239.34.10

Answer: ns7.googledomains.com
2001:4860:4802:36::a, 216.239.36.10

Answer: ns8.googledomains.com
2001:4860:4802:38::a, 216.239.38.10
4
ns-cloud-e3.googledomains.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns5.googledomains.com, ns6.googledomains.com, ns7.googledomains.com, ns8.googledomains.com

Answer: ns5.googledomains.com
2001:4860:4802:32::a, 216.239.32.10

Answer: ns6.googledomains.com
2001:4860:4802:34::a, 216.239.34.10

Answer: ns7.googledomains.com
2001:4860:4802:36::a, 216.239.36.10

Answer: ns8.googledomains.com
2001:4860:4802:38::a, 216.239.38.10
5
ns-cloud-e4.googledomains.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns5.googledomains.com, ns6.googledomains.com, ns7.googledomains.com, ns8.googledomains.com

Answer: ns5.googledomains.com
2001:4860:4802:32::a, 216.239.32.10

Answer: ns6.googledomains.com
2001:4860:4802:34::a, 216.239.34.10

Answer: ns7.googledomains.com
2001:4860:4802:36::a, 216.239.36.10

Answer: ns8.googledomains.com
2001:4860:4802:38::a, 216.239.38.10
6
ns-cloud-e1.googledomains.com: 216.239.32.110
A
ns5.googledomains.com (2001:4860:4802:32::a)
7
ns-cloud-e1.googledomains.com: 2001:4860:4802:32::6e
AAAA
ns5.googledomains.com (2001:4860:4802:32::a)
8
ns-cloud-e2.googledomains.com: 216.239.34.110
A
ns5.googledomains.com (2001:4860:4802:32::a)
9
ns-cloud-e2.googledomains.com: 2001:4860:4802:34::6e
AAAA
ns5.googledomains.com (2001:4860:4802:32::a)
10
ns-cloud-e3.googledomains.com: 216.239.36.110
A
ns5.googledomains.com (2001:4860:4802:32::a)
11
ns-cloud-e3.googledomains.com: 2001:4860:4802:36::6e
AAAA
ns5.googledomains.com (2001:4860:4802:32::a)
12
ns-cloud-e4.googledomains.com: 216.239.38.110
A
ns5.googledomains.com (2001:4860:4802:32::a)
13
ns-cloud-e4.googledomains.com: 2001:4860:4802:38::6e
AAAA
ns5.googledomains.com (2001:4860:4802:32::a)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
jdfbi.jdfvms.com
0

no CAA entry found
1
0
jdfvms.com
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
jdfvms.com

ok
1
0
jdfbi.jdfvms.com

ok
1
0
_acme-challenge.jdfbi.jdfvms.com

Name Error - The domain name does not exist
1
0
_acme-challenge.jdfbi.jdfvms.com.jdfvms.com

Name Error - The domain name does not exist
1
0
_acme-challenge.jdfbi.jdfvms.com.jdfbi.jdfvms.com

Name Error - The domain name does not exist
1
0


15. Portchecks

Domain or IPPortDescriptionResultAnswer
jdfbi.jdfvms.com
21
FTP



jdfbi.jdfvms.com
21
FTP



jdfbi.jdfvms.com
22
SSH
open
SSH-2.0-OpenSSH_8.1

jdfbi.jdfvms.com
22
SSH
open
SSH-2.0-OpenSSH_8.1

jdfbi.jdfvms.com
25
SMTP



jdfbi.jdfvms.com
25
SMTP



jdfbi.jdfvms.com
53
DNS



jdfbi.jdfvms.com
53
DNS



jdfbi.jdfvms.com
110
POP3



jdfbi.jdfvms.com
110
POP3



jdfbi.jdfvms.com
143
IMAP



jdfbi.jdfvms.com
143
IMAP



jdfbi.jdfvms.com
465
SMTP (encrypted)



jdfbi.jdfvms.com
465
SMTP (encrypted)



jdfbi.jdfvms.com
587
SMTP (encrypted, submission)



jdfbi.jdfvms.com
587
SMTP (encrypted, submission)



jdfbi.jdfvms.com
993
IMAP (encrypted)



jdfbi.jdfvms.com
993
IMAP (encrypted)



jdfbi.jdfvms.com
995
POP3 (encrypted)



jdfbi.jdfvms.com
995
POP3 (encrypted)



jdfbi.jdfvms.com
1433
MS SQL



jdfbi.jdfvms.com
1433
MS SQL



jdfbi.jdfvms.com
2082
cPanel (http)



jdfbi.jdfvms.com
2082
cPanel (http)



jdfbi.jdfvms.com
2083
cPanel (https)



jdfbi.jdfvms.com
2083
cPanel (https)



jdfbi.jdfvms.com
2086
WHM (http)



jdfbi.jdfvms.com
2086
WHM (http)



jdfbi.jdfvms.com
2087
WHM (https)



jdfbi.jdfvms.com
2087
WHM (https)



jdfbi.jdfvms.com
2089
cPanel Licensing



jdfbi.jdfvms.com
2089
cPanel Licensing



jdfbi.jdfvms.com
2095
cPanel Webmail (http)



jdfbi.jdfvms.com
2095
cPanel Webmail (http)



jdfbi.jdfvms.com
2096
cPanel Webmail (https)



jdfbi.jdfvms.com
2096
cPanel Webmail (https)



jdfbi.jdfvms.com
2222
DirectAdmin (http)



jdfbi.jdfvms.com
2222
DirectAdmin (http)



jdfbi.jdfvms.com
2222
DirectAdmin (https)



jdfbi.jdfvms.com
2222
DirectAdmin (https)



jdfbi.jdfvms.com
3306
mySql



jdfbi.jdfvms.com
3306
mySql



jdfbi.jdfvms.com
5224
Plesk Licensing



jdfbi.jdfvms.com
5224
Plesk Licensing



jdfbi.jdfvms.com
5432
PostgreSQL



jdfbi.jdfvms.com
5432
PostgreSQL



jdfbi.jdfvms.com
8080
Ookla Speedtest (http)
open
http://jdfbi.jdfvms.com:8080/
Http-Status: 200

jdfbi.jdfvms.com
8080
Ookla Speedtest (http)
open
http://jdfbi.jdfvms.com:8080/
Http-Status: 200

jdfbi.jdfvms.com
8080
Ookla Speedtest (https)
open
https://jdfbi.jdfvms.com:8080/
Http-Status: -4
SendFailure - The underlying connection was closed: An unexpected error occurred on a send.

jdfbi.jdfvms.com
8080
Ookla Speedtest (https)
open
https://jdfbi.jdfvms.com:8080/
Http-Status: -4
SendFailure - The underlying connection was closed: An unexpected error occurred on a send.

jdfbi.jdfvms.com
8083
VestaCP http



jdfbi.jdfvms.com
8083
VestaCP http



jdfbi.jdfvms.com
8083
VestaCP https



jdfbi.jdfvms.com
8083
VestaCP https



jdfbi.jdfvms.com
8443
Plesk Administration (https)



jdfbi.jdfvms.com
8443
Plesk Administration (https)



jdfbi.jdfvms.com
8447
Plesk Installer + Updates



jdfbi.jdfvms.com
8447
Plesk Installer + Updates



jdfbi.jdfvms.com
8880
Plesk Administration (http)



jdfbi.jdfvms.com
8880
Plesk Administration (http)



jdfbi.jdfvms.com
10000
Webmin (http)



jdfbi.jdfvms.com
10000
Webmin (http)



jdfbi.jdfvms.com
10000
Webmin (https)



jdfbi.jdfvms.com
10000
Webmin (https)



35.210.23.244
21
FTP



35.210.23.244
21
FTP



35.210.23.244
22
SSH
open
SSH-2.0-OpenSSH_8.1

35.210.23.244
22
SSH
open
SSH-2.0-OpenSSH_8.1

35.210.23.244
25
SMTP



35.210.23.244
25
SMTP



35.210.23.244
53
DNS



35.210.23.244
53
DNS



35.210.23.244
110
POP3



35.210.23.244
110
POP3



35.210.23.244
143
IMAP



35.210.23.244
143
IMAP



35.210.23.244
465
SMTP (encrypted)



35.210.23.244
465
SMTP (encrypted)



35.210.23.244
587
SMTP (encrypted, submission)



35.210.23.244
587
SMTP (encrypted, submission)



35.210.23.244
993
IMAP (encrypted)



35.210.23.244
993
IMAP (encrypted)



35.210.23.244
995
POP3 (encrypted)



35.210.23.244
995
POP3 (encrypted)



35.210.23.244
1433
MS SQL



35.210.23.244
1433
MS SQL



35.210.23.244
2082
cPanel (http)



35.210.23.244
2082
cPanel (http)



35.210.23.244
2083
cPanel (https)



35.210.23.244
2083
cPanel (https)



35.210.23.244
2086
WHM (http)



35.210.23.244
2086
WHM (http)



35.210.23.244
2087
WHM (https)



35.210.23.244
2087
WHM (https)



35.210.23.244
2089
cPanel Licensing



35.210.23.244
2089
cPanel Licensing



35.210.23.244
2095
cPanel Webmail (http)



35.210.23.244
2095
cPanel Webmail (http)



35.210.23.244
2096
cPanel Webmail (https)



35.210.23.244
2096
cPanel Webmail (https)



35.210.23.244
2222
DirectAdmin (http)



35.210.23.244
2222
DirectAdmin (http)



35.210.23.244
2222
DirectAdmin (https)



35.210.23.244
2222
DirectAdmin (https)



35.210.23.244
3306
mySql



35.210.23.244
3306
mySql



35.210.23.244
5224
Plesk Licensing



35.210.23.244
5224
Plesk Licensing



35.210.23.244
5432
PostgreSQL



35.210.23.244
5432
PostgreSQL



35.210.23.244
8080
Ookla Speedtest (http)
open
http://35.210.23.244:8080/
Http-Status: 200

35.210.23.244
8080
Ookla Speedtest (http)
open
http://35.210.23.244:8080/
Http-Status: 200

35.210.23.244
8080
Ookla Speedtest (https)
open
https://35.210.23.244:8080/
Http-Status: -4
SendFailure - The underlying connection was closed: An unexpected error occurred on a send.

35.210.23.244
8080
Ookla Speedtest (https)
open
https://35.210.23.244:8080/
Http-Status: -4
SendFailure - The underlying connection was closed: An unexpected error occurred on a send.

35.210.23.244
8083
VestaCP http



35.210.23.244
8083
VestaCP http



35.210.23.244
8083
VestaCP https



35.210.23.244
8083
VestaCP https



35.210.23.244
8443
Plesk Administration (https)



35.210.23.244
8443
Plesk Administration (https)



35.210.23.244
8447
Plesk Installer + Updates



35.210.23.244
8447
Plesk Installer + Updates



35.210.23.244
8880
Plesk Administration (http)



35.210.23.244
8880
Plesk Administration (http)



35.210.23.244
10000
Webmin (http)



35.210.23.244
10000
Webmin (http)



35.210.23.244
10000
Webmin (https)



35.210.23.244
10000
Webmin (https)





Permalink: https://check-your-website.server-daten.de/?i=c491ebde-aa42-471a-8b2a-fd8547761e61


Last Result: https://check-your-website.server-daten.de/?q=jdfbi.jdfvms.com - 2021-04-07 19:47:17


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

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