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

...

skip EDNS-Check

skip Content-Check

check links

Timeout

Checked:
20.06.2025 06:43:29

Older results

T - 10.06.2025 08:20:08

T - 05.06.2025 13:35:20

T - 04.06.2025 11:47:27

T - 04.06.2025 08:48:39

T - 30.05.2025 07:35:26

T - 29.05.2025 13:14:58

T - 22.05.2025 08:12:00

T - 13.05.2025 13:00:14

T - 09.05.2025 13:58:04

T - 01.05.2025 07:49:30

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
consumablessad.up.gov.in			yes	2	1
www.consumablessad.up.gov.in			yes	2	0
consumablessad.up.gov.in	A	164.100.181.144 New Delhi/National Capital Territory of Delhi/India (IN) - National Informatics Centre No Hostname found	no
	A	220.158.147.58 Jodhpur/Rajasthan/India (IN) - Powergrid Teleservices Limited No Hostname found	no
www.consumablessad.up.gov.in	A	164.100.181.144 New Delhi/National Capital Territory of Delhi/India (IN) - National Informatics Centre No Hostname found	no
	A	220.158.147.58 Jodhpur/Rajasthan/India (IN) - Powergrid Teleservices Limited No Hostname found	no
*.up.gov.in	A	Name Error	yes
	AAAA	Name Error	yes
	CNAME	Name Error	yes
*.consumablessad.up.gov.in	A		yes
	AAAA		yes
	CNAME		yes

2. DNSSEC

Zone (*)	DNSSEC - Informations

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


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


	• Status: Valid because published


	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 53148, 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.2025, 00:00:00 +, Signature-Inception: 10.06.2025, 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 8, KeyTag 48140, DigestType 2 and Digest XuR0jCBpuZyYvDmlaIGmSvF8x4cR5il9Q6xaT0tbtuU=


	1 RRSIG RR to validate DS RR found


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


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


	4 DNSKEY RR found


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


	Public Key with Algorithm 8, KeyTag 41271, Flags 256


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


	Public Key with Algorithm 13, KeyTag 55175, Flags 256


	4 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner in., Algorithm: 13, 1 Labels, original TTL: 300 sec, Signature-expiration: 18.07.2025, 10:54:20 +, Signature-Inception: 19.06.2025, 22:36:16 +, KeyTag 10094, Signer-Name: in


	RRSIG-Owner in., Algorithm: 8, 1 Labels, original TTL: 300 sec, Signature-expiration: 19.07.2025, 08:35:19 +, Signature-Inception: 19.06.2025, 22:36:16 +, KeyTag 41271, Signer-Name: in


	RRSIG-Owner in., Algorithm: 8, 1 Labels, original TTL: 300 sec, Signature-expiration: 18.07.2025, 18:54:35 +, Signature-Inception: 19.06.2025, 22:36:16 +, KeyTag 48140, Signer-Name: in


	RRSIG-Owner in., Algorithm: 13, 1 Labels, original TTL: 300 sec, Signature-expiration: 18.07.2025, 19:29:25 +, Signature-Inception: 19.06.2025, 22:36:16 +, KeyTag 55175, Signer-Name: in


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


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


	• Status: Good - Algorithmus 8 and DNSKEY with KeyTag 48140 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 8, KeyTag 48140, DigestType 2 and Digest "XuR0jCBpuZyYvDmlaIGmSvF8x4cR5il9Q6xaT0tbtuU=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: gov.in
gov.in	2 DS RR in the parent zone found


	DS with Algorithm 8, KeyTag 60952, DigestType 2 and Digest W+aey0wKZincmSv++RtFWbaEQ2apYyhObAHBmNksDuE=


	DS with Algorithm 13, KeyTag 52194, DigestType 2 and Digest Tc2n5kuuC6vP6ozK4L517wjqNx6v3p64apwTBNFCOC0=


	2 RRSIG RR to validate DS RR found


	RRSIG-Owner gov.in., Algorithm: 8, 2 Labels, original TTL: 900 sec, Signature-expiration: 19.07.2025, 10:12:17 +, Signature-Inception: 19.06.2025, 16:11:13 +, KeyTag 41271, Signer-Name: in


	RRSIG-Owner gov.in., Algorithm: 13, 2 Labels, original TTL: 900 sec, Signature-expiration: 18.07.2025, 17:29:31 +, Signature-Inception: 19.06.2025, 22:36:16 +, KeyTag 55175, Signer-Name: in


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


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


	4 DNSKEY RR found


	Public Key with Algorithm 13, KeyTag 22437, Flags 256


	Public Key with Algorithm 8, KeyTag 48544, Flags 256


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


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


	4 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner gov.in., Algorithm: 13, 2 Labels, original TTL: 300 sec, Signature-expiration: 18.07.2025, 01:16:13 +, Signature-Inception: 19.06.2025, 13:56:10 +, KeyTag 22437, Signer-Name: gov.in


	RRSIG-Owner gov.in., Algorithm: 8, 2 Labels, original TTL: 300 sec, Signature-expiration: 17.07.2025, 18:50:06 +, Signature-Inception: 19.06.2025, 13:56:10 +, KeyTag 48544, Signer-Name: gov.in


	RRSIG-Owner gov.in., Algorithm: 13, 2 Labels, original TTL: 300 sec, Signature-expiration: 18.07.2025, 05:07:24 +, Signature-Inception: 19.06.2025, 13:56:10 +, KeyTag 52194, Signer-Name: gov.in


	RRSIG-Owner gov.in., Algorithm: 8, 2 Labels, original TTL: 300 sec, Signature-expiration: 17.07.2025, 21:16:13 +, Signature-Inception: 19.06.2025, 13:56:10 +, KeyTag 60952, Signer-Name: gov.in


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


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


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


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


	• Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 52194, DigestType 2 and Digest "Tc2n5kuuC6vP6ozK4L517wjqNx6v3p64apwTBNFCOC0=" 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 60952, DigestType 2 and Digest "W+aey0wKZincmSv++RtFWbaEQ2apYyhObAHBmNksDuE=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: up.gov.in
up.gov.in	0 DS RR in the parent zone found


	DS-Query in the parent zone sends valid NSEC3 RR with the Hash "npk19skvsdmju264d4ono0khqf7eafqv" as Owner. That's the Hash of "gov.in" with the NextHashedOwnerName "p0kkr4bmbgljdokbgbi0kdm39dsm0ea4". So that domain name is the Closest Encloser of "up.gov.in". Opt-Out: True. Bitmap: NS, SOA, MX, TXT, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner npk19skvsdmju264d4ono0khqf7eafqv.gov.in., Algorithm: 13, 3 Labels, original TTL: 300 sec, Signature-expiration: 18.07.2025, 14:41:38 +, Signature-Inception: 19.06.2025, 13:56:10 +, KeyTag 22437, Signer-Name: gov.in


	DS-Query in the parent zone sends valid NSEC3 RR with the Hash "npk19skvsdmju264d4ono0khqf7eafqv" as Owner. That's the Hash of "gov.in" with the NextHashedOwnerName "p0kkr4bmbgljdokbgbi0kdm39dsm0ea4". So that domain name is the Closest Encloser of "up.gov.in". Opt-Out: True. Bitmap: NS, SOA, MX, TXT, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner npk19skvsdmju264d4ono0khqf7eafqv.gov.in., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 26.06.2025, 14:03:37 +, Signature-Inception: 28.05.2025, 18:43:39 +, KeyTag 48544, Signer-Name: gov.in


	The ClosestEncloser says, that "*.gov.in" with the Hash "u5ugp5fqd4j2g2csniuduq0c33smgisg" is a possible Wildcard of the DS Query Name. But the DS-Query in the parent zone sends a valid NSEC3 RR With the owner "rtn55db3nk19h252q98n471ja9mtndjv" and the Next Owner "33tlr274o6kab5hdfsvo5h5se644jpet", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: True Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner rtn55db3nk19h252q98n471ja9mtndjv.gov.in., Algorithm: 13, 3 Labels, original TTL: 300 sec, Signature-expiration: 19.07.2025, 09:18:29 +, Signature-Inception: 19.06.2025, 13:56:10 +, KeyTag 22437, Signer-Name: gov.in


	The ClosestEncloser says, that "*.gov.in" with the Hash "u5ugp5fqd4j2g2csniuduq0c33smgisg" is a possible Wildcard of the DS Query Name. But the DS-Query in the parent zone sends a valid NSEC3 RR With the owner "rtn55db3nk19h252q98n471ja9mtndjv" and the Next Owner "33tlr274o6kab5hdfsvo5h5se644jpet", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: True Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner rtn55db3nk19h252q98n471ja9mtndjv.gov.in., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 26.06.2025, 21:22:37 +, Signature-Inception: 28.05.2025, 18:43:39 +, KeyTag 48544, Signer-Name: gov.in


	0 DNSKEY RR found




Zone: consumablessad.up.gov.in
consumablessad.up.gov.in	0 DS RR in the parent zone found


	0 DNSKEY RR found




Zone: www.consumablessad.up.gov.in
www.consumablessad.up.gov.in	0 DS RR in the parent zone found

3. Name Servers

Domain	Nameserver	NS-IP
consumablessad.up.gov.in	• ns1.consumablessad.up.gov.in
	• ns2.consumablessad.up.gov.in
up.gov.in	• ns1.nic.in	164.100.11.11 Delhi/National Capital Territory of Delhi/India (IN) - National Informatics Centre
	X ns10.nic.in	2001:4408:10::10 New Delhi/National Capital Territory of Delhi/India (IN) - National Informatics Centre
	• ns2.nic.in	164.100.105.30 New Delhi/National Capital Territory of Delhi/India (IN) - National Informatics Centre	•
	• ns7.nic.in	164.100.4.10 Delhi/National Capital Territory of Delhi/India (IN) - National Informatics Centre	•
gov.in	• ns.trs-dns.com
	• ns01.trs-dns.com / fra01.dns1.tucows.net	64.96.1.1 East Irvine/California/United States (US) - Tucows.com Co.	•
	•	2620:57:4001::1 New Delhi/National Capital Territory of Delhi/India (IN) - Tucows.com Co.	•
	• ns01.trs-dns.net / fra02.dns2.tucows.net	64.96.2.1 East Irvine/California/United States (US) - Tucows.com Co.	•
	•	2620:57:4002::1 New Delhi/National Capital Territory of Delhi/India (IN) - Tucows.com Co.	•
	• ns10.trs-dns.info / 2.fra.pch	64.78.204.1 New York/United States (US) - WoodyNet, Inc.	•
	•	2620:171:812:1534:8::1 Berkeley/California/United States (US) - WoodyNet, Inc.	•
	• ns10.trs-dns.org / 2.fra.pch	64.78.205.1 New York/United States (US) - WoodyNet, Inc.	•
	•	2620:171:813:1534:8::1 Berkeley/California/United States (US) - WoodyNet, Inc.	•
in	• ns.trs-dns.com
	• ns01.trs-dns.com / fra01.dns1.tucows.net		•
	• ns01.trs-dns.net / fra02.dns2.tucows.net		•
	• ns10.trs-dns.info / 1.fra.pch		•
	• ns10.trs-dns.org / 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:	1750394461
Refresh:	1800
Retry:	900
Expire:	604800
TTL:	300
num Entries:	4

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

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

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

Domain:	up.gov.in
Zone-Name:	up.gov.in
Primary:	ns2.nic.in
Mail:	nsadmin.nic.in
Serial:	2025061802
Refresh:	10800
Retry:	1800
Expire:	1209600
TTL:	14400
num Entries:	3

Domain:	consumablessad.up.gov.in
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:	2

5. Screenshots

No Screenshot listed, because no url-check with https + http status 200-299, 400-599 + not-ACME-check found.

6. Url-Checks

Domainname	Http-Status	Sec.	G
• http://consumablessad.up.gov.in/ 164.100.181.144	-14	10.043	T
Timeout - The operation has timed out.

• http://consumablessad.up.gov.in/ 220.158.147.58	-14	10.033	T
Timeout - The operation has timed out.

• http://www.consumablessad.up.gov.in/ 164.100.181.144	-14	10.023	T
Timeout - The operation has timed out.

• http://www.consumablessad.up.gov.in/ 220.158.147.58	-14	10.113	T
Timeout - The operation has timed out.

• https://consumablessad.up.gov.in/ 164.100.181.144	-14	10.087	T
Timeout - The operation has timed out.

• https://consumablessad.up.gov.in/ 220.158.147.58	-14	10.023	T
Timeout - The operation has timed out.

• https://www.consumablessad.up.gov.in/ 164.100.181.144	-14	10.027	T
Timeout - The operation has timed out.

• https://www.consumablessad.up.gov.in/ 220.158.147.58	-14	10.030	T
Timeout - The operation has timed out.

• http://consumablessad.up.gov.in/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 164.100.181.144	-14	10.030	T
Timeout - The operation has timed out.
Visible Content:

• http://consumablessad.up.gov.in/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 220.158.147.58	-14	10.017	T
Timeout - The operation has timed out.
Visible Content:

• http://www.consumablessad.up.gov.in/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 164.100.181.144	-14	10.034	T
Timeout - The operation has timed out.
Visible Content:

• http://www.consumablessad.up.gov.in/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 220.158.147.58	-14	10.020	T
Timeout - The operation has timed out.
Visible Content:

• https://220.158.147.58/ 220.158.147.58	-14	10.030	T
Timeout - The operation has timed out.

• https://164.100.181.144/ 164.100.181.144	-14	10.026	T
Timeout - The operation has timed out.

7. Comments

	1. General Results, most used to calculate the result
A	name "consumablessad.up.gov.in" is subdomain, public suffix is ".gov.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: 1234 (complete: 271405)
A	Good: All ip addresses are public addresses
	HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
X	Fatal error: Nameserver doesn't support TCP connection: ns1.nic.in / 164.100.11.11: Timeout
X	Fatal error: Nameserver doesn't support TCP connection: ns10.nic.in / 2001:4408:10::10: Fatal error (-14). Details: Unable to read data from the transport connection: Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat.. - Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat
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.consumablessad.up.gov.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:: 13 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers.
A	Info:: 13 Queries complete, 5 with IPv6, 8 with IPv4.
	Warning: Only some DNS Queries done via ipv6. IPv6 is the future, so the name servers of your name servers should have ipv6 addresses.
	Ok (4 - 8):: An average of 3.3 queries per domain name server required to find all ip addresses of all name servers.
A	Info:: 4 different Name Servers found: ns1.nic.in, ns10.nic.in, ns2.nic.in, ns7.nic.in, 4 Name Servers included in Delegation: ns1.nic.in, ns10.nic.in, ns2.nic.in, ns7.nic.in, 4 Name Servers included in 2 Zone definitions: ns1.nic.in, ns10.nic.in, ns2.nic.in, ns7.nic.in, 1 Name Servers listed in SOA.Primary: ns2.nic.in.
A	Good: Only one SOA.Primary Name Server found.: ns2.nic.in.
A	Good: SOA.Primary Name Server included in the delegation set.: ns2.nic.in.
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	Info: Ipv4-Subnet-list: 3 Name Servers, 1 different subnets (first Byte): 164., 1 different subnets (first two Bytes): 164.100., 3 different subnets (first three Bytes): 164.100.105., 164.100.11., 164.100.4.
A	Good: Name Server IPv4-addresses from different subnet found:
A	Info: IPv6-Subnet-list: 1 Name Servers with IPv6, 1 different subnets (first block): 2001:, 1 different subnets (first two blocks): 2001:4408:, 1 different subnets (first three blocks): 2001:4408:0010:, 1 different subnets (first four blocks): 2001:4408:0010:0000:
	Fatal: All Name Server IPv6 addresses from the same subnet.
X	Nameserver Timeout checking Echo Capitalization: ns10.nic.in / 2001:4408:10::10
X	Nameserver Timeout checking EDNS512: ns10.nic.in / 2001:4408:10::10
	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.
	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.
	Nameserver doesn't pass all EDNS-Checks: ns1.consumablessad.up.gov.in: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
	Nameserver doesn't pass all EDNS-Checks: ns10.nic.in / 2001:4408:10::10: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout.
	Nameserver doesn't pass all EDNS-Checks: ns2.consumablessad.up.gov.in: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
A	Good: All SOA have the same Serial Number
A	Good: CAA entries found, creating certificate is limited: sectigo.com is allowed to create certificates
	4. Content- and Performance-critical Checks
	http://consumablessad.up.gov.in/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 164.100.181.144	-14	Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
	http://consumablessad.up.gov.in/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 220.158.147.58	-14	Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
	http://www.consumablessad.up.gov.in/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 164.100.181.144	-14	Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
	http://www.consumablessad.up.gov.in/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 220.158.147.58	-14	Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. 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: 365396 milliseconds, 365.396 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=emSign SSL CA - G1, OU=emSign PKI, O=eMudhra Technologies Limited, C=IN				0	1	1

CertSpotter-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
8214878301 precert	CN=emSign SSL CA - G1, OU=emSign PKI, O=eMudhra Technologies Limited, C=IN	2024-09-19 11:38:05	2025-10-14 11:38:05	consumablessad.up.gov.in - 1 entries

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

Issuer				last 7 days	active	num Certs
CN=Sectigo RSA Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, C=GB, ST=Greater Manchester				0	0	3
CN=GlobalSign GCC R3 DV TLS CA 2020, O=GlobalSign nv-sa, C=BE				0	0	3
CN=emSign SSL CA - G1, OU=emSign PKI, O=eMudhra Technologies Limited, C=IN				0	1	1

CRT-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
15065523967 leaf cert	CN=emSign SSL CA - G1, OU=emSign PKI, O=eMudhra Technologies Limited, C=IN	2024-09-19 09:38:05	2025-10-14 09:38:05	consumablessad.up.gov.in 1 entries
14062122898 leaf cert	CN=Sectigo RSA Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, C=GB, ST=Greater Manchester	2024-08-08 22:00:00	2024-09-08 21:59:59	consumablessad.up.gov.in, www.consumablessad.up.gov.in 2 entries
13694808569 leaf cert	CN=Sectigo RSA Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, C=GB, ST=Greater Manchester	2024-07-10 22:00:00	2024-08-10 21:59:59	consumablessad.up.gov.in, www.consumablessad.up.gov.in 2 entries
13378169083 leaf cert	CN=Sectigo RSA Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, C=GB, ST=Greater Manchester	2024-06-12 22:00:00	2024-07-13 21:59:59	consumablessad.up.gov.in 1 entries
11362568171 precert	CN=GlobalSign GCC R3 DV TLS CA 2020, O=GlobalSign nv-sa, C=BE	2023-12-09 08:57:03	2024-05-13 06:52:49	www.consumablessad.up.gov.in 1 entries
11362502057 precert	CN=GlobalSign GCC R3 DV TLS CA 2020, O=GlobalSign nv-sa, C=BE	2023-12-09 08:47:02	2024-05-13 06:52:49	www.consumablessad.up.gov.in 1 entries
9125924077 precert	CN=GlobalSign GCC R3 DV TLS CA 2020, O=GlobalSign nv-sa, C=BE	2023-04-12 06:52:50	2024-05-13 06:52:49	www.consumablessad.up.gov.in 1 entries

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: ns1.nic.in, ns10.nic.in, ns2.nic.in, ns7.nic.in

QNr.	Domain	Type	NS used
1	in	NS	e.root-servers.net (2001:500:a8::e)
	Answer: ns01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.info, ns10.trs-dns.org
2	ns1.nic.in	NS	ns01.trs-dns.com (2620:57:4001::1)
	Answer: nicnet.nic.in, ns4.nic.in, ns6.nic.in, ns8.nic.in
	Answer: nicnet.nic.in 164.100.105.105
	Answer: ns4.nic.in 164.100.11.2
	Answer: ns6.nic.in 164.100.4.2
	Answer: ns8.nic.in 2001:4408:10::11
3	ns10.nic.in	NS	ns01.trs-dns.com (2620:57:4001::1)
	Answer: nicnet.nic.in, ns4.nic.in, ns6.nic.in, ns8.nic.in
	Answer: nicnet.nic.in 164.100.105.105
	Answer: ns4.nic.in 164.100.11.2
	Answer: ns6.nic.in 164.100.4.2
	Answer: ns8.nic.in 2001:4408:10::11
4	ns2.nic.in	NS	ns01.trs-dns.com (2620:57:4001::1)
	Answer: nicnet.nic.in, ns4.nic.in, ns6.nic.in, ns8.nic.in
	Answer: nicnet.nic.in 164.100.105.105
	Answer: ns4.nic.in 164.100.11.2
	Answer: ns6.nic.in 164.100.4.2
	Answer: ns8.nic.in 2001:4408:10::11
5	ns7.nic.in	NS	ns01.trs-dns.com (2620:57:4001::1)
	Answer: nicnet.nic.in, ns4.nic.in, ns6.nic.in, ns8.nic.in
	Answer: nicnet.nic.in 164.100.105.105
	Answer: ns4.nic.in 164.100.11.2
	Answer: ns6.nic.in 164.100.4.2
	Answer: ns8.nic.in 2001:4408:10::11
6	ns1.nic.in: 164.100.11.11	A	nicnet.nic.in (164.100.105.105)
7	ns1.nic.in: No AAAA record found	AAAA	nicnet.nic.in (164.100.105.105)
8	ns10.nic.in: No A record found	A	nicnet.nic.in (164.100.105.105)
9	ns10.nic.in: 2001:4408:10::10	AAAA	nicnet.nic.in (164.100.105.105)
10	ns2.nic.in: 164.100.105.30	A	nicnet.nic.in (164.100.105.105)
11	ns2.nic.in: No AAAA record found	AAAA	nicnet.nic.in (164.100.105.105)
12	ns7.nic.in: 164.100.4.10	A	nicnet.nic.in (164.100.105.105)
13	ns7.nic.in: No AAAA record found	AAAA	nicnet.nic.in (164.100.105.105)

14. CAA - Entries

Domainname	flag	Name	Value	∑ Queries	∑ Timeout
consumablessad.up.gov.in				2	0
up.gov.in	5	issue	sectigo.com	2	1
gov.in	0		no CAA entry found	1	0
in	0		no CAA entry found	1	0

15. TXT - Entries

Domainname	TXT Entry	Status	∑ Queries	∑ Timeout
up.gov.in	v=spf1 include:mgovcloud.in mx ip4:164.100.14.0/24 ip4:164.100.2.0/24 ip4:164.100.10.0/24 ip4:164.100.15.0/24 ~all	ok	1	0
_acme-challenge.consumablessad.up.gov.in.up.gov.in		Name Error - The domain name does not exist	1	0

16. DomainService - Entries

No DomainServiceEntries entries found

17. Cipher Suites

No results

18. Portchecks

No open Ports <> 80 / 443 found, so no additional Ports checked.

Permalink: https://check-your-website.server-daten.de/?i=87c80166-8ab8-4913-821b-e14c8db1339f

Last Result: https://check-your-website.server-daten.de/?q=consumablessad.up.gov.in - 2025-06-20 06:43:29

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

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