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




W

wrong Web-Response

Checked:
09.01.2022 17:24:04


Older results


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
johnlush.net
A
34.102.136.180
Kansas City/Missouri/United States (US) - Google LLC
Hostname: 180.136.102.34.bc.googleusercontent.com
yes
2
0

AAAA

yes


www.johnlush.net
CNAME
johnlush.net
yes
1
0

A
34.102.136.180
Kansas City/Missouri/United States (US) - Google LLC
Hostname: 180.136.102.34.bc.googleusercontent.com
yes


*.johnlush.net
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 9799, Flags 256



Public Key with Algorithm 8, KeyTag 14748, Flags 256



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



1 RRSIG RR to validate DNSKEY RR found



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



DS with Algorithm 8, KeyTag 35886, DigestType 2 and Digest eGKyf19Rbr4ZaARE1M5edimBkxhCxGXwAjZAHYvZc+4=



1 RRSIG RR to validate DS RR found



RRSIG-Owner net., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 22.01.2022, 05:00:00 +, Signature-Inception: 09.01.2022, 04:00:00 +, KeyTag 9799, Signer-Name: (root)



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



2 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 40649, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner net., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 19.01.2022, 17:28:30 +, Signature-Inception: 04.01.2022, 17:23:30 +, KeyTag 35886, Signer-Name: net



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



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

Zone: johnlush.net
johnlush.net
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 "d83j680r2ou2h59viier4dikmbpa1b4a" between the hashed NSEC3-owner "d83iroa4inbttkod4i8ovjn9muk4vbet" and the hashed NextOwner "d83jhrai24dnn5lvsaq5pvo89tet68jk". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner d83iroa4inbttkod4i8ovjn9muk4vbet.net., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 14.01.2022, 06:46:26 +, Signature-Inception: 07.01.2022, 05:36:26 +, KeyTag 40649, Signer-Name: net



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "a1rt98bs5qgc9nfi51s9hci47uljg6jh" as Owner. That's the Hash of "net" with the NextHashedOwnerName "a1rtlnpgulogn7b9a62shje1u3ttp8dr". So that domain name is the Closest Encloser of "johnlush.net". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner a1rt98bs5qgc9nfi51s9hci47uljg6jh.net., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 15.01.2022, 06:45:35 +, Signature-Inception: 08.01.2022, 05:35:35 +, KeyTag 40649, Signer-Name: net



0 DNSKEY RR found




Zone: www.johnlush.net
www.johnlush.net
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
johnlush.net
  ns43.domaincontrol.com / hex:0D 70 31 31
97.74.101.22
Scottsdale/Arizona/United States (US) - Host Europe GmbH


 
2603:5:2152::16
Chicago/Illinois/United States (US) - Host Europe GmbH


  ns44.domaincontrol.com / hex:0D 70 30 36
173.201.69.22
Scottsdale/Arizona/United States (US) - Host Europe GmbH


 
2603:5:2252::16
New York/United States (US) - Host Europe GmbH

net
  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


4. SOA-Entries


Domain:net
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:13


Domain:johnlush.net
Zone-Name:johnlush.net
Primary:ns43.domaincontrol.com
Mail:dns.jomax.net
Serial:2020070900
Refresh:28800
Retry:7200
Expire:604800
TTL:600
num Entries:4


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://johnlush.net/
34.102.136.180 No GZip used - 1551 / 2548 - 60.87 % possible
200

Html is minified: 273.98 %
0.147

small visible content (num chars: 0)
Server: openresty
Date: Sun, 09 Jan 2022 16:24:29 GMT
Content-Type: text/html
Content-Length: 2548
Last-Modified: Mon, 15 Nov 2021 12:49:48 GMT
ETag: "6192576c-9f4"
X-Adblock-Key: MFwwDQYJKoZIhvcNAQEBBQADSwAwSAJBAJRmzcpTevQqkWn6dJuX/N/Hxl7YxbOwy8+73ijqYSQEN+WGxrruAKtZtliWC86+ewQ0msW1W8psOFL/b00zWqsCAwEAAQ_bnYheS5PuS4YK+u/CSRLjQU04WmrU3Hx5qOgU55gfR8CW5PQneqnhz8IxNQ6AXr4kvS1N9uER2ORzwXgO2VwYA
Set-Cookie: system=PW;Path=/;Max-Age=86400;,caf_ipaddr=85.215.2.227;Path=/;Max-Age=86400;,country=DE;Path=/;Max-Age=86400;,city="";Path=/;Max-Age=86400;,traffic_target=gd;Path=/;Max-Age=86400;
Accept-Ranges: bytes
Via: 1.1 google
Connection: close

• http://www.johnlush.net/
34.102.136.180 No GZip used - 1551 / 2548 - 60.87 % possible
200

Html is minified: 273.98 %
0.144

small visible content (num chars: 0)
Server: openresty
Date: Sun, 09 Jan 2022 16:24:29 GMT
Content-Type: text/html
Content-Length: 2548
Last-Modified: Mon, 15 Nov 2021 12:49:49 GMT
ETag: "6192576d-9f4"
X-Adblock-Key: MFwwDQYJKoZIhvcNAQEBBQADSwAwSAJBAJRmzcpTevQqkWn6dJuX/N/Hxl7YxbOwy8+73ijqYSQEN+WGxrruAKtZtliWC86+ewQ0msW1W8psOFL/b00zWqsCAwEAAQ_KjCDUzMKV+pTtx3hblVBvbR57PxsH7PnoA5akdfHnddH0hGs2YV4JqAvm3nIuohsbvZ+BOJl6rs4E4yda2Ht0Q
Set-Cookie: system=PW;Path=/;Max-Age=86400;,caf_ipaddr=85.215.2.227;Path=/;Max-Age=86400;,country=DE;Path=/;Max-Age=86400;,city="";Path=/;Max-Age=86400;,traffic_target=gd;Path=/;Max-Age=86400;
Accept-Ranges: bytes
Via: 1.1 google
Connection: close

• https://johnlush.net/
34.102.136.180
-4

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

• https://www.johnlush.net/
34.102.136.180
-4

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

• http://johnlush.net:443/
34.102.136.180
-8

0.276
A
ConnectionClosed - The underlying connection was closed: The connection was closed unexpectedly.
Visible Content:

• http://www.johnlush.net:443/
34.102.136.180
-8

0.187
A
ConnectionClosed - The underlying connection was closed: The connection was closed unexpectedly.
Visible Content:

• http://johnlush.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
34.102.136.180 No GZip used - 1551 / 2548 - 60.87 % possible
Inline-JavaScript (∑/total): 4/1559 Inline-CSS (∑/total): 1/27
200

Html is minified: 273.98 %
0.156

Visible Content:
Info: Html-Content with meta and/or script, may be a problem creating a Letsencrypt certificate using http-01 validation
Server: openresty
Date: Sun, 09 Jan 2022 16:24:30 GMT
Content-Type: text/html
Content-Length: 2548
Last-Modified: Mon, 15 Nov 2021 12:49:49 GMT
ETag: "6192576d-9f4"
X-Adblock-Key: MFwwDQYJKoZIhvcNAQEBBQADSwAwSAJBAJRmzcpTevQqkWn6dJuX/N/Hxl7YxbOwy8+73ijqYSQEN+WGxrruAKtZtliWC86+ewQ0msW1W8psOFL/b00zWqsCAwEAAQ_AKp1ZhxNsrIcsYA43X+f1eZ3YpuZMtGv62vrdTYmWBYJFQEz5/O+iorwEzOgbW+flgnKQHxtOoFQ4r41sa501w
Set-Cookie: system=PW;Path=/;Max-Age=86400;,caf_ipaddr=85.215.2.227;Path=/;Max-Age=86400;,country=DE;Path=/;Max-Age=86400;,city="";Path=/;Max-Age=86400;,traffic_target=gd;Path=/;Max-Age=86400;
Accept-Ranges: bytes
Via: 1.1 google
Connection: close

• http://www.johnlush.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
34.102.136.180 No GZip used - 1551 / 2548 - 60.87 % possible
Inline-JavaScript (∑/total): 4/1559 Inline-CSS (∑/total): 1/27
200

Html is minified: 273.98 %
0.150

Visible Content:
Info: Html-Content with meta and/or script, may be a problem creating a Letsencrypt certificate using http-01 validation
Server: openresty
Date: Sun, 09 Jan 2022 16:24:30 GMT
Content-Type: text/html
Content-Length: 2548
Last-Modified: Wed, 10 Nov 2021 15:37:25 GMT
ETag: "618be735-9f4"
X-Adblock-Key: MFwwDQYJKoZIhvcNAQEBBQADSwAwSAJBAJRmzcpTevQqkWn6dJuX/N/Hxl7YxbOwy8+73ijqYSQEN+WGxrruAKtZtliWC86+ewQ0msW1W8psOFL/b00zWqsCAwEAAQ_Fdu8RmoEIXjsIuy5zQNhIQ2XEhNk9fO5hKVtEQLwzUiDXfW8LMbYkj0RiI0HbNtFwPQrdXc3Zv6QwTHn7dGT4g
Set-Cookie: system=PW;Path=/;Max-Age=86400;,caf_ipaddr=85.215.2.227;Path=/;Max-Age=86400;,country=DE;Path=/;Max-Age=86400;,city="";Path=/;Max-Age=86400;,traffic_target=gd;Path=/;Max-Age=86400;
Accept-Ranges: bytes
Via: 1.1 google
Connection: close

• https://34.102.136.180/
34.102.136.180
-4

0.213
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 "johnlush.net" is domain, public suffix is ".net", top-level-domain is ".net", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .net-domains preloaded: 6852 (complete: 168171)
AGood: All ip addresses are public addresses
Warning: Only one ip address found: johnlush.net has only one ip address.
Warning: Only one ip address found: www.johnlush.net 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: johnlush.net has no ipv6 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: www.johnlush.net has no ipv6 address.
AGood: No asked Authoritative Name Server had a timeout
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: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):0 complete Content-Type - header (4 urls)
http://johnlush.net/ 34.102.136.180


Url with incomplete Content-Type - header - missing charset
http://www.johnlush.net/ 34.102.136.180


Url with incomplete Content-Type - header - missing charset
http://johnlush.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.102.136.180


Url with incomplete Content-Type - header - missing charset
http://www.johnlush.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.102.136.180


Url with incomplete Content-Type - header - missing charset
http://johnlush.net/ 34.102.136.180
200
system=PW;Path=/;Max-Age=86400;
Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
http://johnlush.net/ 34.102.136.180
200
caf_ipaddr=85.215.2.227;Path=/;Max-Age=86400;
Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
http://johnlush.net/ 34.102.136.180
200
country=DE;Path=/;Max-Age=86400;
Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
http://johnlush.net/ 34.102.136.180
200
city="";Path=/;Max-Age=86400;
Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
http://johnlush.net/ 34.102.136.180
200
traffic_target=gd;Path=/;Max-Age=86400;
Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
http://www.johnlush.net/ 34.102.136.180
200
system=PW;Path=/;Max-Age=86400;
Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
http://www.johnlush.net/ 34.102.136.180
200
caf_ipaddr=85.215.2.227;Path=/;Max-Age=86400;
Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
http://www.johnlush.net/ 34.102.136.180
200
country=DE;Path=/;Max-Age=86400;
Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
http://www.johnlush.net/ 34.102.136.180
200
city="";Path=/;Max-Age=86400;
Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
http://www.johnlush.net/ 34.102.136.180
200
traffic_target=gd;Path=/;Max-Age=86400;
Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
http://johnlush.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.102.136.180
200
system=PW;Path=/;Max-Age=86400;
Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
http://johnlush.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.102.136.180
200
caf_ipaddr=85.215.2.227;Path=/;Max-Age=86400;
Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
http://johnlush.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.102.136.180
200
country=DE;Path=/;Max-Age=86400;
Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
http://johnlush.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.102.136.180
200
city="";Path=/;Max-Age=86400;
Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
http://johnlush.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.102.136.180
200
traffic_target=gd;Path=/;Max-Age=86400;
Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
http://www.johnlush.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.102.136.180
200
system=PW;Path=/;Max-Age=86400;
Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
http://www.johnlush.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.102.136.180
200
caf_ipaddr=85.215.2.227;Path=/;Max-Age=86400;
Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
http://www.johnlush.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.102.136.180
200
country=DE;Path=/;Max-Age=86400;
Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
http://www.johnlush.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.102.136.180
200
city="";Path=/;Max-Age=86400;
Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
http://www.johnlush.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.102.136.180
200
traffic_target=gd;Path=/;Max-Age=86400;
Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative.
Bhttp://johnlush.net/ 34.102.136.180
200
system=PW;Path=/;Max-Age=86400;
Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
Bhttp://johnlush.net/ 34.102.136.180
200
caf_ipaddr=85.215.2.227;Path=/;Max-Age=86400;
Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
Bhttp://johnlush.net/ 34.102.136.180
200
country=DE;Path=/;Max-Age=86400;
Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
Bhttp://johnlush.net/ 34.102.136.180
200
city="";Path=/;Max-Age=86400;
Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
Bhttp://johnlush.net/ 34.102.136.180
200
traffic_target=gd;Path=/;Max-Age=86400;
Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
Bhttp://www.johnlush.net/ 34.102.136.180
200
system=PW;Path=/;Max-Age=86400;
Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
Bhttp://www.johnlush.net/ 34.102.136.180
200
caf_ipaddr=85.215.2.227;Path=/;Max-Age=86400;
Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
Bhttp://www.johnlush.net/ 34.102.136.180
200
country=DE;Path=/;Max-Age=86400;
Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
Bhttp://www.johnlush.net/ 34.102.136.180
200
city="";Path=/;Max-Age=86400;
Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
Bhttp://www.johnlush.net/ 34.102.136.180
200
traffic_target=gd;Path=/;Max-Age=86400;
Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
Bhttp://johnlush.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.102.136.180
200
system=PW;Path=/;Max-Age=86400;
Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
Bhttp://johnlush.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.102.136.180
200
caf_ipaddr=85.215.2.227;Path=/;Max-Age=86400;
Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
Bhttp://johnlush.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.102.136.180
200
country=DE;Path=/;Max-Age=86400;
Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
Bhttp://johnlush.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.102.136.180
200
city="";Path=/;Max-Age=86400;
Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
Bhttp://johnlush.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.102.136.180
200
traffic_target=gd;Path=/;Max-Age=86400;
Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
Bhttp://www.johnlush.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.102.136.180
200
system=PW;Path=/;Max-Age=86400;
Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
Bhttp://www.johnlush.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.102.136.180
200
caf_ipaddr=85.215.2.227;Path=/;Max-Age=86400;
Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
Bhttp://www.johnlush.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.102.136.180
200
country=DE;Path=/;Max-Age=86400;
Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
Bhttp://www.johnlush.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.102.136.180
200
city="";Path=/;Max-Age=86400;
Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
Bhttp://www.johnlush.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.102.136.180
200
traffic_target=gd;Path=/;Max-Age=86400;
Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value.
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.
Ihttp://johnlush.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.102.136.180
200

Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Not used to calculate the result because it's a http - check. But listed so you should fix it.
Ihttp://www.johnlush.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.102.136.180
200

Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Not used to calculate the result because it's a http - check. But listed so you should fix it.
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 johnlush.net, 1 ip addresses.
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 www.johnlush.net, 1 ip addresses.

2. Header-Checks


3. DNS- and NameServer - Checks

AInfo:: 27 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
AInfo:: 27 Queries complete, 27 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
Bad (greater 8):: An average of 13.5 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 2 different Name Servers found: ns43.domaincontrol.com, ns44.domaincontrol.com, 2 Name Servers included in Delegation: ns43.domaincontrol.com, ns44.domaincontrol.com, 2 Name Servers included in 1 Zone definitions: ns43.domaincontrol.com, ns44.domaincontrol.com, 1 Name Servers listed in SOA.Primary: ns43.domaincontrol.com.
AGood: Only one SOA.Primary Name Server found.: ns43.domaincontrol.com.
AGood: SOA.Primary Name Server included in the delegation set.: ns43.domaincontrol.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: ns43.domaincontrol.com, ns44.domaincontrol.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: domaincontrol.com
Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: US
AInfo: Ipv4-Subnet-list: 2 Name Servers, 2 different subnets (first Byte): 173., 97., 2 different subnets (first two Bytes): 173.201., 97.74., 2 different subnets (first three Bytes): 173.201.69., 97.74.101.
AExcellent: Every Name Server IPv4-address starts with an unique Byte.
AInfo: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2603:, 1 different subnets (first two blocks): 2603:0005:, 2 different subnets (first three blocks): 2603:0005:2152:, 2603:0005:2252:, 2 different subnets (first four blocks): 2603:0005:2152:0000:, 2603:0005:2252:0000:
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 4 good Nameserver
AGood: Nameserver supports Echo Capitalization: 4 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 4 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 4 good Nameserver
Nameserver doesn't pass all EDNS-Checks: a.gtld-servers.net: 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: b.gtld-servers.net: 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: c.gtld-servers.net: 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: d.gtld-servers.net: 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: e.gtld-servers.net: 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: f.gtld-servers.net: 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: g.gtld-servers.net: 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: h.gtld-servers.net: 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: i.gtld-servers.net: 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: j.gtld-servers.net: 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: k.gtld-servers.net: 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: l.gtld-servers.net: 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: m.gtld-servers.net: 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

http://johnlush.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.102.136.180
200

Warning: Not existing ACME-file, but Server sends 200, not 404 or redirect. May be a problem creating a Letsencrypt certificate. Checking /.well-known/acme-challenge/random-filename - a http status 404 - Not Found - is expected. If your server sends content and a http status 200, the validation file (87 bytes, token, dot and the hash of the public part of the account key) may be invisible, so Letsencrypt can't validate your domain. If it is an application that sends this content, perhaps create an exception, so /.well-known/acme-challenge sends raw files. Or create a redirect to another domain and / or port 443, but your Letsencrypt client must support such a solution. Certbot: Use webroot as authenticator - https://certbot.eff.org/docs/using.html Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
http://www.johnlush.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.102.136.180
200

Warning: Not existing ACME-file, but Server sends 200, not 404 or redirect. May be a problem creating a Letsencrypt certificate. Checking /.well-known/acme-challenge/random-filename - a http status 404 - Not Found - is expected. If your server sends content and a http status 200, the validation file (87 bytes, token, dot and the hash of the public part of the account key) may be invisible, so Letsencrypt can't validate your domain. If it is an application that sends this content, perhaps create an exception, so /.well-known/acme-challenge sends raw files. Or create a redirect to another domain and / or port 443, but your Letsencrypt client must support such a solution. Certbot: Use webroot as authenticator - https://certbot.eff.org/docs/using.html Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
http://johnlush.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.102.136.180
200

Critical: Some script Elements (type text/javascript) with a src-Attribute don't have a defer / async - Attribute. Loading and executing these JavaScripts blocks parsing and rendering the Html-Output. That's bad if your site is large or the connection is slow / mobile usage. Use "async" if the js file has only functions (so nothing is executed after parsing the file) or is independend. Use "defer" if the order of the scripts is important. All "defer" scripts are executed before the DOMContentLoaded event is fired. Check https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script to see some details.: 3 script elements without defer/async.
http://www.johnlush.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.102.136.180
200

Critical: Some script Elements (type text/javascript) with a src-Attribute don't have a defer / async - Attribute. Loading and executing these JavaScripts blocks parsing and rendering the Html-Output. That's bad if your site is large or the connection is slow / mobile usage. Use "async" if the js file has only functions (so nothing is executed after parsing the file) or is independend. Use "defer" if the order of the scripts is important. All "defer" scripts are executed before the DOMContentLoaded event is fired. Check https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script to see some details.: 3 script elements without defer/async.
Warning: CSS / JavaScript found without GZip support. Send these ressources with GZip. 2 external CSS / JavaScript files without GZip found - 4 with GZip, 6 complete
Warning: CSS / JavaScript files with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 0 external CSS / JavaScript files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 2 with Cache-Control max-age too short (minimum 7 days), 4 with Cache-Control long enough, 6 complete.
AGood: All checked attribute values are enclosed in quotation marks (" or ').
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: 58277 milliseconds, 58.277 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

Summary

Subresource Integrity (SRI)
DomainnameHtmlElementrel/property∑ size∑ problems∑ int.∑ ext.∑ Origin poss.∑ SRI ParseErrors∑ SRI valid∑ SRI missing
http://johnlush.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
34.102.136.180
a

1

0


0
0
0


link
other
1

1


0
0
0


meta
other
2

0


0
0
0


script

3
314,244 Bytes
0
0
3
2
0
0
-2
http://www.johnlush.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
34.102.136.180
a

1

0


0
0
0


link
other
1

1


0
0
0


meta
other
2

0


0
0
0


script

3
314,215 Bytes
0
0
3
2
0
0
-2

Details

DomainnameHtml-Elementname/equiv/ property/relhref/src/contentHttpStatusmsgStatus
http://johnlush.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
34.102.136.180
a

https://www.enable-javascript.com/


1
ok








link
shortcut icon
data:image/x-icon;,
Image:


1
No <svg> - element found. Must be the root element of your svg image., Unknown mime type. Must start with "data:image/svg+xml" or another valid image mime type., The svg xmlns (svg Namespace declaration) must be "http://www.w3.org/2000/svg". Not https, not with additional white spaces.









meta
content-type
text/html;charset=utf-8


1
ok








meta
viewport
width=device-width,initial-scale=1


1
ok








script
src
https://img1.wsimg.com/parking-lander/static/js/2.a0b81bff.chunk.js
200

1
ok
Missing defer / async attribute. application/javascript, missing X-Content-Type-Options nosniff

Cache-Control: max-age=31536000 - with long duration found.
GZip: 123245/392667 Bytes




Server-Header Access-Control-Allow-Origin: *
Cross-Origin Resource Sharing (CORS) supported

missing crossorigin=anonymous|use-credentials and integrity - attribute, possible hash-values:

sha256-ZsJOHSAF/R00aCbUcg5TPHAlIXk+emU9fCULfPFS5YE=
sha384-V0OaBnfnza84o9MbYmWbwPtPftMCzellvbZKYTNbFv48Zlamgqa3jkzwr4TEIuyk
sha512-okLUVba4RXK4T2jKoBnRe2CqB/SqYuugRJ60sEa6OsIfbWbEWEPGofsLb1rr9Ie6z4f1uEyvZW/wPtXamm4IxQ==

<script src="https://img1.wsimg.com/parking-lander/static/js/2.a0b81bff.chunk.js" crossorigin="anonymous" integrity="sha256-ZsJOHSAF/R00aCbUcg5TPHAlIXk+emU9fCULfPFS5YE=" />




script
src
https://img1.wsimg.com/parking-lander/static/js/main.31e47cc9.chunk.js
200

1
ok
Missing defer / async attribute. application/javascript, missing X-Content-Type-Options nosniff

Cache-Control: max-age=31536000 - with long duration found.
GZip: 49710/244545 Bytes




Server-Header Access-Control-Allow-Origin: *
Cross-Origin Resource Sharing (CORS) supported

missing crossorigin=anonymous|use-credentials and integrity - attribute, possible hash-values:

sha256-QPzIFlIME+jMSJzbI2OBARgrmUF+DGdN5RRtwjqm+e4=
sha384-c9Pf3uWPxFmH82kO9M3M3/fDOB6+kD6Yd9MrUmdx3ZE6N6aeGU+TVQmNcmZh/1rr
sha512-CCL4LCBuUSzYVBGnvmmqX9f+thTFP7QXhh9j3xf1Tveg4YQXdy4ksGT35HFqMl+VtXYiZrIpgJ4c56P6pORfNA==

<script src="https://img1.wsimg.com/parking-lander/static/js/main.31e47cc9.chunk.js" crossorigin="anonymous" integrity="sha256-QPzIFlIME+jMSJzbI2OBARgrmUF+DGdN5RRtwjqm+e4=" />




script
src
https://www.google.com/adsense/domains/caf.js
200

1
ok
Missing defer / async attribute. text/javascript; charset=UTF-8, X-Content-Type-Options nosniff found

Cache-Control: private, max-age=3600 - max-age too short.
GZip required: 141289 Bytes




Server-Header Access-Control-Allow-Origin: not found
Cross-Origin Resource Sharing (CORS) not supported


http://www.johnlush.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
34.102.136.180
a

https://www.enable-javascript.com/


1
ok








link
shortcut icon
data:image/x-icon;,
Image:


1
No <svg> - element found. Must be the root element of your svg image., Unknown mime type. Must start with "data:image/svg+xml" or another valid image mime type., The svg xmlns (svg Namespace declaration) must be "http://www.w3.org/2000/svg". Not https, not with additional white spaces.









meta
content-type
text/html;charset=utf-8


1
ok








meta
viewport
width=device-width,initial-scale=1


1
ok








script
src
https://img1.wsimg.com/parking-lander/static/js/2.a0b81bff.chunk.js
200

1
ok
Missing defer / async attribute. application/javascript, missing X-Content-Type-Options nosniff

Cache-Control: max-age=31536000 - with long duration found.
GZip: 123245/392667 Bytes




Server-Header Access-Control-Allow-Origin: *
Cross-Origin Resource Sharing (CORS) supported

missing crossorigin=anonymous|use-credentials and integrity - attribute, possible hash-values:

sha256-ZsJOHSAF/R00aCbUcg5TPHAlIXk+emU9fCULfPFS5YE=
sha384-V0OaBnfnza84o9MbYmWbwPtPftMCzellvbZKYTNbFv48Zlamgqa3jkzwr4TEIuyk
sha512-okLUVba4RXK4T2jKoBnRe2CqB/SqYuugRJ60sEa6OsIfbWbEWEPGofsLb1rr9Ie6z4f1uEyvZW/wPtXamm4IxQ==

<script src="https://img1.wsimg.com/parking-lander/static/js/2.a0b81bff.chunk.js" crossorigin="anonymous" integrity="sha256-ZsJOHSAF/R00aCbUcg5TPHAlIXk+emU9fCULfPFS5YE=" />




script
src
https://img1.wsimg.com/parking-lander/static/js/main.31e47cc9.chunk.js
200

1
ok
Missing defer / async attribute. application/javascript, missing X-Content-Type-Options nosniff

Cache-Control: max-age=31536000 - with long duration found.
GZip: 49710/244545 Bytes




Server-Header Access-Control-Allow-Origin: *
Cross-Origin Resource Sharing (CORS) supported

missing crossorigin=anonymous|use-credentials and integrity - attribute, possible hash-values:

sha256-QPzIFlIME+jMSJzbI2OBARgrmUF+DGdN5RRtwjqm+e4=
sha384-c9Pf3uWPxFmH82kO9M3M3/fDOB6+kD6Yd9MrUmdx3ZE6N6aeGU+TVQmNcmZh/1rr
sha512-CCL4LCBuUSzYVBGnvmmqX9f+thTFP7QXhh9j3xf1Tveg4YQXdy4ksGT35HFqMl+VtXYiZrIpgJ4c56P6pORfNA==

<script src="https://img1.wsimg.com/parking-lander/static/js/main.31e47cc9.chunk.js" crossorigin="anonymous" integrity="sha256-QPzIFlIME+jMSJzbI2OBARgrmUF+DGdN5RRtwjqm+e4=" />




script
src
https://www.google.com/adsense/domains/caf.js
200

1
ok
Missing defer / async attribute. text/javascript; charset=UTF-8, X-Content-Type-Options nosniff found

Cache-Control: private, max-age=3600 - max-age too short.
GZip required: 141260 Bytes




Server-Header Access-Control-Allow-Origin: not found
Cross-Origin Resource Sharing (CORS) not supported



12. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: ns43.domaincontrol.com, ns44.domaincontrol.com

QNr.DomainTypeNS used
1
com
NS
a.root-servers.net (2001:503:ba3e::2:30)

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

Answer: a1-245.akam.net, a11-64.akam.net, a20-65.akam.net, a6-66.akam.net, a8-67.akam.net, a9-67.akam.net, ans01.domaincontrol.com, ans02.domaincontrol.com

Answer: ans01.domaincontrol.com
2603:5:2111::23, 97.74.97.35

Answer: ans02.domaincontrol.com
173.201.65.35, 2603:5:2211::23
3
ns44.domaincontrol.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-245.akam.net, a11-64.akam.net, a20-65.akam.net, a6-66.akam.net, a8-67.akam.net, a9-67.akam.net, ans01.domaincontrol.com, ans02.domaincontrol.com

Answer: ans02.domaincontrol.com
173.201.65.35, 2603:5:2211::23

Answer: ans01.domaincontrol.com
2603:5:2111::23, 97.74.97.35
4
net
NS
a.root-servers.net (2001:503:ba3e::2:30)

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
5
a1-245.akam.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a13-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a3-67.akam.net, a4-67.akam.net, a5-67.akam.net, a6-67.akam.net, a7-67.akam.net, a9-67.akam.net

Answer: a9-67.akam.net
184.85.248.67

Answer: a7-67.akam.net
23.61.199.67

Answer: a5-67.akam.net
95.100.168.67

Answer: a3-67.akam.net
96.7.49.67

Answer: a28-67.akam.net
95.100.173.67

Answer: a22-67.akam.net
23.211.61.67

Answer: a18-67.akam.net
95.101.36.67

Answer: a13-67.akam.net
2.22.230.67

Answer: a12-67.akam.net
184.26.160.67

Answer: a11-67.akam.net
84.53.139.67

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43
6
a11-64.akam.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a13-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a3-67.akam.net, a4-67.akam.net, a5-67.akam.net, a6-67.akam.net, a7-67.akam.net, a9-67.akam.net

Answer: a12-67.akam.net
184.26.160.67

Answer: a11-67.akam.net
84.53.139.67

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a13-67.akam.net
2.22.230.67

Answer: a18-67.akam.net
95.101.36.67

Answer: a22-67.akam.net
23.211.61.67

Answer: a28-67.akam.net
95.100.173.67

Answer: a3-67.akam.net
96.7.49.67

Answer: a5-67.akam.net
95.100.168.67

Answer: a7-67.akam.net
23.61.199.67

Answer: a9-67.akam.net
184.85.248.67
7
a20-65.akam.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a13-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a3-67.akam.net, a4-67.akam.net, a5-67.akam.net, a6-67.akam.net, a7-67.akam.net, a9-67.akam.net

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
84.53.139.67

Answer: a12-67.akam.net
184.26.160.67

Answer: a13-67.akam.net
2.22.230.67

Answer: a18-67.akam.net
95.101.36.67

Answer: a22-67.akam.net
23.211.61.67

Answer: a28-67.akam.net
95.100.173.67

Answer: a3-67.akam.net
96.7.49.67

Answer: a5-67.akam.net
95.100.168.67

Answer: a7-67.akam.net
23.61.199.67

Answer: a9-67.akam.net
184.85.248.67
8
a6-66.akam.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a13-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a3-67.akam.net, a4-67.akam.net, a5-67.akam.net, a6-67.akam.net, a7-67.akam.net, a9-67.akam.net

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
84.53.139.67

Answer: a12-67.akam.net
184.26.160.67

Answer: a13-67.akam.net
2.22.230.67

Answer: a18-67.akam.net
95.101.36.67

Answer: a22-67.akam.net
23.211.61.67

Answer: a28-67.akam.net
95.100.173.67

Answer: a3-67.akam.net
96.7.49.67

Answer: a5-67.akam.net
95.100.168.67

Answer: a7-67.akam.net
23.61.199.67

Answer: a9-67.akam.net
184.85.248.67
9
a8-67.akam.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a13-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a3-67.akam.net, a4-67.akam.net, a5-67.akam.net, a6-67.akam.net, a7-67.akam.net, a9-67.akam.net

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
84.53.139.67

Answer: a12-67.akam.net
184.26.160.67

Answer: a13-67.akam.net
2.22.230.67

Answer: a18-67.akam.net
95.101.36.67

Answer: a22-67.akam.net
23.211.61.67

Answer: a28-67.akam.net
95.100.173.67

Answer: a3-67.akam.net
96.7.49.67

Answer: a5-67.akam.net
95.100.168.67

Answer: a7-67.akam.net
23.61.199.67

Answer: a9-67.akam.net
184.85.248.67
10
a4-67.akam.net: 72.246.46.67
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
84.53.139.67

Answer: a12-67.akam.net
184.26.160.67

Answer: a13-67.akam.net
2.22.230.67

Answer: a18-67.akam.net
95.101.36.67

Answer: a22-67.akam.net
23.211.61.67

Answer: a28-67.akam.net
95.100.173.67

Answer: a3-67.akam.net
96.7.49.67

Answer: a5-67.akam.net
95.100.168.67

Answer: a7-67.akam.net
23.61.199.67

Answer: a9-67.akam.net
184.85.248.67
11
a6-67.akam.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a13-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a3-67.akam.net, a4-67.akam.net, a5-67.akam.net, a6-67.akam.net, a7-67.akam.net, a9-67.akam.net

Answer: a1-67.akam.net
193.108.91.67, 2600:1401:2::43

Answer: a11-67.akam.net
84.53.139.67

Answer: a12-67.akam.net
184.26.160.67

Answer: a13-67.akam.net
2.22.230.67

Answer: a18-67.akam.net
95.101.36.67

Answer: a22-67.akam.net
23.211.61.67

Answer: a28-67.akam.net
95.100.173.67

Answer: a3-67.akam.net
96.7.49.67

Answer: a4-67.akam.net
72.246.46.67

Answer: a5-67.akam.net
95.100.168.67

Answer: a7-67.akam.net
23.61.199.67

Answer: a9-67.akam.net
184.85.248.67
12
a1-245.akam.net: 193.108.91.245
A
a1-67.akam.net (2600:1401:2::43)
13
a1-245.akam.net: 2600:1401:2::f5
AAAA
a1-67.akam.net (2600:1401:2::43)
14
a11-64.akam.net: 84.53.139.64
A
a1-67.akam.net (2600:1401:2::43)
15
a11-64.akam.net: 2600:1480:1::40
AAAA
a1-67.akam.net (2600:1401:2::43)
16
a20-65.akam.net: 95.100.175.65
A
a1-67.akam.net (2600:1401:2::43)
17
a20-65.akam.net: 2a02:26f0:67::41
AAAA
a1-67.akam.net (2600:1401:2::43)
18
a6-66.akam.net: 23.211.133.66
A
a1-67.akam.net (2600:1401:2::43)
19
a6-66.akam.net: 2600:1401:1::42
AAAA
a1-67.akam.net (2600:1401:2::43)
20
a8-67.akam.net: 2.16.40.67
A
a1-67.akam.net (2600:1401:2::43)
21
a8-67.akam.net: 2600:1403:a::43
AAAA
a1-67.akam.net (2600:1401:2::43)
22
a6-67.akam.net: 23.211.133.67
A
a1-67.akam.net (2600:1401:2::43)
23
a6-67.akam.net: 2600:1401:1::43
AAAA
a1-67.akam.net (2600:1401:2::43)
24
ns43.domaincontrol.com: 97.74.101.22
A
a1-245.akam.net (2600:1401:2::f5)
25
ns43.domaincontrol.com: 2603:5:2152::16
AAAA
a1-245.akam.net (2600:1401:2::f5)
26
ns44.domaincontrol.com: 173.201.69.22
A
a1-245.akam.net (2600:1401:2::f5)
27
ns44.domaincontrol.com: 2603:5:2252::16
AAAA
a1-245.akam.net (2600:1401:2::f5)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.johnlush.net



1
0
johnlush.net
0

no CAA entry found
1
0
net
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
johnlush.net
ppe-7e9f04714afb0195b817
ok
1
0
johnlush.net
v=spf1 a:dispatch-us.ppe-hosted.com ~all
ok
1
0
www.johnlush.net
ppe-7e9f04714afb0195b817
ok
1
0
www.johnlush.net
v=spf1 a:dispatch-us.ppe-hosted.com ~all
ok
1
0
_acme-challenge.johnlush.net

Name Error - The domain name does not exist
1
0
_acme-challenge.www.johnlush.net

Name Error - The domain name does not exist
1
0
_acme-challenge.johnlush.net.johnlush.net

Name Error - The domain name does not exist
1
0
_acme-challenge.www.johnlush.net.johnlush.net

Name Error - The domain name does not exist
1
0
_acme-challenge.www.johnlush.net.www.johnlush.net

Name Error - The domain name does not exist
1
0


15. DomainService - Entries

No DomainServiceEntries entries found



16. Cipher Suites

No Ciphers found


17. Portchecks

DomainIPPortDescriptionResultAnswer
johnlush.net
34.102.136.180
21
FTP



johnlush.net
34.102.136.180
21
FTP



johnlush.net
34.102.136.180
22
SSH



johnlush.net
34.102.136.180
22
SSH



johnlush.net
34.102.136.180
25
SMTP



johnlush.net
34.102.136.180
25
SMTP



johnlush.net
34.102.136.180
53
DNS



johnlush.net
34.102.136.180
53
DNS



johnlush.net
34.102.136.180
110
POP3



johnlush.net
34.102.136.180
110
POP3



johnlush.net
34.102.136.180
143
IMAP



johnlush.net
34.102.136.180
143
IMAP



johnlush.net
34.102.136.180
465
SMTP (encrypted)



johnlush.net
34.102.136.180
465
SMTP (encrypted)



johnlush.net
34.102.136.180
587
SMTP (encrypted, submission)



johnlush.net
34.102.136.180
587
SMTP (encrypted, submission)



johnlush.net
34.102.136.180
993
IMAP (encrypted)



johnlush.net
34.102.136.180
993
IMAP (encrypted)



johnlush.net
34.102.136.180
995
POP3 (encrypted)



johnlush.net
34.102.136.180
995
POP3 (encrypted)



johnlush.net
34.102.136.180
1433
MS SQL



johnlush.net
34.102.136.180
1433
MS SQL



johnlush.net
34.102.136.180
2082
cPanel (http)



johnlush.net
34.102.136.180
2082
cPanel (http)



johnlush.net
34.102.136.180
2083
cPanel (https)



johnlush.net
34.102.136.180
2083
cPanel (https)



johnlush.net
34.102.136.180
2086
WHM (http)



johnlush.net
34.102.136.180
2086
WHM (http)



johnlush.net
34.102.136.180
2087
WHM (https)



johnlush.net
34.102.136.180
2087
WHM (https)



johnlush.net
34.102.136.180
2089
cPanel Licensing



johnlush.net
34.102.136.180
2089
cPanel Licensing



johnlush.net
34.102.136.180
2095
cPanel Webmail (http)



johnlush.net
34.102.136.180
2095
cPanel Webmail (http)



johnlush.net
34.102.136.180
2096
cPanel Webmail (https)



johnlush.net
34.102.136.180
2096
cPanel Webmail (https)



johnlush.net
34.102.136.180
2222
DirectAdmin (http)



johnlush.net
34.102.136.180
2222
DirectAdmin (http)



johnlush.net
34.102.136.180
2222
DirectAdmin (https)



johnlush.net
34.102.136.180
2222
DirectAdmin (https)



johnlush.net
34.102.136.180
3306
mySql



johnlush.net
34.102.136.180
3306
mySql



johnlush.net
34.102.136.180
5224
Plesk Licensing



johnlush.net
34.102.136.180
5224
Plesk Licensing



johnlush.net
34.102.136.180
5432
PostgreSQL



johnlush.net
34.102.136.180
5432
PostgreSQL



johnlush.net
34.102.136.180
8080
Ookla Speedtest (http)



johnlush.net
34.102.136.180
8080
Ookla Speedtest (http)



johnlush.net
34.102.136.180
8080
Ookla Speedtest (https)



johnlush.net
34.102.136.180
8080
Ookla Speedtest (https)



johnlush.net
34.102.136.180
8083
VestaCP http



johnlush.net
34.102.136.180
8083
VestaCP http



johnlush.net
34.102.136.180
8083
VestaCP https



johnlush.net
34.102.136.180
8083
VestaCP https



johnlush.net
34.102.136.180
8443
Plesk Administration (https)



johnlush.net
34.102.136.180
8443
Plesk Administration (https)



johnlush.net
34.102.136.180
8447
Plesk Installer + Updates



johnlush.net
34.102.136.180
8447
Plesk Installer + Updates



johnlush.net
34.102.136.180
8880
Plesk Administration (http)



johnlush.net
34.102.136.180
8880
Plesk Administration (http)



johnlush.net
34.102.136.180
10000
Webmin (http)



johnlush.net
34.102.136.180
10000
Webmin (http)



johnlush.net
34.102.136.180
10000
Webmin (https)



johnlush.net
34.102.136.180
10000
Webmin (https)



www.johnlush.net
34.102.136.180
21
FTP



www.johnlush.net
34.102.136.180
21
FTP



www.johnlush.net
34.102.136.180
22
SSH



www.johnlush.net
34.102.136.180
22
SSH



www.johnlush.net
34.102.136.180
25
SMTP



www.johnlush.net
34.102.136.180
25
SMTP



www.johnlush.net
34.102.136.180
53
DNS



www.johnlush.net
34.102.136.180
53
DNS



www.johnlush.net
34.102.136.180
110
POP3



www.johnlush.net
34.102.136.180
110
POP3



www.johnlush.net
34.102.136.180
143
IMAP



www.johnlush.net
34.102.136.180
143
IMAP



www.johnlush.net
34.102.136.180
465
SMTP (encrypted)



www.johnlush.net
34.102.136.180
465
SMTP (encrypted)



www.johnlush.net
34.102.136.180
587
SMTP (encrypted, submission)



www.johnlush.net
34.102.136.180
587
SMTP (encrypted, submission)



www.johnlush.net
34.102.136.180
993
IMAP (encrypted)



www.johnlush.net
34.102.136.180
993
IMAP (encrypted)



www.johnlush.net
34.102.136.180
995
POP3 (encrypted)



www.johnlush.net
34.102.136.180
995
POP3 (encrypted)



www.johnlush.net
34.102.136.180
1433
MS SQL



www.johnlush.net
34.102.136.180
1433
MS SQL



www.johnlush.net
34.102.136.180
2082
cPanel (http)



www.johnlush.net
34.102.136.180
2082
cPanel (http)



www.johnlush.net
34.102.136.180
2083
cPanel (https)



www.johnlush.net
34.102.136.180
2083
cPanel (https)



www.johnlush.net
34.102.136.180
2086
WHM (http)



www.johnlush.net
34.102.136.180
2086
WHM (http)



www.johnlush.net
34.102.136.180
2087
WHM (https)



www.johnlush.net
34.102.136.180
2087
WHM (https)



www.johnlush.net
34.102.136.180
2089
cPanel Licensing



www.johnlush.net
34.102.136.180
2089
cPanel Licensing



www.johnlush.net
34.102.136.180
2095
cPanel Webmail (http)



www.johnlush.net
34.102.136.180
2095
cPanel Webmail (http)



www.johnlush.net
34.102.136.180
2096
cPanel Webmail (https)



www.johnlush.net
34.102.136.180
2096
cPanel Webmail (https)



www.johnlush.net
34.102.136.180
2222
DirectAdmin (http)



www.johnlush.net
34.102.136.180
2222
DirectAdmin (http)



www.johnlush.net
34.102.136.180
2222
DirectAdmin (https)



www.johnlush.net
34.102.136.180
2222
DirectAdmin (https)



www.johnlush.net
34.102.136.180
3306
mySql



www.johnlush.net
34.102.136.180
3306
mySql



www.johnlush.net
34.102.136.180
5224
Plesk Licensing



www.johnlush.net
34.102.136.180
5224
Plesk Licensing



www.johnlush.net
34.102.136.180
5432
PostgreSQL



www.johnlush.net
34.102.136.180
5432
PostgreSQL



www.johnlush.net
34.102.136.180
8080
Ookla Speedtest (http)



www.johnlush.net
34.102.136.180
8080
Ookla Speedtest (http)



www.johnlush.net
34.102.136.180
8080
Ookla Speedtest (https)



www.johnlush.net
34.102.136.180
8080
Ookla Speedtest (https)



www.johnlush.net
34.102.136.180
8083
VestaCP http



www.johnlush.net
34.102.136.180
8083
VestaCP http



www.johnlush.net
34.102.136.180
8083
VestaCP https



www.johnlush.net
34.102.136.180
8083
VestaCP https



www.johnlush.net
34.102.136.180
8443
Plesk Administration (https)



www.johnlush.net
34.102.136.180
8443
Plesk Administration (https)



www.johnlush.net
34.102.136.180
8447
Plesk Installer + Updates



www.johnlush.net
34.102.136.180
8447
Plesk Installer + Updates



www.johnlush.net
34.102.136.180
8880
Plesk Administration (http)



www.johnlush.net
34.102.136.180
8880
Plesk Administration (http)



www.johnlush.net
34.102.136.180
10000
Webmin (http)



www.johnlush.net
34.102.136.180
10000
Webmin (http)



www.johnlush.net
34.102.136.180
10000
Webmin (https)



www.johnlush.net
34.102.136.180
10000
Webmin (https)





Permalink: https://check-your-website.server-daten.de/?i=27e2a140-d2cd-493f-b7ed-38abdd238fe1


Last Result: https://check-your-website.server-daten.de/?q=johnlush.net - 2022-01-09 17:24:04


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

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

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