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


 

 

A

 

Top config

 

Checked:
23.09.2020 16:25:14

 

Older results

 

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
tokenly.in
A
76.76.21.21
Walnut/California/United States (US) - Amazon.com, Inc.
No Hostname found
yes
1
0

AAAA

yes


www.tokenly.in

Name Error
yes
1
0
*.tokenly.in
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 20326, Flags 257 (SEP = Secure Entry Point)






Public Key with Algorithm 8, KeyTag 26116, Flags 256






Public Key with Algorithm 8, KeyTag 46594, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 10.10.2020, 00:00:00 +, Signature-Inception: 19.09.2020, 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: 06.10.2020, 05:00:00 +, Signature-Inception: 23.09.2020, 04:00:00 +, KeyTag 46594, Signer-Name: (root)






Status: Good - Algorithmus 8 and DNSKEY with KeyTag 46594 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: 16.10.2020, 21:17:58 +, Signature-Inception: 16.09.2020, 21:04:15 +, KeyTag 54739, Signer-Name: in






RRSIG-Owner in., Algorithm: 8, 1 Labels, original TTL: 900 sec, Signature-expiration: 16.10.2020, 21:17:58 +, Signature-Inception: 16.09.2020, 21:04:15 +, 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: tokenly.in

tokenly.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 "bvus2lcqfennjku8giiv551qa97u01j1" between the hashed NSEC3-owner "bvsslgm085uhpmvd2pslqumbe4p2b5fb" and the hashed NextOwner "bvv5e0331difs2eo1bvgaf5o79tv09n3". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner bvsslgm085uhpmvd2pslqumbe4p2b5fb.in., Algorithm: 8, 2 Labels, original TTL: 1800 sec, Signature-expiration: 20.10.2020, 09:34:51 +, Signature-Inception: 20.09.2020, 09:19:52 +, 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 "bogvhkg29utcjapqn8d3rgvdg613eusq". So that domain name is the Closest Encloser of "tokenly.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: 22.10.2020, 13:12:21 +, Signature-Inception: 22.09.2020, 12:29:34 +, KeyTag 65169, Signer-Name: in






0 DNSKEY RR found









Zone: www.tokenly.in

www.tokenly.in
0 DS RR in the parent zone found

 

3. Name Servers

DomainNameserverNS-IP
www.tokenly.in
  dns1.registrar-servers.com

tokenly.in
  dns1.registrar-servers.com
156.154.132.200
New York/United States (US) - NeuStar, Inc.


 
2610:a1:1024::200
Ashburn/Virginia/United States (US) - NeuStar, Inc.


  dns2.registrar-servers.com
156.154.133.200
New York/United States (US) - NeuStar, Inc.


 
2610:a1:1025::200
Ashburn/Virginia/United States (US) - NeuStar, Inc.

in
  ns1.neustar.in


  ns1.registry.in


  ns2.registry.in


  ns3.registry.in


  ns4.registry.in


  ns5.registry.in


  ns6.registry.in

 

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:1600870873
Refresh:1800
Retry:300
Expire:1814400
TTL:1800
num Entries:6


Domain:tokenly.in
Zone-Name:tokenly.in
Primary:dns1.registrar-servers.com
Mail:hostmaster.registrar-servers.com
Serial:1599591303
Refresh:43200
Retry:3600
Expire:604800
TTL:3601
num Entries:4


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


5. Screenshots

Startaddress: https://tokenly.in, address used: https://tokenly.in/, Screenshot created 2020-09-23 16:26:09 +00:0

 

Mobil (412px x 732px)

 

732 milliseconds

 

Screenshot mobile - https://tokenly.in/
Mobil + Landscape (732px x 412px)

 

695 milliseconds

 

Screenshot mobile landscape - https://tokenly.in/
Screen (1280px x 1680px)

 

2370 milliseconds

 

Screenshot Desktop - https://tokenly.in/

 

Mobile- and other Chrome-Checks


widthheight
visual Viewport396732
content Size39610929

 

Good: No horizontal scrollbar. Content-size width = visual Viewport width.

 

Chrome-Connection: secure. secure connection settings. The connection to this site is encrypted and authenticated using TLS 1.3, X25519, and AES_128_GCM.

 

Chrome-Resources : secure. all served securely. All resources on this page are served securely.

 

 

6. Url-Checks


:

:
DomainnameHttp-StatusredirectSec.G
• http://tokenly.in/
76.76.21.21
308
https://tokenly.in/
Html is minified: 100.00 %
0.047
A
Date: Wed, 23 Sep 2020 14:25:36 GMT
Content-Type: text/plain
Transfer-Encoding: chunked
Connection: close
Location: https://tokenly.in/
Refresh: 0;url=https://tokenly.in/
server: Vercel
x-vercel-id: cdg1::2jmnn-1600871136846-efd1978b4893

• https://tokenly.in/
76.76.21.21
200

Html is minified: 100.24 %
3.890
A
Date: Wed, 23 Sep 2020 14:25:38 GMT
Content-Type: text/html; charset=utf-8
Transfer-Encoding: chunked
Connection: close
content-disposition: inline; filename="index"
cache-control: public, max-age=0, must-revalidate
access-control-allow-origin: *
etag: W/"70ef283bca1021e8c1702cd7b8c75faef836fd9a6314f8c6a68e39a86cfa3746"
x-vercel-cache: MISS
age: 0
server: Vercel
x-vercel-id: cdg1::lnwwv-1600871137213-8bfe765fb3e5
strict-transport-security: max-age=63072000
Content-Encoding: gzip

• http://tokenly.in/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
76.76.21.21
404

Html is minified: 100.00 %
0.186
A
Not Found
Visible Content: {"error":{"message":"Token not found","code":"not_found","statusCode":404,"meta":{}}}
Date: Wed, 23 Sep 2020 14:25:41 GMT
Content-Type: application/json; charset=utf-8
Content-Length: 85
Connection: close
Access-Control-Allow-Origin: *
Access-Control-Allow-Headers: Authorization, Accept, Content-Type
Access-Control-Allow-Methods: OPTIONS, GET, POST, PUT, PATCH, DELETE
server: Vercel
x-vercel-id: lhr1::htpzf-1600871141602-5d31417f93bf

• https://76.76.21.21/
76.76.21.21
404

Html is minified: 101.52 %
2.313
N
Not Found
Certificate error: RemoteCertificateNameMismatch, RemoteCertificateChainErrors
small visible content (num chars: 65)
The deployment could not be found on Vercel. DEPLOYMENT_NOT_FOUND
Date: Wed, 23 Sep 2020 14:25:41 GMT
Content-Type: text/plain; charset=utf-8
Connection: close
content-length: 67
server: Vercel
x-vercel-id: cdg1::lnwwv-1600871141933-f5134ed1ed97
strict-transport-security: max-age=63072000
cache-control: s-maxage=0

 

7. Comments


1. General Results, most used to calculate the result

Aname "tokenly.in" is domain, 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: 481 (complete: 131120)
AGood: All ip addresses are public addresses
Warning: Only one ip address found: tokenly.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: tokenly.in has no ipv6 address.
AGood: No asked Authoritative Name Server had a timeout
ADNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
AGood: destination is https
AGood - only one version with Http-Status 200
AGood: one preferred version: non-www is preferred
AGood: No cookie sent via http.
AGood: every https has a Strict Transport Security Header
AGood: HSTS max-age is long enough, 63072000 seconds = 730 days
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)
http://tokenly.in/ 76.76.21.21

0;url=https://tokenly.in/
Info: Non-standard Header "Refresh" found.
Ahttp://tokenly.in/ 76.76.21.21
308
https://tokenly.in/
Correct redirect http - https with the same domain name
Mhttps://76.76.21.21/ 76.76.21.21
404

Misconfiguration - main pages should never send http status 400 - 499
Nhttps://76.76.21.21/ 76.76.21.21
404

Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Info: Checking all ip addresses of that domain without sending the hostname only one certificate found. Checking all ip addresses and sending the hostname only one certificate found. Both certificates are different. So that domain requires Server Name Indication (SNI), so the server is able to select the correct certificate.: Domain tokenly.in, 1 ip addresses.

2. Header-Checks (Cross-Origin-* headers are alpha - started 2024-06-05)


3. DNS- and NameServer - Checks

AInfo:: 37 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
AInfo:: 37 Queries complete, 37 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
Bad (greater 8):: An average of 18.5 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 2 different Name Servers found: dns1.registrar-servers.com, dns2.registrar-servers.com, 2 Name Servers included in Delegation: dns1.registrar-servers.com, dns2.registrar-servers.com, 2 Name Servers included in 1 Zone definitions: dns1.registrar-servers.com, dns2.registrar-servers.com, 1 Name Servers listed in SOA.Primary: dns1.registrar-servers.com.
AGood: Only one SOA.Primary Name Server found.: dns1.registrar-servers.com.
AGood: SOA.Primary Name Server included in the delegation set.: dns1.registrar-servers.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: dns1.registrar-servers.com, dns2.registrar-servers.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: registrar-servers.com
Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: US
AInfo: Ipv4-Subnet-list: 2 Name Servers, 1 different subnets (first Byte): 156., 1 different subnets (first two Bytes): 156.154., 2 different subnets (first three Bytes): 156.154.132., 156.154.133.
AGood: Name Server IPv4-addresses from different subnet found:
AInfo: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2610:, 1 different subnets (first two blocks): 2610:00a1:, 2 different subnets (first three blocks): 2610:00a1:1024:, 2610:00a1:1025:, 2 different subnets (first four blocks): 2610:00a1:1024:0000:, 2610:00a1:1025: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: 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

AGood: All checks /.well-known/acme-challenge/random-filename without redirects answer with the expected http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 challenge should work. If it doesn't work: Check your vHost configuration (apachectl -S, httpd -S, nginx -T). Every combination of port and ServerName / ServerAlias (Apache) or Server (Nginx) must be unique. Merge duplicated entries in one vHost. If you use an IIS, extensionless files must be allowed in the /.well-known/acme-challenge subdirectory. Create a web.config in that directory. Content: <configuration><system.webServer><staticContent><mimeMap fileExtension="." mimeType="text/plain" /></staticContent></system.webServer></configuration>. If you have a redirect http ⇒ https, that's ok, Letsencrypt follows such redirects to port 80 / 443 (same or other server). There must be a certificate. But the certificate may be expired, self signed or with a not matching domain name. Checking the validation file Letsencrypt ignores such certificate errors. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
AGood: Every https result with status 200 and greater 1024 Bytes is compressed (gzip, deflate, br checked).
AGood: Every https result with status 200 has a minified Html-Content with a quota lower then 110 %.
AGood: Every https connection via port 443 supports the http/2 protocol via ALPN.
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
https://76.76.21.21/ 76.76.21.21
404
2.313 seconds
Warning: 404 needs more then one second
ADuration: 61313 milliseconds, 61.313 seconds

 

8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
tokenly.in
76.76.21.21
443
ok
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok
tokenly.in
76.76.21.21
443
ok
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok
http/2 via ALPN supported 
SNI required
Tls.1.2
no Tls.1.1
no Tls.1.0
http/2 via ALPN supported
SNI required
Tls.1.2
no Tls.1.1
no Tls.1.0
Chain - incomplete

1CN=tokenly.in


2CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US


76.76.21.21
76.76.21.21
443
Certificate/chain invalid and wrong name
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok

76.76.21.21
76.76.21.21
443
Certificate/chain invalid and wrong name
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok
no http/2 via ALPN 
Cert sent without SNI
Tls.1.2
no Tls.1.1
no Tls.1.0
no http/2 via ALPN
Cert sent without SNI
Tls.1.2
no Tls.1.1
no Tls.1.0

 

9. Certificates

1.
1.
CN=tokenly.in
06.09.2020
05.12.2020
1460 days expired
tokenly.in - 1 entry
1.
1.
CN=tokenly.in
06.09.2020

05.12.2020
1460 days expired


tokenly.in - 1 entry

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:031F69D16FF15E94049EC1FB87AD267AFB00
Thumbprint:533A8C19667B89824910B9EF7AFCCB4F8A95E76F
SHA256 / Certificate:8C30gzb0LG+/ArB+bMb04WWmbm3mTvIH+aX0h5ck2wM=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):541139ee45c5000f61985ef7cd6aa3d0d3a4fd4084a1d2712afb0adeb388a1cd
SHA256 hex / Subject Public Key Information (SPKI):541139ee45c5000f61985ef7cd6aa3d0d3a4fd4084a1d2712afb0adeb388a1cd
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://ocsp.int-x3.letsencrypt.org
OCSP - must staple:no
Certificate Transparency:yes
Enhanced Key Usage:Serverauthentifizierung (1.3.6.1.5.5.7.3.1), Clientauthentifizierung (1.3.6.1.5.5.7.3.2)




2.
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
17.03.2016
17.03.2021
1358 days expired


2.
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
17.03.2016

17.03.2021
1358 days expired




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:0A0141420000015385736A0B85ECA708
Thumbprint:E6A3B45B062D509B3382282D196EFE97D5956CCB
SHA256 / Certificate:JYR9Zo608E/dQLErawdAxWfafQJDCOtsLJb+QdneIY0=
SHA256 hex / Cert (DANE * 0 1):25847d668eb4f04fdd40b12b6b0740c567da7d024308eb6c2c96fe41d9de218d
SHA256 hex / PublicKey (DANE * 1 1):60b87575447dcba2a36b7d11ac09fb24a9db406fee12d2cc90180517616e8a18
SHA256 hex / Subject Public Key Information (SPKI):60b87575447dcba2a36b7d11ac09fb24a9db406fee12d2cc90180517616e8a18
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://isrg.trustid.ocsp.identrust.com
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:




3.
CN=DST Root CA X3, O=Digital Signature Trust Co.
30.09.2000
30.09.2021
1161 days expired


3.
CN=DST Root CA X3, O=Digital Signature Trust Co.
30.09.2000

30.09.2021
1161 days expired




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA-1 with RSA Encryption
Serial Number:44AFB080D6A327BA893039862EF8406B
Thumbprint:DAC9024F54D8F6DF94935FB1732638CA6AD77C13
SHA256 / Certificate:BocmAzGnJAPZCfEF5pvPDTLhvSST/8bZIG0RvNZ3Bzk=
SHA256 hex / Cert (DANE * 0 1):0687260331a72403d909f105e69bcf0d32e1bd2493ffc6d9206d11bcd6770739
SHA256 hex / PublicKey (DANE * 1 1):563b3caf8cfef34c2335caf560a7a95906e8488462eb75ac59784830df9e5b2b
SHA256 hex / Subject Public Key Information (SPKI):563b3caf8cfef34c2335caf560a7a95906e8488462eb75ac59784830df9e5b2b
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:




2.
1.
CN=zeit.co
09.10.2019
08.10.2021
1153 days expired

2.
1.
CN=zeit.co
09.10.2019

08.10.2021
1153 days expired




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:4FB49F37255171F86BE9675173F8814410A6962F
Thumbprint:BF7E1796AAD127CFC152AEC4D65422E0EA8C7188
SHA256 / Certificate:ruyrhWE5+DPAtERp3F9iMPrWH++q+Hq/cla0gbC+CBA=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):88bf1684463e23fee1d83ef8b4ed0ce13b7ea7dd903c6e0d2ec40a79485e2c94
SHA256 hex / Subject Public Key Information (SPKI):88bf1684463e23fee1d83ef8b4ed0ce13b7ea7dd903c6e0d2ec40a79485e2c94
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:


UntrustedRoot: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.


 

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

No Html-Content entries found. Only checked if https + status 200/401/403/404

 

12. Html-Parsing via https://validator.nu/ / https://validator.w3.org/nu/ (started 2024-09-28, 09:00, alpha)

  Unfortunately, there are differences between the first used validator.nu and validator.w3.org/nu/ - switched to validator.w3.org/nu/. Looks like some error messages (link - fetchpriority attribute) of validator.nu are obsolete, not seen in the w3.org-version and not found in the current specification: link may have a fetchpriority attribute.

Small Code update, wait one minute

 

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: dns1.registrar-servers.com, dns2.registrar-servers.com

 

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

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
dns1.registrar-servers.com
NS
b.gtld-servers.net (2001:503:231d::2:30)

Answer: edns4.ultradns.biz, edns4.ultradns.com, edns4.ultradns.net, edns4.ultradns.org

Answer: edns4.ultradns.com
2001:502:f3ff::204, 204.74.66.4
3
dns2.registrar-servers.com
NS
b.gtld-servers.net (2001:503:231d::2:30)

Answer: edns4.ultradns.biz, edns4.ultradns.com, edns4.ultradns.net, edns4.ultradns.org

Answer: edns4.ultradns.com
2001:502:f3ff::204, 204.74.66.4
4
biz
NS
b.root-servers.net (2001:500:200::b)

Answer: a.gtld.biz, b.gtld.biz, c.gtld.biz, e.gtld.biz, f.gtld.biz, k.gtld.biz
5
edns4.ultradns.biz
NS
a.gtld.biz (2001:502:ad09::30)

Answer: ari.alpha.aridns.net.au, ari.beta.aridns.net.au, ari.delta.aridns.net.au, ari.gamma.aridns.net.au, pdns196.ultradns.biz, pdns196.ultradns.co.uk, pdns196.ultradns.com, pdns196.ultradns.info, pdns196.ultradns.net, pdns196.ultradns.org

Answer: pdns196.ultradns.biz
156.154.66.196, 2610:a1:1015::e8
6
net
NS
d.root-servers.net (2001:500:2d::d)

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

Answer: ari.alpha.aridns.net.au, ari.beta.aridns.net.au, ari.delta.aridns.net.au, ari.gamma.aridns.net.au, pdns196.ultradns.biz, pdns196.ultradns.co.uk, pdns196.ultradns.com, pdns196.ultradns.info, pdns196.ultradns.net, pdns196.ultradns.org

Answer: pdns196.ultradns.net
156.154.65.196, 2610:a1:1014::e8
8
org
NS
j.root-servers.net (2001:503:c27::2:30)

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
9
edns4.ultradns.org
NS
a0.org.afilias-nst.info (2001:500:e::1)

Answer: ari.alpha.aridns.net.au, ari.beta.aridns.net.au, ari.delta.aridns.net.au, ari.gamma.aridns.net.au, pdns196.ultradns.biz, pdns196.ultradns.co.uk, pdns196.ultradns.com, pdns196.ultradns.info, pdns196.ultradns.net, pdns196.ultradns.org

Answer: pdns196.ultradns.org
156.154.67.196, 2001:502:4612::e8
10
au
NS
k.root-servers.net (2001:7fd::1)

Answer: a.au, c.au, d.au, m.au, n.au, q.au, r.au, s.au, t.au
11
ari.alpha.aridns.net.au
NS
a.au (2407:6e00:254:306::73)

Answer: q.au, r.au, s.au, t.au

Answer: q.au
2a01:8840:be::1, 65.22.196.1

Answer: r.au
2a01:8840:bf::1, 65.22.197.1

Answer: s.au
2a01:8840:c0::1, 65.22.198.1

Answer: t.au
2a01:8840:c1::1, 65.22.199.1
12
ari.beta.aridns.net.au
NS
a.au (2407:6e00:254:306::73)

Answer: q.au, r.au, s.au, t.au

Answer: q.au
2a01:8840:be::1, 65.22.196.1

Answer: r.au
2a01:8840:bf::1, 65.22.197.1

Answer: s.au
2a01:8840:c0::1, 65.22.198.1

Answer: t.au
2a01:8840:c1::1, 65.22.199.1
13
ari.delta.aridns.net.au
NS
a.au (2407:6e00:254:306::73)

Answer: q.au, r.au, s.au, t.au

Answer: q.au
2a01:8840:be::1, 65.22.196.1

Answer: r.au
2a01:8840:bf::1, 65.22.197.1

Answer: s.au
2a01:8840:c0::1, 65.22.198.1

Answer: t.au
2a01:8840:c1::1, 65.22.199.1
14
ari.gamma.aridns.net.au
NS
a.au (2407:6e00:254:306::73)

Answer: q.au, r.au, s.au, t.au

Answer: q.au
2a01:8840:be::1, 65.22.196.1

Answer: r.au
2a01:8840:bf::1, 65.22.197.1

Answer: s.au
2a01:8840:c0::1, 65.22.198.1

Answer: t.au
2a01:8840:c1::1, 65.22.199.1
15
uk
NS
m.root-servers.net (2001:dc3::35)

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
16
pdns196.ultradns.co.uk: 156.154.69.196, 2610:a1:1017::e8
NS
dns1.nic.uk (2a01:618:400::1)
17
pdns196.ultradns.com: 156.154.64.196, 2001:502:f3ff::e8
NS
b.gtld-servers.net (2001:503:231d::2:30)
18
info
NS
b.root-servers.net (2001:500:200::b)

Answer: a0.info.afilias-nst.info, a2.info.afilias-nst.info, b0.info.afilias-nst.org, b2.info.afilias-nst.org, c0.info.afilias-nst.info, d0.info.afilias-nst.org
19
pdns196.ultradns.info: 156.154.68.196, 2610:a1:1016::e8
NS
a0.info.afilias-nst.info (2001:500:19::1)
20
edns4.ultradns.biz: 204.74.67.4
A
pdns196.ultradns.biz (2610:a1:1015::e8)
21
edns4.ultradns.biz: 2610:a1:1015::204
AAAA
pdns196.ultradns.biz (2610:a1:1015::e8)
22
edns4.ultradns.net: 204.74.110.4
A
pdns196.ultradns.biz (2610:a1:1015::e8)
23
edns4.ultradns.net: 2610:a1:1014::204
AAAA
pdns196.ultradns.biz (2610:a1:1015::e8)
24
edns4.ultradns.org: 204.74.111.4
A
pdns196.ultradns.biz (2610:a1:1015::e8)
25
edns4.ultradns.org: 2001:502:4612::204
AAAA
pdns196.ultradns.biz (2610:a1:1015::e8)
26
ari.alpha.aridns.net.au: No A record found
A
q.au (2a01:8840:be::1)
27
ari.alpha.aridns.net.au: No AAAA record found
AAAA
q.au (2a01:8840:be::1)
28
ari.beta.aridns.net.au: No A record found
A
q.au (2a01:8840:be::1)
29
ari.beta.aridns.net.au: No AAAA record found
AAAA
q.au (2a01:8840:be::1)
30
ari.delta.aridns.net.au: No A record found
A
q.au (2a01:8840:be::1)
31
ari.delta.aridns.net.au: No AAAA record found
AAAA
q.au (2a01:8840:be::1)
32
ari.gamma.aridns.net.au: No A record found
A
q.au (2a01:8840:be::1)
33
ari.gamma.aridns.net.au: No AAAA record found
AAAA
q.au (2a01:8840:be::1)
34
dns1.registrar-servers.com: 156.154.132.200
A
edns4.ultradns.biz (2610:a1:1015::204)
35
dns1.registrar-servers.com: 2610:a1:1024::200
AAAA
edns4.ultradns.biz (2610:a1:1015::204)
36
dns2.registrar-servers.com: 156.154.133.200
A
edns4.ultradns.biz (2610:a1:1015::204)
37
dns2.registrar-servers.com: 2610:a1:1025::200
AAAA
edns4.ultradns.biz (2610:a1:1015::204)

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
tokenly.in
0

no CAA entry found
1
0
in
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
tokenly.in
google-site-verification=v3VkvKNxfjvw5MqwjHZH94X6izzKMW7rAZ7cWxrqWsY
ok
1
0
_acme-challenge.tokenly.in

Name Error - The domain name does not exist
1
0
_acme-challenge.tokenly.in.tokenly.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 open Ports <> 80 / 443 found, so no additional Ports checked.

 

 

Permalink: https://check-your-website.server-daten.de/?i=21f3c084-62b0-4347-b81f-15ab5103d4f6

 

Last Result: https://check-your-website.server-daten.de/?q=tokenly.in - 2020-09-23 16:25:14

 

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

 

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