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

0 in Queue, 0 of max. 8 Checks (19:22:59)
Why should you only use Prefix - Cookies? |
Hall of Fame - A+ and A

 

Shortcuts: 1. IP-Addresses | 2. DNSSEC | 3. Name Servers | 4. SOA-Entries | 5. Screenshots | 6. Url-Checks | 7. Comments | 8. Connections | 9. Certificates | 10. CT-Logs | 11. Html-Content | 12. Html-Parsing | 13. NameServer-IPAddresses | 14. CAA | 15. TXT | 16. DomainServiceEntries | 17. Cipher Suites | 18. Portchecks |

 

N

 

No trusted Certificate

 

Checked:
20.06.2019 11:25:16

 

Older results

No older results found

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
tattvadesigns.co.in
A
184.168.131.241
Scottsdale/Arizona/US
Hostname: ip-184-168-131-241.ip.secureserver.net
yes
2
0

AAAA

yes


www.tattvadesigns.co.in
CNAME
tattvadesigns.co.in
yes
1
0

A
184.168.131.241
Scottsdale/Arizona/US
Hostname: ip-184-168-131-241.ip.secureserver.net
yes


 

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: 01.07.2019, 00:00:00 +, Signature-Inception: 10.06.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: 02.07.2019, 17:00:00 +, Signature-Inception: 19.06.2019, 16: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: 19.07.2019, 20:31:11 +, Signature-Inception: 19.06.2019, 20:00:38 +, KeyTag 9182, Signer-Name: in






RRSIG-Owner in., Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 19.07.2019, 20:31:11 +, Signature-Inception: 19.06.2019, 20:00:38 +, 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: 19.07.2019, 19:47:01 +, Signature-Inception: 19.06.2019, 19:03:16 +, 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: 19.07.2019, 19:51:56 +, Signature-Inception: 19.06.2019, 18:56:19 +, KeyTag 8093, Signer-Name: co.in






RRSIG-Owner co.in., Algorithm: 7, 2 Labels, original TTL: 900 sec, Signature-expiration: 19.07.2019, 19:51:56 +, Signature-Inception: 19.06.2019, 18:56:19 +, 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: tattvadesigns.co.in

tattvadesigns.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 "vnvekpa2jsj99v284m85r7m71im0fe5h" between the hashed NSEC3-owner "vnl6uk89otqh9akdc8j3n7k4rffpj3l3" and the hashed NextOwner "voqi557pmov9oemqon3ghj39dka4rfsg". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner vnl6uk89otqh9akdc8j3n7k4rffpj3l3.co.in., Algorithm: 7, 3 Labels, original TTL: 1800 sec, Signature-expiration: 18.07.2019, 16:57:45 +, Signature-Inception: 18.06.2019, 16:25:22 +, KeyTag 8093, Signer-Name: co.in






0 DNSKEY RR found









Zone: www.tattvadesigns.co.in

www.tattvadesigns.co.in
0 DS RR in the parent zone found

 

3. Name Servers

DomainNameserverNS-IP
tattvadesigns.co.in
•  ns15.domaincontrol.com / p05
97.74.107.8
Scottsdale/Arizona/US		•

• 
2603:5:21b0::8
/US		•

•  ns16.domaincontrol.com / p04
173.201.75.8
Scottsdale/Arizona/US		•

• 
2603:5:22b0::8
/US		•
co.in
•  ns1.neustar.in / dns1.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 / dns2.sjc


•  ns2.neustar.in / dns2.ams
•

•  ns3.neustar.in / dns4.ams
•

•  ns4.neustar.in / dns5.ams
•

•  ns5.neustar.in
•

•  ns6.neustar.in
•

 

4. SOA-Entries


Domain:in
Zone-Name:
Primary:ns1.neustar.in
Mail:hostmaster.neustar.in
Serial:1561022537
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:1561022558
Refresh:1800
Retry:300
Expire:1814400
TTL:1800
num Entries:6


Domain:tattvadesigns.co.in
Zone-Name:
Primary:ns15.domaincontrol.com
Mail:dns.jomax.net
Serial:2019061501
Refresh:28800
Retry:7200
Expire:604800
TTL:600
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


:

:
DomainnameHttp-StatusredirectSec.G
• http://tattvadesigns.co.in/
184.168.131.241
200


0.800
H
Server: nginx/1.12.2
Date: Thu, 20 Jun 2019 09:25:58 GMT
Content-Type: text/html; charset=utf-8
Transfer-Encoding: chunked
Connection: close

• http://www.tattvadesigns.co.in/
184.168.131.241
200


0.873
H
Server: nginx/1.12.2
Date: Thu, 20 Jun 2019 09:25:58 GMT
Content-Type: text/html; charset=utf-8
Transfer-Encoding: chunked
Connection: close

• https://tattvadesigns.co.in/
184.168.131.241
200


1.987
N
Certificate error: RemoteCertificateNameMismatch
Server: nginx/1.12.2
Date: Thu, 20 Jun 2019 09:25:59 GMT
Content-Type: text/html; charset=utf-8
Transfer-Encoding: chunked
Connection: close

• https://www.tattvadesigns.co.in/
184.168.131.241
200


1.983
N
Certificate error: RemoteCertificateNameMismatch
Server: nginx/1.12.2
Date: Thu, 20 Jun 2019 09:26:02 GMT
Content-Type: text/html; charset=utf-8
Transfer-Encoding: chunked
Connection: close

• http://tattvadesigns.co.in/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
184.168.131.241
200


0.530

Visible Content:
Server: nginx/1.12.2
Date: Thu, 20 Jun 2019 09:26:04 GMT
Content-Type: text/html; charset=utf-8
Transfer-Encoding: chunked
Connection: close

• http://www.tattvadesigns.co.in/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
184.168.131.241
200


0.403

Visible Content:
Server: nginx/1.12.2
Date: Thu, 20 Jun 2019 09:26:04 GMT
Content-Type: text/html; charset=utf-8
Transfer-Encoding: chunked
Connection: close

 

7. Comments


1. General Results, most used to calculate the result

Aname "tattvadesigns.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"
AGood: All ip addresses are public addresses
AGood: No asked Authoritative Name Server had a timeout
AGood: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
Bhttps://tattvadesigns.co.in/ 184.168.131.241
200

Missing HSTS-Header
Bhttps://www.tattvadesigns.co.in/ 184.168.131.241
200

Missing HSTS-Header
CError - no preferred version www or non-www. Select one version as preferred version, then add a redirect https + not-preferred version to https + preferred version. Perhaps in your port 443 vHost something like "RewriteEngine on" + "RewriteCond %{SERVER_NAME} = example.com" + "ReWriteRule ^ https://www.example.com%{REQUEST_URI} [END,QSA,R=permanent]" (three rows, without the "). That should create a redirect https + example.com ⇒ https + www.example.com. Or switch both values to use the non-www version as your preferred version.
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: 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.
Ihttps://tattvadesigns.co.in/ 184.168.131.241
200

Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Check the Html-Content - Part.
Ihttps://www.tattvadesigns.co.in/ 184.168.131.241
200

Content problems or problems with resources included - http links, files doesn't exist, different Content-Type definitions. Check the Html-Content - Part.
Nhttps://tattvadesigns.co.in/ 184.168.131.241
200

Error - Certificate isn't trusted, RemoteCertificateNameMismatch
Nhttps://www.tattvadesigns.co.in/ 184.168.131.241
200

Error - Certificate isn't trusted, RemoteCertificateNameMismatch
XFatal 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

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: 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: 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: 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.
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://tattvadesigns.co.in/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 184.168.131.241
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.tattvadesigns.co.in/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 184.168.131.241
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.
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: 49440 milliseconds, 49.440 seconds

 

8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
tattvadesigns.co.in
184.168.131.241
443
name does not match
Tls12
ECDH Ephermal
256
Aes256
256
Sha384
error checking OCSP stapling
ok
tattvadesigns.co.in
184.168.131.241
443
name does not match
Tls12

ECDH Ephermal
256
Aes256
256
Sha384
error checking OCSP stapling
ok
 
no Tls.1.2
no Tls.1.1
no Tls.1.0

 no Tls.1.2
no Tls.1.1
no Tls.1.0
Chain - too much certificates, don't send root certificates

1CN=shortener.secureserver.net, O="Special Domain Services, LLC", L=Scottsdale, C=US, ST=Arizona


2CN=Starfield Secure Certificate Authority - G2, OU=http://certs.starfieldtech.com/repository/, O="Starfield Technologies, Inc.", L=Scottsdale, C=US, ST=Arizona


3CN=Starfield Root Certificate Authority - G2, O="Starfield Technologies, Inc.", L=Scottsdale, C=US, ST=Arizona


4OU=Starfield Class 2 Certification Authority, O="Starfield Technologies, Inc.", C=US


www.tattvadesigns.co.in
184.168.131.241
443
name does not match
Tls12
ECDH Ephermal
256
Aes256
256
Sha384
error checking OCSP stapling
ok

www.tattvadesigns.co.in
184.168.131.241
443
name does not match
Tls12

ECDH Ephermal
256
Aes256
256
Sha384
error checking OCSP stapling
ok
 
no Tls.1.2
no Tls.1.1
no Tls.1.0

 no Tls.1.2
no Tls.1.1
no Tls.1.0
Chain - too much certificates, don't send root certificates

1CN=shortener.secureserver.net, O="Special Domain Services, LLC", L=Scottsdale, C=US, ST=Arizona


2CN=Starfield Secure Certificate Authority - G2, OU=http://certs.starfieldtech.com/repository/, O="Starfield Technologies, Inc.", L=Scottsdale, C=US, ST=Arizona


3CN=Starfield Root Certificate Authority - G2, O="Starfield Technologies, Inc.", L=Scottsdale, C=US, ST=Arizona


4OU=Starfield Class 2 Certification Authority, O="Starfield Technologies, Inc.", C=US

 

9. Certificates

1.
1.
CN=shortener.secureserver.net, O="Special Domain Services, LLC", L=Scottsdale, S=Arizona, C=US, SERIALNUMBER=R17247303, OID.2.5.4.15=Private Organization, OID.1.3.6.1.4.1.311.60.2.1.2=Arizona, OID.1.3.6.1.4.1.311.60.2.1.3=US
27.09.2018
27.09.2020
1690 days expired		shortener.secureserver.net, www.shortener.secureserver.net - 2 entries
1.
1.
CN=shortener.secureserver.net, O="Special Domain Services, LLC", L=Scottsdale, S=Arizona, C=US, SERIALNUMBER=R17247303, OID.2.5.4.15=Private Organization, OID.1.3.6.1.4.1.311.60.2.1.2=Arizona, OID.1.3.6.1.4.1.311.60.2.1.3=US
27.09.2018

27.09.2020
1690 days expired


shortener.secureserver.net, www.shortener.secureserver.net - 2 entries

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:00EF5927289A9FDADB
Thumbprint:22873D8FEFEB318394D1B906A5E4657876552D80
SHA256 / Certificate:/jivrbIJNjrPiS+jdPi3b+Db3cS1tf2JJLGaCZqqTw8=
SHA256 hex / Cert (DANE * 0 1):fe38afadb209363acf892fa374f8b76fe0dbddc4b5b5fd8924b19a099aaa4f0f
SHA256 hex / PublicKey (DANE * 1 1):53417153b98c96675a05d3ac1c04154019ba4dbf351298169c07e21d718cec20
SHA256 hex / Subject Public Key Information (SPKI):53417153b98c96675a05d3ac1c04154019ba4dbf351298169c07e21d718cec20
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://ocsp.starfieldtech.com/
OCSP - must staple:no
Certificate Transparency:yes
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)




2.
CN=shortener.secureserver.net, O="Special Domain Services, LLC", L=Scottsdale, S=Arizona, C=US, SERIALNUMBER=R17247303, OID.2.5.4.15=Private Organization, OID.1.3.6.1.4.1.311.60.2.1.2=Arizona, OID.1.3.6.1.4.1.311.60.2.1.3=US
27.09.2018
27.09.2020
1690 days expired		shortener.secureserver.net, www.shortener.secureserver.net - 2 entries

2.
CN=shortener.secureserver.net, O="Special Domain Services, LLC", L=Scottsdale, S=Arizona, C=US, SERIALNUMBER=R17247303, OID.2.5.4.15=Private Organization, OID.1.3.6.1.4.1.311.60.2.1.2=Arizona, OID.1.3.6.1.4.1.311.60.2.1.3=US
27.09.2018

27.09.2020
1690 days expired


shortener.secureserver.net, www.shortener.secureserver.net - 2 entries

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:00EF5927289A9FDADB
Thumbprint:22873D8FEFEB318394D1B906A5E4657876552D80
SHA256 / Certificate:/jivrbIJNjrPiS+jdPi3b+Db3cS1tf2JJLGaCZqqTw8=
SHA256 hex / Cert (DANE * 0 1):fe38afadb209363acf892fa374f8b76fe0dbddc4b5b5fd8924b19a099aaa4f0f
SHA256 hex / PublicKey (DANE * 1 1):53417153b98c96675a05d3ac1c04154019ba4dbf351298169c07e21d718cec20
SHA256 hex / Subject Public Key Information (SPKI):53417153b98c96675a05d3ac1c04154019ba4dbf351298169c07e21d718cec20
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://ocsp.starfieldtech.com/
OCSP - must staple:no
Certificate Transparency:yes
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)




3.
CN=Starfield Secure Certificate Authority - G2, OU=http://certs.starfieldtech.com/repository/, O="Starfield Technologies, Inc.", L=Scottsdale, S=Arizona, C=US
03.05.2011
03.05.2031
expires in 2180 days

3.
CN=Starfield Secure Certificate Authority - G2, OU=http://certs.starfieldtech.com/repository/, O="Starfield Technologies, Inc.", L=Scottsdale, S=Arizona, C=US
03.05.2011

03.05.2031
expires in 2180 days




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:07
Thumbprint:7EDC376DCFD45E6DDF082C160DF6AC21835B95D4
SHA256 / Certificate:k6B4mNibLMoWa6bx+KFBOM5Dgo5JG4MZJryCR9ORzHI=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):f24196ae94078667348f02e8e37458a3a6e6aad1e0b0dc610118cce721427bfc
SHA256 hex / Subject Public Key Information (SPKI):f24196ae94078667348f02e8e37458a3a6e6aad1e0b0dc610118cce721427bfc
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Check unknown. No result 404 / 200
OCSP - Url:http://ocsp.starfieldtech.com/
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:




4.
CN=Starfield Secure Certificate Authority - G2, OU=http://certs.starfieldtech.com/repository/, O="Starfield Technologies, Inc.", L=Scottsdale, S=Arizona, C=US
03.05.2011
03.05.2031
expires in 2180 days

4.
CN=Starfield Secure Certificate Authority - G2, OU=http://certs.starfieldtech.com/repository/, O="Starfield Technologies, Inc.", L=Scottsdale, S=Arizona, C=US
03.05.2011

03.05.2031
expires in 2180 days




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:07
Thumbprint:7EDC376DCFD45E6DDF082C160DF6AC21835B95D4
SHA256 / Certificate:k6B4mNibLMoWa6bx+KFBOM5Dgo5JG4MZJryCR9ORzHI=
SHA256 hex / Cert (DANE * 0 1):93a07898d89b2cca166ba6f1f8a14138ce43828e491b831926bc8247d391cc72
SHA256 hex / PublicKey (DANE * 1 1):f24196ae94078667348f02e8e37458a3a6e6aad1e0b0dc610118cce721427bfc
SHA256 hex / Subject Public Key Information (SPKI):f24196ae94078667348f02e8e37458a3a6e6aad1e0b0dc610118cce721427bfc
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://ocsp.starfieldtech.com/
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:




5.
CN=Starfield Root Certificate Authority - G2, O="Starfield Technologies, Inc.", L=Scottsdale, S=Arizona, C=US
01.01.2014
30.05.2031
expires in 2207 days

5.
CN=Starfield Root Certificate Authority - G2, O="Starfield Technologies, Inc.", L=Scottsdale, S=Arizona, C=US
01.01.2014

30.05.2031
expires in 2207 days




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:391484
Thumbprint:9565B778C8A50EB4FEFD45C8A658DDE2411EAD0A
SHA256 / Certificate:n0PVLoCMIK/2ngL6rCBarGhOaXUhPWYg+sZL3l/KtLw=
SHA256 hex / Cert (DANE * 0 1):9f43d52e808c20aff69e02faac205aac684e6975213d6620fac64bde5fcab4bc
SHA256 hex / PublicKey (DANE * 1 1):808d68b3fab4884a5f971ace7d10550d7a95a163774f3ec36afffb213fbe4c74
SHA256 hex / Subject Public Key Information (SPKI):808d68b3fab4884a5f971ace7d10550d7a95a163774f3ec36afffb213fbe4c74
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://ocsp.starfieldtech.com/
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:




6.
CN=Starfield Root Certificate Authority - G2, O="Starfield Technologies, Inc.", L=Scottsdale, S=Arizona, C=US
01.09.2009
01.01.2038
expires in 4615 days

6.
CN=Starfield Root Certificate Authority - G2, O="Starfield Technologies, Inc.", L=Scottsdale, S=Arizona, C=US
01.09.2009

01.01.2038
expires in 4615 days




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:00
Thumbprint:B51C067CEE2B0C3DF855AB2D92F4FE39D4E70F0E
SHA256 / Certificate:LOHLC/nS+eECmT++IVFSw7LdDKveHGjlMZuDkVTbt/U=
SHA256 hex / Cert (DANE * 0 1):2ce1cb0bf9d2f9e102993fbe215152c3b2dd0cabde1c68e5319b839154dbb7f5
SHA256 hex / PublicKey (DANE * 1 1):808d68b3fab4884a5f971ace7d10550d7a95a163774f3ec36afffb213fbe4c74
SHA256 hex / Subject Public Key Information (SPKI):808d68b3fab4884a5f971ace7d10550d7a95a163774f3ec36afffb213fbe4c74
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:





7.
OU=Starfield Class 2 Certification Authority, O="Starfield Technologies, Inc.", C=US
29.06.2004
29.06.2034
expires in 3333 days

7.
OU=Starfield Class 2 Certification Authority, O="Starfield Technologies, Inc.", C=US
29.06.2004

29.06.2034
expires in 3333 days




KeyalgorithmRSA encryption ( bit)
Signatur:SHA-1 with RSA Encryption
Serial Number:00
Thumbprint:AD7E1C28B064EF8F6003402014C3D0E3370EB58A
SHA256 / Certificate:FGX6IFOXuHb6pvCplY5VkOQPzH+qT7fCyGd1Iftftlg=
SHA256 hex / Cert (DANE * 0 1):1465fa205397b876faa6f0a9958e5590e40fcc7faa4fb7c2c8677521fb5fb658
SHA256 hex / PublicKey (DANE * 1 1):15f14ac45c9c7da233d3479164e8137fe35ee0f38ae858183f08410ea82ac4b4
SHA256 hex / Subject Public Key Information (SPKI):15f14ac45c9c7da233d3479164e8137fe35ee0f38ae858183f08410ea82ac4b4
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)

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

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

DomainnameflagNameValue∑ Queries∑ Timeout
www.tattvadesigns.co.in



1
0
tattvadesigns.co.in
0

no CAA entry found
1
0
co.in
0

no CAA entry found
1
0
in
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
tattvadesigns.co.in

ok
1
0
www.tattvadesigns.co.in


1
0
_acme-challenge.tattvadesigns.co.in

Name Error - The domain name does not exist
1
0
_acme-challenge.www.tattvadesigns.co.in

Name Error - The domain name does not exist
1
0
_acme-challenge.tattvadesigns.co.in.tattvadesigns.co.in

Name Error - The domain name does not exist
1
0
_acme-challenge.www.tattvadesigns.co.in.tattvadesigns.co.in

Name Error - The domain name does not exist
1
0
_acme-challenge.www.tattvadesigns.co.in.www.tattvadesigns.co.in

Name Error - The domain name does not exist
1
0

 

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=2f2afb79-b3d0-4424-9bf5-e5837575268c

 

Last Result: https://check-your-website.server-daten.de/?q=tattvadesigns.co.in - 2019-06-20 11:25:16

 

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

 

<a href="https://check-your-website.server-daten.de/?q=tattvadesigns.co.in" target="_blank">Check this Site: tattvadesigns.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=tattvadesigns.co.in

 

 

Jürgen Auer • Friedenstr. 37 • 10249 Berlin • +49(0)30 420 200 60 • info@sql-und-xml.de • USt-IdNr.: DE221734518

 

Errors, ideas, questions? Use the Contact form • A project using Server-Daten - Web Database solutions