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

...

skip EDNS-Check

skip Content-Check

check links

Connect failure - perhaps firewall

Checked:
03.06.2026 23:15:43

Older results

V - 04.04.2026 11:28:08

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
tivimate.in	A	103.176.90.137 Kwun Tong/Kwun Tong District/Hong Kong (HK) - Corebach Backbone SARL No Hostname found	yes	1	0
	AAAA		yes
www.tivimate.in		Name Error	yes	1	0
*.tivimate.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 38696, Flags 257 (SEP = Secure Entry Point)


	Public Key with Algorithm 8, KeyTag 54393, 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.2026, 00:00:00 +, Signature-Inception: 31.05.2026, 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	1 DS RR in the parent zone found


	DS with Algorithm 13, KeyTag 10094, DigestType 2 and Digest WCTumlXtcvDUbSw6UR85PwXvwn5zy9EAW+u8c0ArYYY=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner in., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 16.06.2026, 19:00:00 +, Signature-Inception: 03.06.2026, 18:00:00 +, KeyTag 54393, Signer-Name: (root)


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


	2 DNSKEY RR found


	Public Key with Algorithm 13, KeyTag 10094, Flags 257 (SEP = Secure Entry Point)


	Public Key with Algorithm 13, KeyTag 55175, Flags 256


	2 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner in., Algorithm: 13, 1 Labels, original TTL: 300 sec, Signature-expiration: 23.06.2026, 13:46:56 +, Signature-Inception: 24.05.2026, 20:56:09 +, KeyTag 10094, Signer-Name: in


	RRSIG-Owner in., Algorithm: 13, 1 Labels, original TTL: 300 sec, Signature-expiration: 26.06.2026, 05:41:24 +, Signature-Inception: 27.05.2026, 22:51:11 +, KeyTag 55175, Signer-Name: in


	• Status: Good - Algorithmus 13 and DNSKEY with KeyTag 10094 used to validate the DNSKEY RRSet


	• Status: Good - Algorithmus 13 and DNSKEY with KeyTag 55175 used to validate the DNSKEY RRSet


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

Zone: tivimate.in
tivimate.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 "se1bv48i3mu11k613sa8cb12n7ac36am" between the hashed NSEC3-owner "se0ce8jjukt85q5sv589t53sr3dl9el0" and the hashed NextOwner "se1d61bsdehge7n7dh8ljfcj08ff9ftl". So the parent zone confirmes the not-existence of a DS RR. Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner se0ce8jjukt85q5sv589t53sr3dl9el0.in., Algorithm: 13, 2 Labels, original TTL: 300 sec, Signature-expiration: 16.06.2026, 09:12:15 +, Signature-Inception: 18.05.2026, 12:41:58 +, KeyTag 55175, Signer-Name: in


	DS-Query in the parent zone sends valid NSEC3 RR with the Hash "u7smslveus494o8dr4h483un5spuc1tu" as Owner. That's the Hash of "in" with the NextHashedOwnerName "u7tsqcfm3blko8649tcsmrltu907ijup". So that domain name is the Closest Encloser of "tivimate.in". Opt-Out: True. Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner u7smslveus494o8dr4h483un5spuc1tu.in., Algorithm: 13, 2 Labels, original TTL: 300 sec, Signature-expiration: 17.06.2026, 11:03:00 +, Signature-Inception: 18.05.2026, 12:41:58 +, KeyTag 55175, Signer-Name: in


	2 DNSKEY RR found


	Public Key with Algorithm 13, KeyTag 2371, Flags 257 (SEP = Secure Entry Point)


	Public Key with Algorithm 13, KeyTag 34505, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner tivimate.in., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 14.07.2026, 00:45:32 +, Signature-Inception: 14.05.2026, 00:45:32 +, KeyTag 2371, Signer-Name: tivimate.in


	• Status: Good - Algorithmus 13 and DNSKEY with KeyTag 2371 used to validate the DNSKEY RRSet


	Error: DNSKEY 2371 signs DNSKEY RRset, but no confirming DS RR in the parent zone found. No chain of trust created.


	RRSIG Type 1 validates the A - Result: 103.176.90.137 Validated: RRSIG-Owner tivimate.in., Algorithm: 13, 2 Labels, original TTL: 59 sec, Signature-expiration: 04.06.2026, 22:15:56 +, Signature-Inception: 02.06.2026, 20:15:56 +, KeyTag 34505, Signer-Name: tivimate.in


	CNAME-Query sends a valid NSEC RR as result with the query name "tivimate.in" equal the NSEC-owner "tivimate.in" and the NextOwner "\000.tivimate.in". So the zone confirmes the not-existence of that CNAME RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, NS, SOA, 13, MX, TXT, AAAA, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, DNSKEY, TLSA, 53, HIP, CDS, CDNSKEY, 61, 64, 65, URI, CAA Validated: RRSIG-Owner tivimate.in., Algorithm: 13, 2 Labels, original TTL: 1800 sec, Signature-expiration: 04.06.2026, 22:15:57 +, Signature-Inception: 02.06.2026, 20:15:57 +, KeyTag 34505, Signer-Name: tivimate.in


	Status: Good. NoData-Proof required and found.


	TXT-Query sends a valid NSEC RR as result with the query name "tivimate.in" equal the NSEC-owner "tivimate.in" and the NextOwner "\000.tivimate.in". So the zone confirmes the not-existence of that TXT RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, NS, SOA, 13, MX, AAAA, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, DNSKEY, TLSA, 53, HIP, CDS, CDNSKEY, 61, 64, 65, URI, CAA Validated: RRSIG-Owner tivimate.in., Algorithm: 13, 2 Labels, original TTL: 1800 sec, Signature-expiration: 04.06.2026, 22:15:57 +, Signature-Inception: 02.06.2026, 20:15:57 +, KeyTag 34505, Signer-Name: tivimate.in


	Status: Good. NoData-Proof required and found.


	AAAA-Query sends a valid NSEC RR as result with the query name "tivimate.in" equal the NSEC-owner "tivimate.in" and the NextOwner "\000.tivimate.in". So the zone confirmes the not-existence of that AAAA RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, NS, SOA, 13, MX, TXT, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, DNSKEY, TLSA, 53, HIP, CDS, CDNSKEY, 61, 64, 65, URI, CAA Validated: RRSIG-Owner tivimate.in., Algorithm: 13, 2 Labels, original TTL: 1800 sec, Signature-expiration: 04.06.2026, 22:15:57 +, Signature-Inception: 02.06.2026, 20:15:57 +, KeyTag 34505, Signer-Name: tivimate.in


	Status: Good. NoData-Proof required and found.


	TLSA-Query (_443._tcp.tivimate.in) sends a valid NSEC RR as result with the query name "_443._tcp.tivimate.in" equal the NSEC-owner "_443._tcp.tivimate.in" and the NextOwner "\000._443._tcp.tivimate.in". So the zone confirmes the not-existence of that TLSA RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: RRSIG, NSEC, 128 Validated: RRSIG-Owner _443._tcp.tivimate.in., Algorithm: 13, 4 Labels, original TTL: 1800 sec, Signature-expiration: 04.06.2026, 22:15:57 +, Signature-Inception: 02.06.2026, 20:15:57 +, KeyTag 34505, Signer-Name: tivimate.in


	Status: Good. NoData-Proof required and found.


	CAA-Query sends a valid NSEC RR as result with the query name "tivimate.in" equal the NSEC-owner "tivimate.in" and the NextOwner "\000.tivimate.in". So the zone confirmes the not-existence of that CAA RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, NS, SOA, 13, MX, TXT, AAAA, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, DNSKEY, TLSA, 53, HIP, CDS, CDNSKEY, 61, 64, 65, URI Validated: RRSIG-Owner tivimate.in., Algorithm: 13, 2 Labels, original TTL: 1800 sec, Signature-expiration: 04.06.2026, 22:15:57 +, Signature-Inception: 02.06.2026, 20:15:57 +, KeyTag 34505, Signer-Name: tivimate.in


	Status: Good. NoData-Proof required and found.

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


	DS-Query in the parent zone has a valid NSEC RR as result with the domain name between the NSEC-Owner "www.tivimate.in" and the NextOwner "\000.www.tivimate.in". So the parent zone confirmes the non-existence of a DS RR. Bitmap: RRSIG, NSEC, 128

3. Name Servers

Domain	Nameserver	NS-IP
www.tivimate.in	• kianchau.ns.cloudflare.com
tivimate.in	• kianchau.ns.cloudflare.com / 67m127	108.162.195.179 Toronto/Ontario/Canada (CA) - Cloudflare, Inc.	•
	•	162.159.44.179 Budapest/Hungary (HU) - Cloudflare, Inc.	•
	•	172.64.35.179 Toronto/Ontario/Canada (CA) - Cloudflare, Inc.	•
	•	2606:4700:58::a29f:2cb3 Montreal/Quebec/Canada (CA) - Cloudflare, Inc.	•
	•	2803:f800:50::6ca2:c3b3 San José/Provincia de San José/Costa Rica (CR) - Cloudflare, Inc.	•
	•	2a06:98c1:50::ac40:23b3 London/England/United Kingdom (GB) - CloudFLARENET-EU	•
	• mckenzie.ns.cloudflare.com / 67m161	108.162.194.253 Toronto/Ontario/Canada (CA) - Cloudflare, Inc.	•
	•	162.159.38.253 Budapest/Hungary (HU) - Cloudflare, Inc.	•
	•	172.64.34.253 Toronto/Ontario/Canada (CA) - Cloudflare, Inc.	•
	•	2606:4700:50::a29f:26fd Montreal/Quebec/Canada (CA) - Cloudflare, Inc.	•
	•	2803:f800:50::6ca2:c2fd San José/Provincia de San José/Costa Rica (CR) - Cloudflare, Inc.	•
	•	2a06:98c1:50::ac40:22fd London/England/United Kingdom (GB) - CloudFLARENET-EU	•
in	• ns.trs-dns.com
	• ns01.trs-dns.com / fra01.dns1		•
	• ns01.trs-dns.net / fra02.dns2		•
	• ns1.registry.in / fra02.dns1		•
	• ns10.trs-dns.info / 2.fra.pch		•
	• ns10.trs-dns.org / 2.fra.pch		•
	• ns2.registry.in / fra01.dns2		•
	• ns3.registry.in / 2.fra.pch		•
	• ns4.registry.in / 1.fra.pch		•

4. SOA-Entries

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

Domain:	in
Zone-Name:	in
Primary:	ns.trs-dns.com
Mail:	trs-ops.tucows.com
Serial:	1780521061
Refresh:	1800
Retry:	900
Expire:	604800
TTL:	300
num Entries:	8

Domain:	tivimate.in
Zone-Name:	tivimate.in
Primary:	kianchau.ns.cloudflare.com
Mail:	dns.cloudflare.com
Serial:	2405928426
Refresh:	10000
Retry:	2400
Expire:	604800
TTL:	1800
num Entries:	12

Domain:	www.tivimate.in
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
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

show header:

Domainname	Http-Status	redirect	Sec.	G
• http://tivimate.in/c/ 103.176.90.137 No Compression used - 3077 / 8704 - 35.35 % possible	200	Html is minified: 132.10 %	0.056	H
Server: nginx
Date: Wed, 03 Jun 2026 21:16:27 GMT
Connection: keep-alive
ETag: "69a2683b-2200"
Cache-Control: no-store, must-revalidate, proxy-revalidate, no-cache
Pragma: no-cache
Accept-Ranges: bytes
Content-Type: text/html
Content-Length: 8704
Last-Modified: Sat, 28 Feb 2026 03:59:55 GMT
Expires: Wed, 03 Jun 2026 21:16:26 GMT

• https://tivimate.in/c/ 103.176.90.137	-102		1.073	V
ConnectionError (2, 0x80004005). Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. (103.176.90.137:443)

• http://tivimate.in/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 103.176.90.137 Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0	404	Other inline scripts (∑/total): 0/0	0.027	A
Not Found
Visible Content:
Server: nginx
Date: Wed, 03 Jun 2026 21:16:28 GMT
Transfer-Encoding: chunked
Connection: keep-alive
Content-Type: text/html
Content-Length: 1

• https://103.176.90.137/c/ 103.176.90.137	-102		1.076	V
ConnectionError (2, 0x80004005). Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. (103.176.90.137:443)

7. Comments

	1. General Results, most used to calculate the result
A	name "tivimate.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: 1281 (complete: 276475)
A	Good: All ip addresses are public addresses
	Warning: Only one ip address found: tivimate.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: tivimate.in has no ipv6 address.
A	Good: No asked Authoritative Name Server had a timeout
A	DNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
A	Good - only one version with Http-Status 200
A	Good: 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.
A	Good: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):0 complete Content-Type - header (2 urls)
	http://tivimate.in/c/ 103.176.90.137		Url with incomplete Content-Type - header - missing charset
	http://tivimate.in/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 103.176.90.137		Url with incomplete Content-Type - header - missing charset
H	Fatal error: No https - result with http-status 200, no encryption
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.
V	https://tivimate.in/c/ 103.176.90.137	-102	Connect failure - perhaps firewall
V	https://103.176.90.137/c/ 103.176.90.137	-102	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 tivimate.in, 1 ip addresses.
B	No _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Read the result of server-daten.de (Url-Checks, Comments, Connections and DomainServiceRecords) to see a complete definition. Domainname: _mta-sts.tivimate.in
	2. Header-Checks
U			No https result with http status 2 or 4 (standard-check) found, no header checked.
	3. DNS- and NameServer - Checks
A	Info:: 7 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
A	Info:: 7 Queries complete, 7 with IPv6, 0 with IPv4.
A	Good: All DNS Queries done via IPv6.
	Ok (4 - 8):: An average of 3.5 queries per domain name server required to find all ip addresses of all name servers.
A	Info:: 2 different Name Servers found: kianchau.ns.cloudflare.com, mckenzie.ns.cloudflare.com, 2 Name Servers included in Delegation: kianchau.ns.cloudflare.com, mckenzie.ns.cloudflare.com, 2 Name Servers included in 1 Zone definitions: kianchau.ns.cloudflare.com, mckenzie.ns.cloudflare.com, 1 Name Servers listed in SOA.Primary: kianchau.ns.cloudflare.com.
A	Good: Only one SOA.Primary Name Server found.: kianchau.ns.cloudflare.com.
A	Good: SOA.Primary Name Server included in the delegation set.: kianchau.ns.cloudflare.com.
A	Good: 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: kianchau.ns.cloudflare.com, mckenzie.ns.cloudflare.com
A	Good: All Name Server Domain Names have a Public Suffix.
A	Good: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
A	Good: All Name Server ip addresses are public.
A	Good: Minimal 2 different name servers (public suffix and public ip address) found: 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: cloudflare.com
A	Good: Name servers with different Country locations found: 2 Name Servers, 4 Countries: CA, CR, GB, HU
A	Info: Ipv4-Subnet-list: 6 Name Servers, 3 different subnets (first Byte): 108., 162., 172., 3 different subnets (first two Bytes): 108.162., 162.159., 172.64., 6 different subnets (first three Bytes): 108.162.194., 108.162.195., 162.159.38., 162.159.44., 172.64.34., 172.64.35.
A	Good: Name Server IPv4-addresses from different subnet found:
A	Info: IPv6-Subnet-list: 6 Name Servers with IPv6, 3 different subnets (first block): 2606:, 2803:, 2a06:, 3 different subnets (first two blocks): 2606:4700:, 2803:f800:, 2a06:98c1:, 4 different subnets (first three blocks): 2606:4700:0050:, 2606:4700:0058:, 2803:f800:0050:, 2a06:98c1:0050:, 4 different subnets (first four blocks): 2606:4700:0050:0000:, 2606:4700:0058:0000:, 2803:f800:0050:0000:, 2a06:98c1:0050:0000:
A	Good: Name Server IPv6 addresses from different subnets found.
A	Good: Nameserver supports TCP connections: 12 good Nameserver
A	Good: Nameserver supports Echo Capitalization: 12 good Nameserver
A	Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 12 good Nameserver
A	Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 12 good Nameserver
	Nameserver doesn't pass all EDNS-Checks: kianchau.ns.cloudflare.com: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
	Nameserver doesn't pass all EDNS-Checks: ns.trs-dns.com: 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.
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	Info: No img element found, no alt attribute checked
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
A	Duration: 56573 milliseconds, 56.573 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)

Issuer				last 7 days	active	num Certs
CN=WE1, O=Google Trust Services, C=US				0	1	2
CN=Sectigo Public Server Authentication CA DV E36, O=Sectigo Limited, C=GB				0	1	2

CertSpotter-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
14433192019 precert	CN=WE1, O=Google Trust Services, C=US	2026-04-09 03:30:52	2026-07-08 04:25:55	*.tivimate.in, tivimate.in - 2 entries
14231381059 leaf cert	CN=Sectigo Public Server Authentication CA DV E36, O=Sectigo Limited, C=GB	2026-03-23 00:00:00	2026-06-21 03:41:54	*.tivimate.in, tivimate.in - 2 entries
13731738687 precert	CN=WE1, O=Google Trust Services, C=US	2026-02-09 03:12:19	2026-05-10 04:09:59	*.tivimate.in, tivimate.in - 2 entries
13512790426 leaf cert	CN=Sectigo Public Server Authentication CA DV E36, O=Sectigo Limited, C=GB	2026-01-21 00:00:00	2026-04-21 09:25:26	*.tivimate.in, tivimate.in - 2 entries

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

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

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

No https result http status 200 and Content-Type text/html or text/xml found, no Html-Parsing - Check

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: kianchau.ns.cloudflare.com, mckenzie.ns.cloudflare.com

QNr.	Domain	Type	NS used
1	com	NS	a.root-servers.net (2001:503:ba3e::2:30)
	Answer: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net
2	kianchau.ns.cloudflare.com	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: ns3.cloudflare.com, ns4.cloudflare.com, ns5.cloudflare.com, ns6.cloudflare.com, ns7.cloudflare.com
	Answer: ns3.cloudflare.com 162.159.0.33, 162.159.7.226, 2400:cb00:2049:1::a29f:21, 2400:cb00:2049:1::a29f:7e2
	Answer: ns4.cloudflare.com 162.159.1.33, 162.159.8.55, 2400:cb00:2049:1::a29f:121, 2400:cb00:2049:1::a29f:837
	Answer: ns5.cloudflare.com 162.159.2.9, 162.159.9.55, 2400:cb00:2049:1::a29f:209, 2400:cb00:2049:1::a29f:937
	Answer: ns6.cloudflare.com 162.159.3.11, 162.159.5.6, 2400:cb00:2049:1::a29f:30b, 2400:cb00:2049:1::a29f:506
	Answer: ns7.cloudflare.com 162.159.4.8, 162.159.6.6, 2400:cb00:2049:1::a29f:408, 2400:cb00:2049:1::a29f:606
3	mckenzie.ns.cloudflare.com	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: ns3.cloudflare.com, ns4.cloudflare.com, ns5.cloudflare.com, ns6.cloudflare.com, ns7.cloudflare.com
	Answer: ns3.cloudflare.com 162.159.0.33, 162.159.7.226, 2400:cb00:2049:1::a29f:21, 2400:cb00:2049:1::a29f:7e2
	Answer: ns4.cloudflare.com 162.159.1.33, 162.159.8.55, 2400:cb00:2049:1::a29f:121, 2400:cb00:2049:1::a29f:837
	Answer: ns5.cloudflare.com 162.159.2.9, 162.159.9.55, 2400:cb00:2049:1::a29f:209, 2400:cb00:2049:1::a29f:937
	Answer: ns6.cloudflare.com 162.159.3.11, 162.159.5.6, 2400:cb00:2049:1::a29f:30b, 2400:cb00:2049:1::a29f:506
	Answer: ns7.cloudflare.com 162.159.4.8, 162.159.6.6, 2400:cb00:2049:1::a29f:408, 2400:cb00:2049:1::a29f:606
4	kianchau.ns.cloudflare.com: 108.162.195.179, 162.159.44.179, 172.64.35.179	A	ns3.cloudflare.com (2400:cb00:2049:1::a29f:21)
5	kianchau.ns.cloudflare.com: 2606:4700:58::a29f:2cb3, 2803:f800:50::6ca2:c3b3, 2a06:98c1:50::ac40:23b3	AAAA	ns3.cloudflare.com (2400:cb00:2049:1::a29f:21)
6	mckenzie.ns.cloudflare.com: 108.162.194.253, 162.159.38.253, 172.64.34.253	A	ns3.cloudflare.com (2400:cb00:2049:1::a29f:21)
7	mckenzie.ns.cloudflare.com: 2606:4700:50::a29f:26fd, 2803:f800:50::6ca2:c2fd, 2a06:98c1:50::ac40:22fd	AAAA	ns3.cloudflare.com (2400:cb00:2049:1::a29f:21)

14. CAA - Entries

Domainname	flag	Name	Value	∑ Queries	∑ Timeout
tivimate.in	0		no CAA entry found	1	0
in	0		no CAA entry found	1	0

15. TXT - Entries

Domainname	TXT Entry	Status	∑ Queries
tivimate.in		ok	1
_acme-challenge.tivimate.in	D42skiTJ6Pyq8L5mlJjM6_GVQj2oTE9nC3PIMpurp6w	looks good, correct length, correct characters	1
_acme-challenge.tivimate.in	rzNLWRx4HMqIICzXH7gT7TsHU2Dtl7KIevPIt8eZU-o	looks good, correct length, correct characters	1
_acme-challenge.tivimate.in.tivimate.in		Name Error - The domain name does not exist	1

16. DomainService - Entries

No DomainServiceEntries entries found

17. Cipher Suites

No results

18. Portchecks

Domain	IP	Port	Description	Result	Answer
tivimate.in	103.176.90.137	21	FTP

tivimate.in	103.176.90.137	21	FTP
tivimate.in	103.176.90.137	22	SSH

tivimate.in	103.176.90.137	22	SSH
tivimate.in	103.176.90.137	25	SMTP

tivimate.in	103.176.90.137	25	SMTP
tivimate.in	103.176.90.137	53	DNS

tivimate.in	103.176.90.137	53	DNS
tivimate.in	103.176.90.137	110	POP3

tivimate.in	103.176.90.137	110	POP3
tivimate.in	103.176.90.137	143	IMAP

tivimate.in	103.176.90.137	143	IMAP
tivimate.in	103.176.90.137	465	SMTP (encrypted)

tivimate.in	103.176.90.137	465	SMTP (encrypted)
tivimate.in	103.176.90.137	587	SMTP (encrypted, submission)

tivimate.in	103.176.90.137	587	SMTP (encrypted, submission)
tivimate.in	103.176.90.137	993	IMAP (encrypted)

tivimate.in	103.176.90.137	993	IMAP (encrypted)
tivimate.in	103.176.90.137	995	POP3 (encrypted)

tivimate.in	103.176.90.137	995	POP3 (encrypted)
tivimate.in	103.176.90.137	1433	MS SQL

tivimate.in	103.176.90.137	1433	MS SQL
tivimate.in	103.176.90.137	2082	cPanel (http)	open
http://103.176.90.137:2082/ Http-Status: 401 Unauthorized
tivimate.in	103.176.90.137	2082	cPanel (http)	open	http://103.176.90.137:2082/ Http-Status: 401 Unauthorized
tivimate.in	103.176.90.137	2083	cPanel (https)

tivimate.in	103.176.90.137	2083	cPanel (https)
tivimate.in	103.176.90.137	2086	WHM (http)

tivimate.in	103.176.90.137	2086	WHM (http)
tivimate.in	103.176.90.137	2087	WHM (https)

tivimate.in	103.176.90.137	2087	WHM (https)
tivimate.in	103.176.90.137	2089	cPanel Licensing

tivimate.in	103.176.90.137	2089	cPanel Licensing
tivimate.in	103.176.90.137	2095	cPanel Webmail (http)

tivimate.in	103.176.90.137	2095	cPanel Webmail (http)
tivimate.in	103.176.90.137	2096	cPanel Webmail (https)

tivimate.in	103.176.90.137	2096	cPanel Webmail (https)
tivimate.in	103.176.90.137	2222	DirectAdmin (http)

tivimate.in	103.176.90.137	2222	DirectAdmin (http)
tivimate.in	103.176.90.137	2222	DirectAdmin (https)

tivimate.in	103.176.90.137	2222	DirectAdmin (https)
tivimate.in	103.176.90.137	3306	mySql

tivimate.in	103.176.90.137	3306	mySql
tivimate.in	103.176.90.137	5224	Plesk Licensing

tivimate.in	103.176.90.137	5224	Plesk Licensing
tivimate.in	103.176.90.137	5432	PostgreSQL

tivimate.in	103.176.90.137	5432	PostgreSQL
tivimate.in	103.176.90.137	8080	Ookla Speedtest (http)

tivimate.in	103.176.90.137	8080	Ookla Speedtest (http)
tivimate.in	103.176.90.137	8080	Ookla Speedtest (https)

tivimate.in	103.176.90.137	8080	Ookla Speedtest (https)
tivimate.in	103.176.90.137	8083	VestaCP http

tivimate.in	103.176.90.137	8083	VestaCP http
tivimate.in	103.176.90.137	8083	VestaCP https

tivimate.in	103.176.90.137	8083	VestaCP https
tivimate.in	103.176.90.137	8443	Plesk Administration (https)

tivimate.in	103.176.90.137	8443	Plesk Administration (https)
tivimate.in	103.176.90.137	8447	Plesk Installer + Updates

tivimate.in	103.176.90.137	8447	Plesk Installer + Updates
tivimate.in	103.176.90.137	8880	Plesk Administration (http)

tivimate.in	103.176.90.137	8880	Plesk Administration (http)
tivimate.in	103.176.90.137	10000	Webmin (http)

tivimate.in	103.176.90.137	10000	Webmin (http)
tivimate.in	103.176.90.137	10000	Webmin (https)

tivimate.in	103.176.90.137	10000	Webmin (https)

Permalink: https://check-your-website.server-daten.de/?i=f6b0b581-85bd-41a9-850f-e7e42b7ad53b

Last Result: https://check-your-website.server-daten.de/?q=tivimate.in%2Fc%2F - 2026-06-03 23:15:43

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

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