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

...

skip EDNS-Check

skip Content-Check

check links

No trusted Certificate

Checked:
01.06.2019 10:08:31

Older results

N - 21.05.2019 08:15:12

N - 17.05.2019 13:09:14

N - 17.05.2019 12:00:06

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
askari.co.in	A	52.172.219.121 Pune/Maharashtra/IN No Hostname found	yes	1	0
	AAAA		yes
www.askari.co.in	CNAME	askari.azurewebsites.net	yes	1	0
	CNAME	waws-prod-pn1-003.sip.azurewebsites.windows.net	yes
www.askari.co.in	A	52.172.219.121 Pune/Maharashtra/IN No Hostname found	no
askari.azurewebsites.net	A	52.172.219.121 Pune/Maharashtra/IN No Hostname found	no

2. DNSSEC

Zone (*)	DNSSEC - Informations

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


	• Status: Valid because published


	2 DNSKEY RR found


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


	Public Key with Algorithm 8, KeyTag 25266, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 21.06.2019, 00:00:00 +, Signature-Inception: 31.05.2019, 00:00:00 +, KeyTag 20326, Signer-Name: (root)


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


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

Zone: in
in	4 DS RR in the parent zone found


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner in., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 14.06.2019, 05:00:00 +, Signature-Inception: 01.06.2019, 04:00:00 +, KeyTag 25266, Signer-Name: (root)


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


	4 DNSKEY RR found


	Public Key with Algorithm 7, KeyTag 9182, Flags 256


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


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


	Public Key with Algorithm 7, KeyTag 51365, Flags 256


	2 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner in., Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 28.06.2019, 21:48:37 +, Signature-Inception: 29.05.2019, 21:12:48 +, KeyTag 9182, Signer-Name: in


	RRSIG-Owner in., Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 28.06.2019, 21:48:37 +, Signature-Inception: 29.05.2019, 21:12:48 +, KeyTag 35373, Signer-Name: in


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


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


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


	• Status: Valid Chain of trust. Parent-DS with Algorithm 7, KeyTag 35373, DigestType 2 and Digest "pfH+s8fGKEPCh7844M+o0zod+P4rf9hxv9z/jqCzVNo=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: co.in
co.in	6 DS RR in the parent zone found


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner co.in., Algorithm: 7, 2 Labels, original TTL: 86400 sec, Signature-expiration: 28.06.2019, 20:58:48 +, Signature-Inception: 29.05.2019, 20:56:15 +, KeyTag 9182, Signer-Name: in


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


	4 DNSKEY RR found


	Public Key with Algorithm 7, KeyTag 8093, Flags 256


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


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


	Public Key with Algorithm 7, KeyTag 61037, Flags 256


	2 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner co.in., Algorithm: 7, 2 Labels, original TTL: 900 sec, Signature-expiration: 28.06.2019, 21:06:46 +, Signature-Inception: 29.05.2019, 20:38:26 +, KeyTag 8093, Signer-Name: co.in


	RRSIG-Owner co.in., Algorithm: 7, 2 Labels, original TTL: 900 sec, Signature-expiration: 28.06.2019, 21:06:46 +, Signature-Inception: 29.05.2019, 20:38:26 +, KeyTag 20220, Signer-Name: co.in


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


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


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


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

Zone: askari.co.in
askari.co.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 "ag7h9jibfhpsdutp63q7ih0l6q7h4afl" between the hashed NSEC3-owner "afhup1808380p0vd8ese6h5o6vrn752r" and the hashed NextOwner "aggu93280vsta1i210tn7cme7fu2ej0n". So the parent zone confirmes the not-existence of a DS RR. Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner afhup1808380p0vd8ese6h5o6vrn752r.co.in., Algorithm: 7, 3 Labels, original TTL: 1800 sec, Signature-expiration: 25.06.2019, 06:08:53 +, Signature-Inception: 26.05.2019, 05:40:19 +, KeyTag 8093, Signer-Name: co.in


	0 DNSKEY RR found




Zone: www.askari.co.in
www.askari.co.in	0 DS RR in the parent zone found

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


	• Status: Valid because published


	2 DNSKEY RR found


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


	Public Key with Algorithm 8, KeyTag 25266, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 21.06.2019, 00:00:00 +, Signature-Inception: 31.05.2019, 00:00:00 +, KeyTag 20326, Signer-Name: (root)


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


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

Zone: net
net	1 DS RR in the parent zone found


	1 RRSIG RR to validate DS RR found


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


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


	2 DNSKEY RR found


	Public Key with Algorithm 8, KeyTag 2129, Flags 256


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


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner net., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 14.06.2019, 15:38:57 +, Signature-Inception: 30.05.2019, 15:33:57 +, 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: azurewebsites.net
azurewebsites.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 "d6lofkh528ci82pefugbvfki9hiot2d3" between the hashed NSEC3-owner "d6lhqj45mdkr47555t8vf6k9mqd5hqg4" and the hashed NextOwner "d6m3mg790tp581qcc0jie3vbnac2iaki". So the parent zone confirmes the not-existence of a DS RR. Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner d6lhqj45mdkr47555t8vf6k9mqd5hqg4.net., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 05.06.2019, 05:47:12 +, Signature-Inception: 29.05.2019, 04:37:12 +, KeyTag 2129, Signer-Name: net


	0 DNSKEY RR found




Zone: askari.azurewebsites.net
askari.azurewebsites.net	0 DS RR in the parent zone found

3. Name Servers

Domain	Nameserver	NS-IP
askari.co.in	• ns71.domaincontrol.com / p23	97.74.105.46 Scottsdale/Arizona/US	•
	•	2603:5:2194::2e /US	•
	• ns72.domaincontrol.com / p08	173.201.73.46 Scottsdale/Arizona/US	•
	•	2603:5:2294::2e /US	•
co.in	X ns1.neustar.in / dns5.sjc
	• ns2.neustar.in / dns2.ams		•
	• ns3.neustar.in / dns4.ams		•
	• ns4.neustar.in / dns5.ams		•
	• ns5.neustar.in		•
	• ns6.neustar.in		•
in	X ns1.neustar.in / dns5.sjc
	• ns2.neustar.in / dns2.ams		•
	• ns3.neustar.in / dns4.ams		•
	• ns4.neustar.in / dns5.ams		•
	• ns5.neustar.in		•
	• ns6.neustar.in		•

azurewebsites.net	• ns1prod.122.azuredns-prd.info		•
	• ns1prod.122.azuredns-prd.org		•
	• ns2prod.122.azuredns-prd.info		•
	• ns2prod.122.azuredns-prd.org		•
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:	in
Zone-Name:
Primary:	ns1.neustar.in
Mail:	hostmaster.neustar.in
Serial:	1559376377
Refresh:	1800
Retry:	300
Expire:	1814400
TTL:	1800
num Entries:	6

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

Domain:	askari.co.in
Zone-Name:
Primary:	ns71.domaincontrol.com
Mail:	dns.jomax.net
Serial:	2019053004
Refresh:	28800
Retry:	7200
Expire:	604800
TTL:	600
num Entries:	4


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

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

Domain:	azurewebsites.net
Zone-Name:
Primary:	prd1.azuredns-cloud.net
Mail:	msnhst.microsoft.com
Serial:	2029458736
Refresh:	900
Retry:	300
Expire:	604800
TTL:	60
num Entries:	4

5. Screenshots

No Screenshot listed, because no screenshot found. Perhaps the check is too old, the feature startet 2019-12-23.

6. Url-Checks

show header:

Domainname	Http-Status	Sec.	G
• http://askari.co.in/ 52.172.219.121	200	1.823	H
Content-Length: 37678
Content-Type: text/html; charset=UTF-8
Server: Microsoft-IIS/10.0
X-Powered-By: PHP/7.0.33,ASP.NET
Link: <http://askari.co.in/index.php/wp-json/>; rel="https://api.w.org/",<http://askari.co.in/>; rel=shortlink
Set-Cookie: ARRAffinity=a677b9fb46a4bf6e5191bb609fb56dcc8b44e23d16652cae9c0651b0db8e234d; Path=/; Domain=askari.co.in; HttpOnly
Date: Sat, 01 Jun 2019 08:09:56 GMT
Connection: close

• http://www.askari.co.in/ 52.172.219.121	404	0.267	M
Site Not Found
Content-Type: text/html
Server: Microsoft-IIS/10.0
Date: Sat, 01 Jun 2019 08:09:56 GMT
Connection: close
Content-Length: 2778

• https://askari.co.in/ 52.172.219.121	200	1.764	N
Certificate error: RemoteCertificateNameMismatch
Content-Length: 37707
Content-Type: text/html; charset=UTF-8
Server: Microsoft-IIS/10.0
X-Powered-By: PHP/7.0.33,ASP.NET
Link: <https://askari.co.in/index.php/wp-json/>; rel="https://api.w.org/",<https://askari.co.in/>; rel=shortlink
Set-Cookie: ARRAffinity=a677b9fb46a4bf6e5191bb609fb56dcc8b44e23d16652cae9c0651b0db8e234d; Path=/; Domain=askari.co.in; HttpOnly
Date: Sat, 01 Jun 2019 08:09:58 GMT
Connection: close

• https://www.askari.co.in/ 52.172.219.121	404	1.263	N
Site Not Found
Certificate error: RemoteCertificateNameMismatch
Content-Type: text/html
Server: Microsoft-IIS/10.0
Date: Sat, 01 Jun 2019 08:10:00 GMT
Connection: close
Content-Length: 2778

• http://askari.co.in/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 52.172.219.121	404	1.054	A
Not Found
Visible Content:
Cache-Control: no-cache, must-revalidate, max-age=0
Content-Length: 18214
Content-Type: text/html; charset=UTF-8
Expires: Wed, 11 Jan 1984 05:00:00 GMT
Server: Microsoft-IIS/10.0
X-Powered-By: PHP/7.0.33,ASP.NET
Link: <http://askari.co.in/index.php/wp-json/>; rel="https://api.w.org/"
Set-Cookie: ARRAffinity=a677b9fb46a4bf6e5191bb609fb56dcc8b44e23d16652cae9c0651b0db8e234d; Path=/; Domain=askari.co.in; HttpOnly
Date: Sat, 01 Jun 2019 08:10:01 GMT
Connection: close

• http://www.askari.co.in/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 52.172.219.121	404	0.273	A
Site Not Found
Visible Content:
Content-Type: text/html
Server: Microsoft-IIS/10.0
Date: Sat, 01 Jun 2019 08:10:01 GMT
Connection: close
Content-Length: 2778

7. Comments

	1. General Results, most used to calculate the result
A	name "askari.co.in" is domain, public suffix is "co.in", top-level-domain-type is "country-code", Country is India, tld-manager is "National Internet Exchange of India"
A	Good: All ip addresses are public addresses
A	Good: No asked Authoritative Name Server had a timeout
A	Good: one preferred version: non-www is preferred
A	Good: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):3 complete Content-Type - header (6 urls)
	http://www.askari.co.in/ 52.172.219.121			Url with incomplete Content-Type - header - missing charset
	https://www.askari.co.in/ 52.172.219.121			Url with incomplete Content-Type - header - missing charset
	http://www.askari.co.in/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 52.172.219.121			Url with incomplete Content-Type - header - missing charset
B	https://askari.co.in/ 52.172.219.121	200		Missing HSTS-Header
B	https://askari.co.in/ 52.172.219.121	200	ARRAffinity=a677b9fb46a4bf6e5191bb609fb56dcc8b44e23d16652cae9c0651b0db8e234d; Path=/; Domain=askari.co.in; HttpOnly	Cookie sent via https, but not marked as secure
C	Error - 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.
H	Fatal 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.
M	http://www.askari.co.in/ 52.172.219.121	404		Misconfiguration - main pages should never send http status 400 - 499
M	https://www.askari.co.in/ 52.172.219.121	404		Misconfiguration - main pages should never send http status 400 - 499
N	https://askari.co.in/ 52.172.219.121	200		Error - Certificate isn't trusted, RemoteCertificateNameMismatch
N	https://www.askari.co.in/ 52.172.219.121	404		Error - Certificate isn't trusted, RemoteCertificateNameMismatch
X	Fatal error: Nameserver doesn't support TCP connection: ns1.neustar.in: Fatal error (-14). Details: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. - An existing connection was forcibly closed by the remote host
	2. Header-Checks
	3. DNS- and NameServer - Checks
A	Good: Nameserver supports TCP connections: 4 good Nameserver
A	Good: Nameserver supports Echo Capitalization: 4 good Nameserver
A	Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 4 good Nameserver
A	Good: 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: ns2.neustar.in: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found (dns2.ams). COOKIE: fatal timeout. CLIENTSUBNET: ok.
	Nameserver doesn't pass all EDNS-Checks: ns2.neustar.in: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found (dns2.ams). COOKIE: fatal timeout. CLIENTSUBNET: ok.
	Nameserver doesn't pass all EDNS-Checks: ns3.neustar.in: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (dns4.ams). COOKIE: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. CLIENTSUBNET: ok.
	Nameserver doesn't pass all EDNS-Checks: ns3.neustar.in: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found (dns4.ams). COOKIE: fatal timeout. CLIENTSUBNET: ok.
	Nameserver doesn't pass all EDNS-Checks: ns4.neustar.in: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found (dns5.ams). COOKIE: fatal timeout. CLIENTSUBNET: ok.
	Nameserver doesn't pass all EDNS-Checks: ns4.neustar.in: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found (dns5.ams). COOKIE: fatal timeout. CLIENTSUBNET: ok.
A	Good: 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
A	Good: 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.
A	Good: 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
	https://www.askari.co.in/ 52.172.219.121	404	1.263 seconds	Warning: 404 needs more then one second
	http://askari.co.in/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 52.172.219.121	404	1.054 seconds	Warning: 404 needs more then one second
A	Duration: 112516 milliseconds, 112.516 seconds

8. Connections

Domain

Port

Cert.

Protocol

KeyExchange

Strength

Cipher

Strength

HashAlgorithm

OCSP stapling

Domain/KeyExchange

IP/Strength

Port/Cipher

Cert./Strength

Protocol/HashAlgorithm

OCSP stapling

askari.co.in

52.172.219.121

443

name does not match

Tls12

ECDH Ephermal

256

Aes256

256

Sha384

supported

askari.co.in

52.172.219.121

443

name does not match

Tls12

ECDH Ephermal

256

Aes256

256

Sha384

supported

no Tls.1.2
no Tls.1.1
no Tls.1.0

www.askari.co.in

52.172.219.121

443

name does not match

Tls12

ECDH Ephermal

256

Aes256

256

Sha384

supported

www.askari.co.in

52.172.219.121

443

name does not match

Tls12

ECDH Ephermal

256

Aes256

256

Sha384

supported

no Tls.1.2
no Tls.1.1
no Tls.1.0

9. Certificates

CN=*.azurewebsites.net

17.12.2017

17.12.2019
1959 days expired

*.azurewebsites.net, *.scm.azurewebsites.net, *.azure-mobile.net, *.scm.azure-mobile.net, *.sso.azurewebsites.net - 5 entries

CN=*.azurewebsites.net

17.12.2017

17.12.2019
1959 days expired

*.azurewebsites.net, *.scm.azurewebsites.net, *.azure-mobile.net, *.scm.azure-mobile.net, *.sso.azurewebsites.net - 5 entries

Keyalgorithm	RSA encryption (2048 bit)
Signatur:	SHA256 With RSA-Encryption
Serial Number:	160000708D70A2A4CB63ABA1C700000000708D
Thumbprint:	3AB0B1C27F746FD90C34F0D6A960CF73A4229DE8
SHA256 / Certificate:	UuQ4PJYa6bhN8PQxThU+xxZ/XpvO561C715OmzZ5mQw=
SHA256 hex / Cert (DANE * 0 1):	52e4383c961ae9b84df0f4314e153ec7167f5e9bcee7ad42ef5e4e9b3679990c
SHA256 hex / PublicKey (DANE * 1 1):	3ad191ee2c6fa994f1687e9ce55a5e8dee0850c81d7ea818748ab96729147207
SHA256 hex / Subject Public Key Information (SPKI):	3ad191ee2c6fa994f1687e9ce55a5e8dee0850c81d7ea818748ab96729147207
SPKI checked via https://v1.pwnedkeys.com/spki-hash:	Good: Key isn't compromised
OCSP - Url:	http://ocsp.msocsp.com
OCSP - must staple:	no
Certificate Transparency:	no
Enhanced Key Usage:	Client Authentication (1.3.6.1.5.5.7.3.2), Server Authentication (1.3.6.1.5.5.7.3.1)

CN=Microsoft IT TLS CA 4, OU=Microsoft IT, O=Microsoft Corporation, L=Redmond, S=Washington, C=US

20.05.2016

20.05.2024
343 days expired

CN=Microsoft IT TLS CA 4, OU=Microsoft IT, O=Microsoft Corporation, L=Redmond, S=Washington, C=US

20.05.2016

20.05.2024
343 days expired

Keyalgorithm	RSA encryption (4096 bit)
Signatur:	SHA256 With RSA-Encryption
Serial Number:	0B6AB3B03EB1A9F6C460926AA8CDFEB3
Thumbprint:	8A38755D0996823FE8FA3116A277CE446EAC4E99
SHA256 / Certificate:	X/rEPg3cW0rytpb2vE236R3zFLuP4NBxOgsaetKmj6w=
SHA256 hex / Cert (DANE * 0 1):	5ffac43e0ddc5b4af2b696f6bc4db7e91df314bb8fe0d0713a0b1a7ad2a68fac
SHA256 hex / PublicKey (DANE * 1 1):	c1463d10e4c9992ec08f87c3542bbf29e13efa657b16021c6e7e1684ccf52369
SHA256 hex / Subject Public Key Information (SPKI):	c1463d10e4c9992ec08f87c3542bbf29e13efa657b16021c6e7e1684ccf52369
SPKI checked via https://v1.pwnedkeys.com/spki-hash:	Good: Key isn't compromised
OCSP - Url:	http://ocsp.digicert.com
OCSP - must staple:	no
Certificate Transparency:	no
Enhanced Key Usage:	Server Authentication (1.3.6.1.5.5.7.3.1), Client Authentication (1.3.6.1.5.5.7.3.2), OCSP Signing (1.3.6.1.5.5.7.3.9)

CN=Baltimore CyberTrust Root, OU=CyberTrust, O=Baltimore, C=IE

12.05.2000

13.05.2025
expires in 15 days

CN=Baltimore CyberTrust Root, OU=CyberTrust, O=Baltimore, C=IE

12.05.2000

13.05.2025
expires in 15 days

Keyalgorithm	RSA encryption (2048 bit)
Signatur:	SHA-1 with RSA Encryption
Serial Number:	020000B9
Thumbprint:	D4DE20D05E66FC53FE1A50882C78DB2852CAE474
SHA256 / Certificate:	Fq9XqfZ2sKsSYJWqXrre8iqzERnWRKyVzUuT2/Pyaus=
SHA256 hex / Cert (DANE * 0 1):	16af57a9f676b0ab126095aa5ebadef22ab31119d644ac95cd4b93dbf3f26aeb
SHA256 hex / PublicKey (DANE * 1 1):	63d9af9b47b1064d49a10e7b7fd566dbc8caa399459bfc2829c571ad8c6ef34a
SHA256 hex / Subject Public Key Information (SPKI):	63d9af9b47b1064d49a10e7b7fd566dbc8caa399459bfc2829c571ad8c6ef34a
SPKI checked via https://v1.pwnedkeys.com/spki-hash:	Good: Key isn't compromised
OCSP - Url:
OCSP - must staple:	no
Certificate Transparency:	no
Enhanced Key Usage:

10. Last Certificates - Certificate Transparency Log Check

1. Source CertSpotter - active certificates (one check per day)

Small Code Update - wait one minute

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

Small Code Update - wait one minute

11. Html-Content - Entries

Summary

No data found or small Code-update

Details (currently limited to 500 rows - some problems with spam users)

Small Code Update - wait one minute

12. Html-Parsing via https://validator.w3.org/nu/

Small Code update, wait one minute

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers:

No NameServer - IP address informations found. The feature is new (2020-05-07), so recheck this domain.

14. CAA - Entries

Domainname	flag	Value	∑ Queries
askari.azurewebsites.net			1
azurewebsites.net	0	no CAA entry found	1
www.askari.co.in			1
askari.co.in	0	no CAA entry found	1
co.in	0	no CAA entry found	1
net	0	no CAA entry found	1
in	0	no CAA entry found	1

15. TXT - Entries

Domainname	TXT Entry	Status	∑ Queries
askari.co.in	askari.azurewebsites.net	ok	1
askari.co.in	v=spf1 mx a ip4:203.109.86.129 ~all	ok	1
www.askari.co.in			1
askari.azurewebsites.net			1
_acme-challenge.askari.co.in	6VWSP1b8SKQJIqoATpI9vCAjgX7Mer_vI9CJ37Gppzk	looks good, correct length, correct characters	1
_acme-challenge.www.askari.co.in		Name Error - The domain name does not exist	1
_acme-challenge.askari.azurewebsites.net		Name Error - The domain name does not exist	1
_acme-challenge.askari.co.in.askari.co.in		Name Error - The domain name does not exist	1
_acme-challenge.www.askari.co.in.askari.co.in		Name Error - The domain name does not exist	1
_acme-challenge.www.askari.co.in.www.askari.co.in		Name Error - The domain name does not exist	1
_acme-challenge.askari.azurewebsites.net.askari.azurewebsites.net		Name Error - The domain name does not exist	1

16. DomainService - Entries

No DomainServiceEntries entries found

17. Cipher Suites

No Ciphers found

18. Portchecks

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

Permalink: https://check-your-website.server-daten.de/?i=257e14b7-b485-4d3f-8284-6fe97ad49a05

Last Result: https://check-your-website.server-daten.de/?q=askari.co.in - 2019-06-01 10:08:31

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

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

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

QR-Code of this page - https://check-your-website.server-daten.de/?d=askari.co.in

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

Older results

1. IP-Addresses

2. DNSSEC

3. Name Servers

4. SOA-Entries

5. Screenshots

6. Url-Checks

7. Comments

1. General Results, most used to calculate the result

2. Header-Checks

3. DNS- and NameServer - Checks

4. Content- and Performance-critical Checks

8. Connections

9. Certificates

10. Last Certificates - Certificate Transparency Log Check

1. Source CertSpotter - active certificates (one check per day)

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

11. Html-Content - Entries

Summary

Details (currently limited to 500 rows - some problems with spam users)

12. Html-Parsing via https://validator.w3.org/nu/

13. Nameserver - IP-Adresses

14. CAA - Entries

15. TXT - Entries

16. DomainService - Entries

17. Cipher Suites

18. Portchecks