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



V

Connect failure - perhaps firewall

Checked:
04.05.2021 14:11:04


Older results


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
analytics.vyaparapp.in
A
34.218.141.62
Portland/Oregon/United States (US) - Amazon.com, Inc.
Hostname: ec2-34-218-141-62.us-west-2.compute.amazonaws.com
yes
1
0

AAAA

yes


www.analytics.vyaparapp.in
A

yes
1
0

AAAA

yes


*.vyaparapp.in
A

yes



AAAA

yes



CNAME

yes


*.analytics.vyaparapp.in
A

yes



AAAA

yes



CNAME

yes



2. DNSSEC

Zone (*)DNSSEC - Informations

Zone: (root)
(root)
1 DS RR published



DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest 4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=



Status: Valid because published



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 14631, 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.05.2021, 00:00:00 +, Signature-Inception: 01.05.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: in
in
2 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 54739, DigestType 1 and Digest K1ykVaDmV2n/nfnnXsQO4ewc3Kk=



DS with Algorithm 8, KeyTag 54739, DigestType 2 and Digest nxIs/WYErm3toP4J8nvjQKMY8Gr6wRcUpzQJ1DE2Ryw=



1 RRSIG RR to validate DS RR found



RRSIG-Owner in., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 17.05.2021, 05:00:00 +, Signature-Inception: 04.05.2021, 04: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 54739, Flags 257 (SEP = Secure Entry Point)



Public Key with Algorithm 8, KeyTag 65169, Flags 256



2 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner in., Algorithm: 8, 1 Labels, original TTL: 900 sec, Signature-expiration: 28.05.2021, 05:03:02 +, Signature-Inception: 28.04.2021, 05:02:12 +, KeyTag 54739, Signer-Name: in



RRSIG-Owner in., Algorithm: 8, 1 Labels, original TTL: 900 sec, Signature-expiration: 28.05.2021, 05:03:02 +, Signature-Inception: 28.04.2021, 05:02:12 +, KeyTag 65169, Signer-Name: in



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



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



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 54739, DigestType 1 and Digest "K1ykVaDmV2n/nfnnXsQO4ewc3Kk=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone



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

Zone: vyaparapp.in
vyaparapp.in
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 "ddh01391ktiv4g216gk9riqujk5a4rmv" between the hashed NSEC3-owner "ddg5j2urcupgno8o30d99i61ddt8ltr6" and the hashed NextOwner "ddi96hthr0l406gqb9leuec0mg6f8nsh". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner ddg5j2urcupgno8o30d99i61ddt8ltr6.in., Algorithm: 8, 2 Labels, original TTL: 1800 sec, Signature-expiration: 29.05.2021, 12:36:08 +, Signature-Inception: 29.04.2021, 12:32:00 +, KeyTag 65169, Signer-Name: in



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "bo801o0uciino3vfr38lrljcrv2ucohi" as Owner. That's the Hash of "in" with the NextHashedOwnerName "bo9uq54vb22m3j37nr3n6grc6j4rvutv". So that domain name is the Closest Encloser of "vyaparapp.in". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner bo801o0uciino3vfr38lrljcrv2ucohi.in., Algorithm: 8, 2 Labels, original TTL: 1800 sec, Signature-expiration: 28.05.2021, 09:07:12 +, Signature-Inception: 28.04.2021, 08:31:06 +, KeyTag 65169, Signer-Name: in



0 DNSKEY RR found




Zone: analytics.vyaparapp.in
analytics.vyaparapp.in
0 DS RR in the parent zone found



0 DNSKEY RR found




Zone: www.analytics.vyaparapp.in
www.analytics.vyaparapp.in
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.analytics.vyaparapp.in
  ns-616.awsdns-13.net / 9b0e15bdc161ea053055e43a4acaca4a -

analytics.vyaparapp.in
  ns-616.awsdns-13.net / 43de7e8b25e75a931ef5210d04a3ef9a -
205.251.194.104
Seattle/Washington/United States (US) - Amazon.com


 
2600:9000:5302:6800::1
Seattle/Washington/United States (US) - Amazon.com

vyaparapp.in
  ns-1361.awsdns-42.org / 1b0dd431bbab75f1ba38c5bd87648827 -
205.251.197.81
London/England/United Kingdom (GB) - Amazon.com


 
2600:9000:5305:5100::1
Seattle/Washington/United States (US) - Amazon.com


  ns-1934.awsdns-49.co.uk / 2d37bee1a8c88e66d4b862b2e0698c32 -
205.251.199.142
Seattle/Washington/United States (US) - Amazon.com


 
2600:9000:5307:8e00::1
Seattle/Washington/United States (US) - Amazon.com


  ns-34.awsdns-04.com / f00369383ea087fd1c9f86e4234ee62b -
205.251.192.34
Paris/Île-de-France/France (FR) - Amazon.com


 
2600:9000:5300:2200::1
Seattle/Washington/United States (US) - Amazon.com


  ns-616.awsdns-13.net / 9b0e15bdc161ea053055e43a4acaca4a -
205.251.194.104
Seattle/Washington/United States (US) - Amazon.com


 
2600:9000:5302:6800::1
Seattle/Washington/United States (US) - Amazon.com

in
  ns1.neustar.in


  ns1.registry.in / dns1.frpar1


  ns2.registry.in / dns1.defra1


  ns3.registry.in / dns1.defra1


  ns4.registry.in / dns1.frpar1


  ns5.registry.in / TLD_Host1.Frankfurt_Node1


  ns6.registry.in / TLD_Host1.Frankfurt_Node1


4. SOA-Entries


Domain:in
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


Domain:in
Zone-Name:in
Primary:ns1.neustar.in
Mail:hostmaster.neustar.in
Serial:1620130016
Refresh:1800
Retry:300
Expire:1814400
TTL:1800
num Entries:6


Domain:vyaparapp.in
Zone-Name:vyaparapp.in
Primary:ns-616.awsdns-13.net
Mail:awsdns-hostmaster.amazon.com
Serial:1
Refresh:7200
Retry:900
Expire:1209600
TTL:86400
num Entries:8


Domain:analytics.vyaparapp.in
Zone-Name:vyaparapp.in
Primary:ns-616.awsdns-13.net
Mail:awsdns-hostmaster.amazon.com
Serial:1
Refresh:7200
Retry:900
Expire:1209600
TTL:86400
num Entries:2


Domain:www.analytics.vyaparapp.in
Zone-Name:vyaparapp.in
Primary:ns-616.awsdns-13.net
Mail:awsdns-hostmaster.amazon.com
Serial:1
Refresh:7200
Retry:900
Expire:1209600
TTL:86400
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://analytics.vyaparapp.in/
34.218.141.62
302
http://analytics.vyaparapp.in/login?next=http%3A%2F%2Fanalytics.vyaparapp.in%2F
Html is minified: 100.33 %
0.337
D
Server: nginx/1.9.10
Date: Tue, 04 May 2021 12:12:03 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 307
Connection: close
Location: http://analytics.vyaparapp.in/login?next=http%3A%2F%2Fanalytics.vyaparapp.in%2F
X-Frame-Options: deny
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
X-Download-Options: noopen
Content-Security-Policy: default-src 'self'; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-eval'; font-src 'self' data:; img-src 'self' http: https: data: blob:; object-src 'none'; frame-ancestors 'none'; frame-src redash.io;
X-Content-Security-Policy: default-src 'self'; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-eval'; font-src 'self' data:; img-src 'self' http: https: data: blob:; object-src 'none'; frame-ancestors 'none'; frame-src redash.io;
Referrer-Policy: strict-origin-when-cross-origin

• http://analytics.vyaparapp.in/login?next=http%3A%2F%2Fanalytics.vyaparapp.in%2F
GZip used - 761 / 1777 - 57.18 %
200

Html is minified: 119.42 %
0.400
H
Server: nginx/1.9.10
Date: Tue, 04 May 2021 12:12:07 GMT
Content-Type: text/html; charset=utf-8
Transfer-Encoding: chunked
Connection: close
X-Frame-Options: deny
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
X-Download-Options: noopen
Content-Security-Policy: default-src 'self'; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-eval'; font-src 'self' data:; img-src 'self' http: https: data: blob:; object-src 'none'; frame-ancestors 'none'; frame-src redash.io;
X-Content-Security-Policy: default-src 'self'; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-eval'; font-src 'self' data:; img-src 'self' http: https: data: blob:; object-src 'none'; frame-ancestors 'none'; frame-src redash.io;
Referrer-Policy: strict-origin-when-cross-origin
Content-Encoding: gzip

• https://analytics.vyaparapp.in/
34.218.141.62
-2

1.570
V
ConnectFailure - Unable to connect to the remote server

• http://analytics.vyaparapp.in/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
34.218.141.62
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
302
http://analytics.vyaparapp.in/login?next=http%3A%2F%2Fanalytics.vyaparapp.in%2F.well-known%2Facme-challenge%2Fcheck-your-website-dot-server-daten-dot-de
Html is minified: 100.22 %
0.370
D
Visible Content: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> Redirecting... Redirecting... You should be redirected automatically to target URL: /login?next=http%3A%2F%2Fanalytics.vyaparapp.in%2F.well-known%2Facme-challenge%2Fcheck-your-website-dot-server-daten-dot-de . If not click the link.
Server: nginx/1.9.10
Date: Tue, 04 May 2021 12:12:05 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 453
Connection: close
Location: http://analytics.vyaparapp.in/login?next=http%3A%2F%2Fanalytics.vyaparapp.in%2F.well-known%2Facme-challenge%2Fcheck-your-website-dot-server-daten-dot-de
X-Frame-Options: deny
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
X-Download-Options: noopen
Content-Security-Policy: default-src 'self'; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-eval'; font-src 'self' data:; img-src 'self' http: https: data: blob:; object-src 'none'; frame-ancestors 'none'; frame-src redash.io;
X-Content-Security-Policy: default-src 'self'; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-eval'; font-src 'self' data:; img-src 'self' http: https: data: blob:; object-src 'none'; frame-ancestors 'none'; frame-src redash.io;
Referrer-Policy: strict-origin-when-cross-origin

• http://analytics.vyaparapp.in/login?next=http%3A%2F%2Fanalytics.vyaparapp.in%2F.well-known%2Facme-challenge%2Fcheck-your-website-dot-server-daten-dot-de
GZip used - 761 / 1777 - 57.18 %
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
200

Html is minified: 119.42 %
0.374

Visible Content: Login to Redash Email Password Log In I forgot my password
Server: nginx/1.9.10
Date: Tue, 04 May 2021 12:12:08 GMT
Content-Type: text/html; charset=utf-8
Transfer-Encoding: chunked
Connection: close
X-Frame-Options: deny
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
X-Download-Options: noopen
Content-Security-Policy: default-src 'self'; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-eval'; font-src 'self' data:; img-src 'self' http: https: data: blob:; object-src 'none'; frame-ancestors 'none'; frame-src redash.io;
X-Content-Security-Policy: default-src 'self'; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-eval'; font-src 'self' data:; img-src 'self' http: https: data: blob:; object-src 'none'; frame-ancestors 'none'; frame-src redash.io;
Referrer-Policy: strict-origin-when-cross-origin
Content-Encoding: gzip

• https://34.218.141.62/
34.218.141.62
-2

1.543
V
ConnectFailure - Unable to connect to the remote server

7. Comments


1. General Results, most used to calculate the result

Aname "analytics.vyaparapp.in" is subdomain, public suffix is ".in", top-level-domain is ".in", top-level-domain-type is "country-code", Country is India, tld-manager is "National Internet Exchange of India", num .in-domains preloaded: 574 (complete: 151507)
Agood: All ip addresses are public addresses
Warning: Only one ip address found: analytics.vyaparapp.in 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: analytics.vyaparapp.in has no ipv6 address.
Agood: No asked Authoritative Name Server had a timeout
Agood - only one version with Http-Status 200
AGood: No cookie sent via http.
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
AGood: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
Dhttp://analytics.vyaparapp.in/ 34.218.141.62
302
http://analytics.vyaparapp.in/login?next=http%3A%2F%2Fanalytics.vyaparapp.in%2F
Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
Dhttp://analytics.vyaparapp.in/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 34.218.141.62
302
http://analytics.vyaparapp.in/login?next=http%3A%2F%2Fanalytics.vyaparapp.in%2F.well-known%2Facme-challenge%2Fcheck-your-website-dot-server-daten-dot-de
Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
Hfatal error: No https - result with http-status 200, no encryption
HFatal error: http result with http-status 200, no encryption. Add a redirect http ⇒ https, so every connection is secure. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop.
Ihttp://analytics.vyaparapp.in/login?next=http%3A%2F%2Fanalytics.vyaparapp.in%2F.well-known%2Facme-challenge%2Fcheck-your-website-dot-server-daten-dot-de
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.
Vhttps://analytics.vyaparapp.in/ 34.218.141.62
-2

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

connect failure - perhaps firewall
Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain analytics.vyaparapp.in, 1 ip addresses.

2. DNS- and NameServer - Checks

AInfo:: 16 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers.
AInfo:: 16 Queries complete, 15 with IPv6, 1 with IPv4.
Warning: Only some DNS Queries done via ipv6. IPv6 is the future, so the name servers of your name servers should have ipv6 addresses.
Ok (4 - 8):: An average of 4.0 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 4 different Name Servers found: ns-1361.awsdns-42.org, ns-1934.awsdns-49.co.uk, ns-34.awsdns-04.com, ns-616.awsdns-13.net, 4 Name Servers included in Delegation: ns-1361.awsdns-42.org, ns-1934.awsdns-49.co.uk, ns-34.awsdns-04.com, ns-616.awsdns-13.net, 4 Name Servers included in 1 Zone definitions: ns-1361.awsdns-42.org, ns-1934.awsdns-49.co.uk, ns-34.awsdns-04.com, ns-616.awsdns-13.net, 1 Name Servers listed in SOA.Primary: ns-616.awsdns-13.net.
AGood: Only one SOA.Primary Name Server found.: ns-616.awsdns-13.net.
AGood: SOA.Primary Name Server included in the delegation set.: ns-616.awsdns-13.net.
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-1361.awsdns-42.org, ns-1934.awsdns-49.co.uk, ns-34.awsdns-04.com, ns-616.awsdns-13.net
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
AGood: Name servers with different Top Level Domains / Public Suffix List entries found: 4 Name Servers, 4 Top Level Domains: org, net, com, co.uk
AGood: Name Servers with different domain names found.: 4 different Domains found
AGood: Name servers with different Country locations found: 4 Name Servers, 3 Countries: FR, GB, US
AInfo: Ipv4-Subnet-list: 4 Name Servers, 1 different subnets (first Byte): 205., 1 different subnets (first two Bytes): 205.251., 4 different subnets (first three Bytes): 205.251.192., 205.251.194., 205.251.197., 205.251.199.
AGood: Name Server IPv4-addresses from different subnet found:
AInfo: IPv6-Subnet-list: 4 Name Servers with IPv6, 1 different subnets (first block): 2600:, 1 different subnets (first two blocks): 2600:9000:, 4 different subnets (first three blocks): 2600:9000:5300:, 2600:9000:5302:, 2600:9000:5305:, 2600:9000:5307:, 4 different subnets (first four blocks): 2600:9000:5300:2200:, 2600:9000:5302:6800:, 2600:9000:5305:5100:, 2600:9000:5307:8e00:
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
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: ns1.neustar.in: 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
Agood: CAA entries found, creating certificate is limited: amazon.com is allowed to create certificates
Agood: CAA entries found, creating certificate is limited: amazonaws.com is allowed to create certificates
Agood: CAA entries found, creating certificate is limited: amazontrust.com is allowed to create certificates
Agood: CAA entries found, creating certificate is limited: awstrust.com is allowed to create certificates
Agood: CAA entries found, creating certificate is limited: godaddy.com is allowed to create certificates

3. Content- and Performance-critical Checks

http://analytics.vyaparapp.in/login?next=http%3A%2F%2Fanalytics.vyaparapp.in%2F.well-known%2Facme-challenge%2Fcheck-your-website-dot-server-daten-dot-de
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.
Warning: CSS / JavaScript files with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 1 external CSS / JavaScript files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 0 with Cache-Control max-age too short (minimum 7 days), 0 with Cache-Control long enough, 1 complete.
Warning: Images with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 1 image files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 0 with Cache-Control max-age too short (minimum 7 days), 0 with Cache-Control long enough, 1 complete.
AGood: All checked attribute values are enclosed in quotation marks (" or ').
Wrong: img-elements without alt-attribute or empty alt-attribute found. The alt-attribute ("alternative") is required and should describe the img. So Screenreader and search engines are able to use these informations.: 1 img-elements without alt-attribute, 0 img-elements with empty alt-attribute found.
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: 89667 milliseconds, 89.667 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" > 2019 are listed

Issuerlast 7 daysactivenum Certs
CN=Amazon, OU=Server CA 1B, O=Amazon, C=US
0
2
2

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
4220863141
leaf cert
CN=Amazon, OU=Server CA 1B, O=Amazon, C=US
2021-03-05 23:00:00
2022-04-04 21:59:59
*.vyaparapp.in, vyaparapp.in
2 entries


4151643601
precert
CN=Amazon, OU=Server CA 1B, O=Amazon, C=US
2021-03-01 23:00:00
2022-03-31 21:59:59
*.vyaparapp.in
1 entries



11. Html-Content - Entries

Summary

Subresource Integrity (SRI)
DomainnameHtmlElementrel/property∑ size∑ problems∑ int.∑ ext.∑ Origin poss.∑ SRI ParseErrors∑ SRI valid∑ SRI missing
http://analytics.vyaparapp.in/login?next=http%3A%2F%2Fanalytics.vyaparapp.in%2F.well-known%2Facme-challenge%2Fcheck-your-website-dot-server-daten-dot-de
a

2

0


0
0
0


form

1

0


0
0
0


img

1

1
1
0
0
0
0


link
stylesheet
1

1
1
0
0
0
0


link
other
3

3
3
0
0
0
0


meta
other
2

0


0
0
0

Details

DomainnameHtml-Elementname/equiv/ property/relhref/src/contentHttpStatusmsgStatus
http://analytics.vyaparapp.in/login?next=http%3A%2F%2Fanalytics.vyaparapp.in%2F.well-known%2Facme-challenge%2Fcheck-your-website-dot-server-daten-dot-de

a

/


1
ok








a

/forgot


1
ok








form
post



1
ok








img
src
/static/images/redash_icon_small.png
-2
ConnectFailure - Unable to connect to the remote server
1
ConnectFailure - Unable to connect to the remote server
no alt-Attribute








link
icon
/static/images/favicon-16x16.png
-2
ConnectFailure - Unable to connect to the remote server
1
ConnectFailure - Unable to connect to the remote server








link
icon
/static/images/favicon-32x32.png
-2
ConnectFailure - Unable to connect to the remote server
1
ConnectFailure - Unable to connect to the remote server








link
icon
/static/images/favicon-96x96.png
-2
ConnectFailure - Unable to connect to the remote server
1
ConnectFailure - Unable to connect to the remote server








link
stylesheet
/static/server.7733150becd78d2f3015.css
-2
ConnectFailure - Unable to connect to the remote server
1
ConnectFailure - Unable to connect to the remote server








meta
X-UA-Compatible
IE=edge


1
ok








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


1
ok








12. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: ns-1361.awsdns-42.org, ns-1934.awsdns-49.co.uk, ns-34.awsdns-04.com, ns-616.awsdns-13.net

QNr.DomainTypeNS used
1
org
NS
d.root-servers.net (2001:500:2d::d)

Answer: a0.org.afilias-nst.info, a2.org.afilias-nst.info, b0.org.afilias-nst.org, b2.org.afilias-nst.org, c0.org.afilias-nst.info, d0.org.afilias-nst.org
2
ns-1361.awsdns-42.org
NS
a0.org.afilias-nst.info (2001:500:e::1)

Answer: g-ns-1069.awsdns-42.org, g-ns-1642.awsdns-42.org, g-ns-170.awsdns-42.org, g-ns-748.awsdns-42.org

Answer: g-ns-1069.awsdns-42.org
205.251.196.45, 2600:9000:5304:2d00::1

Answer: g-ns-1642.awsdns-42.org
205.251.198.106, 2600:9000:5306:6a00::1

Answer: g-ns-170.awsdns-42.org
205.251.192.170, 2600:9000:5300:aa00::1

Answer: g-ns-748.awsdns-42.org
205.251.194.236, 2600:9000:5302:ec00::1
3
uk
NS
l.root-servers.net (2001:500:9f::42)

Answer: dns1.nic.uk, dns2.nic.uk, dns3.nic.uk, dns4.nic.uk, nsa.nic.uk, nsb.nic.uk, nsc.nic.uk, nsd.nic.uk
4
ns-1934.awsdns-49.co.uk
NS
dns1.nic.uk (2a01:618:400::1)

Answer: g-ns-1524.awsdns-49.co.uk, g-ns-1845.awsdns-49.co.uk, g-ns-369.awsdns-49.co.uk, g-ns-945.awsdns-49.co.uk

Answer: g-ns-1524.awsdns-49.co.uk
205.251.197.244, 2600:9000:5305:f400::1

Answer: g-ns-1845.awsdns-49.co.uk
205.251.199.53, 2600:9000:5307:3500::1

Answer: g-ns-369.awsdns-49.co.uk
205.251.193.113, 2600:9000:5301:7100::1

Answer: g-ns-945.awsdns-49.co.uk
205.251.195.177, 2600:9000:5303:b100::1
5
com
NS
k.root-servers.net (2001:7fd::1)

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
6
ns-34.awsdns-04.com
NS
e.gtld-servers.net (2001:502:1ca1::30)

Answer: g-ns-1156.awsdns-04.com, g-ns-1732.awsdns-04.com, g-ns-5.awsdns-04.com, g-ns-580.awsdns-04.com

Answer: g-ns-1156.awsdns-04.com
205.251.196.132, 2600:9000:5304:8400::1

Answer: g-ns-1732.awsdns-04.com
205.251.198.196, 2600:9000:5306:c400::1

Answer: g-ns-5.awsdns-04.com
205.251.192.5, 2600:9000:5300:500::1

Answer: g-ns-580.awsdns-04.com
205.251.194.68, 2600:9000:5302:4400::1
7
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
8
ns-616.awsdns-13.net
NS
b.gtld-servers.net (192.33.14.30)

Answer: g-ns-1357.awsdns-13.net, g-ns-1933.awsdns-13.net, g-ns-462.awsdns-13.net, g-ns-783.awsdns-13.net

Answer: g-ns-1357.awsdns-13.net
205.251.197.77, 2600:9000:5305:4d00::1

Answer: g-ns-1933.awsdns-13.net
205.251.199.141, 2600:9000:5307:8d00::1

Answer: g-ns-462.awsdns-13.net
205.251.193.206, 2600:9000:5301:ce00::1

Answer: g-ns-783.awsdns-13.net
205.251.195.15, 2600:9000:5303:f00::1
9
ns-1361.awsdns-42.org: 205.251.197.81
A
g-ns-1069.awsdns-42.org (2600:9000:5304:2d00::1)
10
ns-1361.awsdns-42.org: 2600:9000:5305:5100::1
AAAA
g-ns-1069.awsdns-42.org (2600:9000:5304:2d00::1)
11
ns-1934.awsdns-49.co.uk: 205.251.199.142
A
g-ns-1524.awsdns-49.co.uk (2600:9000:5305:f400::1)
12
ns-1934.awsdns-49.co.uk: 2600:9000:5307:8e00::1
AAAA
g-ns-1524.awsdns-49.co.uk (2600:9000:5305:f400::1)
13
ns-34.awsdns-04.com: 205.251.192.34
A
g-ns-1156.awsdns-04.com (2600:9000:5304:8400::1)
14
ns-34.awsdns-04.com: 2600:9000:5300:2200::1
AAAA
g-ns-1156.awsdns-04.com (2600:9000:5304:8400::1)
15
ns-616.awsdns-13.net: 205.251.194.104
A
g-ns-1357.awsdns-13.net (2600:9000:5305:4d00::1)
16
ns-616.awsdns-13.net: 2600:9000:5302:6800::1
AAAA
g-ns-1357.awsdns-13.net (2600:9000:5305:4d00::1)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.analytics.vyaparapp.in
5
issue
amazon.com
1
0

5
issue
amazonaws.com
1
0

5
issue
amazontrust.com
1
0

5
issue
awstrust.com
1
0

5
issue
godaddy.com
1
0
analytics.vyaparapp.in
0

no CAA entry found
1
0
vyaparapp.in
5
issue
amazon.com
1
0

5
issue
amazonaws.com
1
0

5
issue
amazontrust.com
1
0

5
issue
awstrust.com
1
0

5
issue
godaddy.com
1
0
in
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
vyaparapp.in

ok
1
0
analytics.vyaparapp.in

ok
1
0
www.analytics.vyaparapp.in

ok
1
0
_acme-challenge.analytics.vyaparapp.in

missing entry or wrong length
1
0
_acme-challenge.www.analytics.vyaparapp.in

missing entry or wrong length
1
0
_acme-challenge.analytics.vyaparapp.in.vyaparapp.in

perhaps wrong
1
0
_acme-challenge.analytics.vyaparapp.in.analytics.vyaparapp.in

perhaps wrong
1
0
_acme-challenge.www.analytics.vyaparapp.in.analytics.vyaparapp.in

perhaps wrong
1
0
_acme-challenge.www.analytics.vyaparapp.in.www.analytics.vyaparapp.in

perhaps wrong
1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=c3003b85-a0dd-4ca1-9014-a8397a1b9396


Last Result: https://check-your-website.server-daten.de/?q=analytics.vyaparapp.in - 2021-05-04 14:11: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=analytics.vyaparapp.in" target="_blank">Check this Site: analytics.vyaparapp.in</a>