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

0 in Queue, 0 of max. 8 Checks (07:04:22)
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. NameServer-IPAddresses | 13. CAA | 14. TXT | 15. DomainServiceEntries | 16. Cipher Suites | 17. Portchecks |


X

DNS-problem - authoritative Nameserver refused, not defined or timeout

Checked:
04.09.2024 18:33:06


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
illiyy.in
A
107.172.39.43
Buffalo/New York/United States (US) - HostPapa
Hostname: 107-172-39-43-host.colocrossing.com
yes
2
0

AAAA

yes


www.illiyy.in
CNAME
illiyy.in
yes
1
0

A
107.172.39.43
Buffalo/New York/United States (US) - HostPapa
Hostname: 107-172-39-43-host.colocrossing.com
yes


*.illiyy.in
A
Name Error
yes



A
Name Error
yes



AAAA
Name Error
yes



AAAA
Name Error
yes



CNAME
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



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 20038, Flags 256



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



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 20.09.2024, 00:00:00 +, Signature-Inception: 30.08.2024, 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 25291, DigestType 2 and Digest KUW2EznfpyIa2C1cbH485OnCUj53VKzIEx0O+UYX4vI=



1 RRSIG RR to validate DS RR found



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



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



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 5409, Flags 256



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



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner in., Algorithm: 8, 1 Labels, original TTL: 3600 sec, Signature-expiration: 18.09.2024, 01:38:53 +, Signature-Inception: 04.09.2024, 00:59:33 +, KeyTag 25291, Signer-Name: in



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



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

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



DS with Algorithm 13, KeyTag 48038, DigestType 2 and Digest SDZNDx0ZcmVMxof/uXrCNiNcZSy5qQ1GcQAelGALMqE=



DS with Algorithm 13, KeyTag 48038, DigestType 4 and Digest F9tlM+KoeUlXfCWEcfqojNX1uMJrw1NPGzVEnHUEL8+9t//a2qSCAHyLv2hoG7Zy



1 RRSIG RR to validate DS RR found



RRSIG-Owner illiyy.in., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 17.09.2024, 07:53:07 +, Signature-Inception: 03.09.2024, 07:30:34 +, KeyTag 5409, Signer-Name: in



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



1 DNSKEY RR found



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



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner illiyy.in., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 12.09.2024, 00:00:00 +, Signature-Inception: 22.08.2024, 00:00:00 +, KeyTag 48038, Signer-Name: illiyy.in



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



• Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 48038, DigestType 2 and Digest "SDZNDx0ZcmVMxof/uXrCNiNcZSy5qQ1GcQAelGALMqE=" 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 13, KeyTag 48038, DigestType 4 and Digest "F9tlM+KoeUlXfCWEcfqojNX1uMJrw1NPGzVEnHUEL8+9t//a2qSCAHyLv2hoG7Zy" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone



RRSIG Type 1 validates the A - Result: 107.172.39.43
Validated: RRSIG-Owner illiyy.in., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 12.09.2024, 00:00:00 +, Signature-Inception: 22.08.2024, 00:00:00 +, KeyTag 48038, Signer-Name: illiyy.in



RRSIG Type 16 validates the TXT - Result: v=spf1 include:zoho.com ~all
Validated: RRSIG-Owner illiyy.in., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 12.09.2024, 00:00:00 +, Signature-Inception: 22.08.2024, 00:00:00 +, KeyTag 48038, Signer-Name: illiyy.in



RRSIG Type 257 validates the CAA - Result: 5|issuesectigo.com 9|issuewildsectigo.com 32773|iodefmailto:inboxriau@illiyy.in 32773|issueletsencrypt.org;validationmethods=dns-01;accounturi=https://acme-v02.api.letsencrypt.org/acme/acct/1325539136
Validated: RRSIG-Owner illiyy.in., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 12.09.2024, 00:00:00 +, Signature-Inception: 22.08.2024, 00:00:00 +, KeyTag 48038, Signer-Name: illiyy.in



CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "91bm2b21nc5f9kv5u0dsgrpve1l01ekp" equal the hashed NSEC3-owner "91bm2b21nc5f9kv5u0dsgrpve1l01ekp" and the hashed NextOwner "9tipv06fot1hrt2r4vv3mdvrs5nob0qf". 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, MX, TXT, RRSIG, DNSKEY, NSEC3PARAM, CDS, CDNSKEY, CAA Validated: RRSIG-Owner 91bm2b21nc5f9kv5u0dsgrpve1l01ekp.illiyy.in., Algorithm: 13, 3 Labels, original TTL: 300 sec, Signature-expiration: 12.09.2024, 00:00:00 +, Signature-Inception: 22.08.2024, 00:00:00 +, KeyTag 48038, Signer-Name: illiyy.in



Status: Good. NoData-Proof required and found.



AAAA-Query sends a valid NSEC3 RR as result with the hashed query name "91bm2b21nc5f9kv5u0dsgrpve1l01ekp" equal the hashed NSEC3-owner "91bm2b21nc5f9kv5u0dsgrpve1l01ekp" and the hashed NextOwner "9tipv06fot1hrt2r4vv3mdvrs5nob0qf". 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, MX, TXT, RRSIG, DNSKEY, NSEC3PARAM, CDS, CDNSKEY, CAA Validated: RRSIG-Owner 91bm2b21nc5f9kv5u0dsgrpve1l01ekp.illiyy.in., Algorithm: 13, 3 Labels, original TTL: 300 sec, Signature-expiration: 12.09.2024, 00:00:00 +, Signature-Inception: 22.08.2024, 00:00:00 +, KeyTag 48038, Signer-Name: illiyy.in



Status: Good. NoData-Proof required and found.



TLSA-Query (_443._tcp.illiyy.in) sends a valid NSEC3 RR as result with the hashed owner name "hq8v4gm8d6p5kq6pva816um8ni7llrs5" (unhashed: _tcp.illiyy.in). So that's the Closest Encloser of the query name.
Bitmap: No Bitmap? Validated: RRSIG-Owner hq8v4gm8d6p5kq6pva816um8ni7llrs5.illiyy.in., Algorithm: 13, 3 Labels, original TTL: 300 sec, Signature-expiration: 12.09.2024, 00:00:00 +, Signature-Inception: 22.08.2024, 00:00:00 +, KeyTag 48038, Signer-Name: illiyy.in



Status: Good. NXDomain-Proof required and found.



TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Wildcard expansion of the ClosestEncloser "4bsa5h3a5bdrha4nkovb5l2u1vmhfn4l" (unhashed: *._tcp.illiyy.in) with the owner "47iemfrlvumndoiqs3dggjnes6t63n83" and the NextOwner "4l0cguepbeg8jed2g58l48qvs86g6d38". So that NSEC3 confirms the not-existence of the Wildcard expansion.
Bitmap: SRV, RRSIG Validated: RRSIG-Owner 47iemfrlvumndoiqs3dggjnes6t63n83.illiyy.in., Algorithm: 13, 3 Labels, original TTL: 300 sec, Signature-expiration: 12.09.2024, 00:00:00 +, Signature-Inception: 22.08.2024, 00:00:00 +, KeyTag 48038, Signer-Name: illiyy.in



Status: Good. NXDomain-Proof required and found.



TLSA-Query (_443._tcp.illiyy.in) sends a valid NSEC3 RR as result with the hashed query name "pn4k60hljn0bqam21a33usa4tghja9el" between the hashed NSEC3-owner "pdna80500442vmfg7k9rfn3dphlol4ic" and the hashed NextOwner "qtnqqloljj5un4b614bdaeulpsn2e8tn". So the zone confirmes the not-existence of that TLSA RR.
Bitmap: RRSIG, TLSA Validated: RRSIG-Owner pdna80500442vmfg7k9rfn3dphlol4ic.illiyy.in., Algorithm: 13, 3 Labels, original TTL: 300 sec, Signature-expiration: 12.09.2024, 00:00:00 +, Signature-Inception: 22.08.2024, 00:00:00 +, KeyTag 48038, Signer-Name: illiyy.in



Status: Good. NXDomain-Proof required and found.

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



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "91bm2b21nc5f9kv5u0dsgrpve1l01ekp" as Owner. That's the Hash of "illiyy.in" with the NextHashedOwnerName "9tipv06fot1hrt2r4vv3mdvrs5nob0qf". So that domain name is the Closest Encloser of "www.illiyy.in". Opt-Out: False.
Bitmap: A, NS, SOA, MX, TXT, RRSIG, DNSKEY, NSEC3PARAM, CDS, CDNSKEY, CAA Validated: RRSIG-Owner 91bm2b21nc5f9kv5u0dsgrpve1l01ekp.illiyy.in., Algorithm: 13, 3 Labels, original TTL: 300 sec, Signature-expiration: 12.09.2024, 00:00:00 +, Signature-Inception: 22.08.2024, 00:00:00 +, KeyTag 48038, Signer-Name: illiyy.in



RRSIG Type 5 validates the CNAME - Result: illiyy.in
Validated: RRSIG-Owner www.illiyy.in., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 12.09.2024, 00:00:00 +, Signature-Inception: 22.08.2024, 00:00:00 +, KeyTag 48038, Signer-Name: illiyy.in


3. Name Servers

DomainNameserverNS-IP
illiyy.in
X  get.desec.io
88.99.64.5
Falkenstein/Saxony/Germany (DE) - Hetzner Online GmbH		•

X 
2a01:4f8:10a:1044:deec:642:ac10:80
Falkenstein/Saxony/Germany (DE) - Hetzner Online GmbH

•  ns1.desec.io / a5d3f96ed1dd
45.54.76.1
Dallas/Texas/United States (US) - NetActuate, Inc		•

• 
2607:f740:e633:deec::2
Dallas/Texas/United States (US) - NetActuate, Inc		•

•  ns2.desec.org / 8539098816c8
157.53.224.1
New York/United States (US) - NetActuate, Inc		•

• 
2607:f740:e00a:deec::2
New York/United States (US) - NetActuate, Inc		•
in
•  ns1.registry.in / dns2.defra1
•

•  ns2.registry.in / dns1.defra1
•

•  ns3.registry.in / dns2.defra1
•

•  ns4.registry.in / dns2.defra1
•

•  ns5.registry.in / TLD_Host1.Frankfurt_Node1
•

•  ns6.registry.in / TLD_Host1.Frankfurt_Node1
•


4. SOA-Entries


Domain:in
Zone-Name:in
Primary:ns1.registry.in
Mail:dns.registry.in
Serial:1725467087
Refresh:1800
Retry:300
Expire:1814400
TTL:1800
num Entries:6


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


Domain:illiyy.in
Zone-Name:illiyy.in
Primary:get.desec.io
Mail:get.desec.io
Serial:2024093256
Refresh:86400
Retry:3600
Expire:2419200
TTL:3600
num Entries:4


5. Screenshots

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

6. Url-Checks

DomainnameHttp-StatusredirectSec.G
• http://illiyy.in/
107.172.39.43
-14

10.013
T
Timeout - The operation has timed out.

• http://www.illiyy.in/
107.172.39.43
-14

10.014
T
Timeout - The operation has timed out.

• https://illiyy.in/
107.172.39.43
-102

1.350
V
ConnectionError (2, 0x80004005). Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. (107.172.39.43:443)

• https://www.illiyy.in/
107.172.39.43
-102

1.346
V
ConnectionError (2, 0x80004005). Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. (107.172.39.43:443)

• http://illiyy.in/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
107.172.39.43
-14

10.013
T
Timeout - The operation has timed out.
Visible Content:

• http://www.illiyy.in/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
107.172.39.43
-14

10.017
T
Timeout - The operation has timed out.
Visible Content:

• https://107.172.39.43/
107.172.39.43
-102

1.350
V
ConnectionError (2, 0x80004005). Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. (107.172.39.43:443)

7. Comments


1. General Results, most used to calculate the result

Aname "illiyy.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: 1081 (complete: 245733)
AGood: All ip addresses are public addresses
Warning: Only one ip address found: illiyy.in has only one ip address.
Warning: Only one ip address found: www.illiyy.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: illiyy.in has no ipv6 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: www.illiyy.in has no ipv6 address.
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
Vhttps://illiyy.in/ 107.172.39.43
-102

Connect failure - perhaps firewall
Vhttps://www.illiyy.in/ 107.172.39.43
-102

Connect failure - perhaps firewall
Vhttps://107.172.39.43/ 107.172.39.43
-102

Connect failure - perhaps firewall
XFatal error: Nameserver isn't defined or has timeout
XFatal error: Nameserver doesn't support TCP connection: get.desec.io / 2a01:4f8:10a:1044:deec:642:ac10:80: Timeout
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 illiyy.in, 1 ip addresses.
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 www.illiyy.in, 1 ip addresses.
BNo _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.illiyy.in

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

U

No https result with http status 2** or 4** (standard-check) found, no header checked.

3. DNS- and NameServer - Checks

AInfo:: 6 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 3 Name Servers.
AInfo:: 6 Queries complete, 6 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
AGood: Some ip addresses of name servers found with the minimum of two DNS Queries. One to find the TLD-Zone, one to ask the TLD-Zone.ns2.desec.org (157.53.224.1, 2607:f740:e00a:deec::2), ns1.desec.io (2607:f740:e633:deec::2, 45.54.76.1)
AGood (1 - 3.0):: An average of 2.0 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 3 different Name Servers found: get.desec.io, ns1.desec.io, ns2.desec.org, 2 Name Servers included in Delegation: ns1.desec.io, ns2.desec.org, 2 Name Servers included in 2 Zone definitions: ns1.desec.io, ns2.desec.org, 1 Name Servers listed in SOA.Primary: get.desec.io.
AGood: Only one SOA.Primary Name Server found.: get.desec.io.
Error: SOA.Primary Name Server not included in the delegation set.: get.desec.io.
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: 3 different Name Servers found
AGood: All name servers have ipv4- and ipv6-addresses.: 3 different Name Servers found
AGood: Name servers with different Top Level Domains / Public Suffix List entries found: 3 Name Servers, 2 Top Level Domains: io, org
AGood: Name Servers with different domain names found.: 2 different Domains found
AGood: Name servers with different Country locations found: 3 Name Servers, 2 Countries: DE, US
AInfo: Ipv4-Subnet-list: 3 Name Servers, 3 different subnets (first Byte): 157., 45., 88., 3 different subnets (first two Bytes): 157.53., 45.54., 88.99., 3 different subnets (first three Bytes): 157.53.224., 45.54.76., 88.99.64.
AExcellent: Every Name Server IPv4-address starts with an unique Byte.
AInfo: IPv6-Subnet-list: 3 Name Servers with IPv6, 2 different subnets (first block): 2607:, 2a01:, 2 different subnets (first two blocks): 2607:f740:, 2a01:04f8:, 3 different subnets (first three blocks): 2607:f740:e00a:, 2607:f740:e633:, 2a01:04f8:010a:, 3 different subnets (first four blocks): 2607:f740:e00a:deec:, 2607:f740:e633:deec:, 2a01:04f8:010a:1044:
AGood: Name Server IPv6 addresses from different subnets found.
Nameserver doesn't pass all EDNS-Checks: get.desec.io / 88.99.64.5: 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: get.desec.io / 2a01:4f8:10a:1044:deec:642:ac10:80: 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: ns1.desec.io / 45.54.76.1: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (a5d3f96ed1dd). COOKIE: SOA expected, but NOT found, NOERR expected, BADVER found, Version 0 expectend and found. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns1.desec.io / 2607:f740:e633:deec::2: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (a5d3f96ed1dd). COOKIE: SOA expected, but NOT found, NOERR expected, BADVER found, Version 0 expectend and found. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns2.desec.org / 157.53.224.1: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (8539098816c8). COOKIE: SOA expected, but NOT found, NOERR expected, BADVER found, Version 0 expectend and found. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns2.desec.org / 2607:f740:e00a:deec::2: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (8539098816c8). COOKIE: SOA expected, but NOT found, NOERR expected, BADVER found, Version 0 expectend and found. CLIENTSUBNET: ok.
AGood: All SOA have the same Serial Number
AGood: CAA entries found, creating certificate is limited: letsencrypt.org is allowed to create certificates
AGood: CAA entries found, creating certificate is limited: sectigo.com is allowed to create certificates
AGood: CAA entries found, creating certificate is limited: sectigo.com is allowed to create wildcard-certificates

4. Content- and Performance-critical Checks

http://illiyy.in/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 107.172.39.43
-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.illiyy.in/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 107.172.39.43
-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.
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
ADuration: 124083 milliseconds, 124.083 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)

Issuerlast 7 daysactivenum Certs
CN=ZeroSSL ECC Domain Secure Site CA, O=ZeroSSL, C=AT
0
1
1

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
7888848817
leaf cert		CN=ZeroSSL ECC Domain Secure Site CA, O=ZeroSSL, C=AT
2024-08-07 00:00:00
2024-11-05 23:59:59
*.illiyy.in, conference.job.illiyy.in, illiyy.in - 3 entries



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

Issuerlast 7 daysactivenum Certs
CN=ZeroSSL ECC Domain Secure Site CA, O=ZeroSSL, C=AT
0
1
3

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
14032504398
leaf cert		CN=ZeroSSL ECC Domain Secure Site CA, O=ZeroSSL, C=AT
2024-08-06 22:00:00
2024-11-05 22:59:59
*.illiyy.in, conference.job.illiyy.in, illiyy.in
3 entries


13051712984
leaf cert		CN=ZeroSSL ECC Domain Secure Site CA, O=ZeroSSL, C=AT
2024-05-13 22:00:00
2024-08-12 21:59:59
*.illiyy.in, conference.job.illiyy.in, illiyy.in
3 entries


13051805844
leaf cert		CN=ZeroSSL ECC Domain Secure Site CA, O=ZeroSSL, C=AT
2024-05-13 22:00:00
2024-08-12 21:59:59
*.illiyy.in, conference.job.illiyy.in, illiyy.in
3 entries



11. Html-Content - Entries

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


12. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: get.desec.io, ns1.desec.io, ns2.desec.org

QNr.DomainTypeNS used
1
io
NS
m.root-servers.net (2001:dc3::35)

Answer: a0.nic.io, a2.nic.io, b0.nic.io, c0.nic.io
2
get.desec.io
NS
a0.nic.io (2a01:8840:9e::17)

Answer: ns1.desec.io, ns2.desec.org

Answer: ns1.desec.io
2607:f740:e633:deec::2, 45.54.76.1
3
org
NS
e.root-servers.net (2001:500:a8::e)

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
4
ns2.desec.org: 157.53.224.1, 2607:f740:e00a:deec::2
NS
a0.org.afilias-nst.info (2001:500:e::1)
5
get.desec.io: 88.99.64.5
A
ns1.desec.io (2607:f740:e633:deec::2)
6
get.desec.io: 2a01:4f8:10a:1044:deec:642:ac10:80
AAAA
ns1.desec.io (2607:f740:e633:deec::2)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.illiyy.in
32773
issue
letsencrypt.org;validationmethods=dns-01;accounturi=https://acme-v02.api.letsencrypt.org/acme/acct/1325539136
1
0

32773
iodef
mailto:inboxriau@illiyy.in
1
0

5
issue
sectigo.com
1
0

9
issuewild
sectigo.com
1
0
illiyy.in
32773
issue
letsencrypt.org;validationmethods=dns-01;accounturi=https://acme-v02.api.letsencrypt.org/acme/acct/1325539136
1
0

32773
iodef
mailto:inboxriau@illiyy.in
1
0

5
issue
sectigo.com
1
0

9
issuewild
sectigo.com
1
0
in
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
illiyy.in
v=spf1 include:zoho.com ~all
ok
1
0
www.illiyy.in
v=spf1 include:zoho.com ~all
ok
1
0
_acme-challenge.illiyy.in

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

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

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

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

Name Error - The domain name does not exist
1
0


15. DomainService - Entries (SPF-Check is alpha - 2024-06-22, DMARC-Detailcheck is alpha - 2024-07-06, SMTP-TLS-Reporting is alpa - 2024-07-13)

TypeDomainPrefValueDNS-errornum AnswersStatusDescription
MX

illiyy.in
10
mx.zoho.com
03ok

A


136.143.191.44
01ok

CNAME


00ok
MX

illiyy.in
20
mx2.zoho.com
03ok

A


204.141.33.44
01ok

CNAME


00ok
MX

illiyy.in
50
mx3.zoho.com
03ok

A


136.143.191.44
01ok

CNAME


00ok
SPF
TXT
illiyy.in

v=spf1 include:zoho.com ~all
ok

TXT
zoho.com

v=spf1 include:spf.zoho.com include:zcsend.net -all
ok

TXT
spf.zoho.com

v=spf1 ip4:136.143.188.0/24 ip4:136.143.184.0/24 ip4:135.84.80.0/24 ip4:135.84.82.0/24 ip4:8.39.54.0/23 ip4:204.141.32.0/23 ip4:136.143.182.0/23 ip4:204.141.42.0/23 ip4:8.40.222.0/23 ip4:65.154.166.0/24 ip4:199.67.84.0/24 ip4:199.67.86.0/24 ip4:169.148.129.0/24 ip4:169.148.131.0/24 ip4:121.244.91.48/32 ip4:199.67.88.0/24 ip4:122.15.156.182/32 ip4:169.148.144.0/25 ip4:199.34.22.36/32 ip4:199.67.80.2/32 ip4:169.148.142.10/32 ip4:136.143.190.0/23 ip4:199.67.82.2/32 ip4:136.143.178.49/32 ip4:169.148.144.10/32 ip4:199.67.82.20/32 ip4:199.67.80.20/32 ip4:121.244.91.52/32 ip4:139.167.79.86/32 -all
ok

TXT
spf.zoho.com

ip4:135.84.82.0/24
8192Duplicated ipv4 found.

TXT
zcsend.net

v=spf1 ip4:135.84.81.0/24 ip4:135.84.83.0/24 ip4:136.143.160.0/24 ip4:165.173.128.0/24 ip4:135.84.82.0/24 ip4:136.143.161.0/24 ip6:2607:13c0:0001:0000:0000:0000:0000:7000/116 ip6:2607:13c0:0002:0000:0000:0000:0000:1000/116 ~all
ok

TXT
zcsend.net

ip4:135.84.82.0/24
8192Duplicated ipv4 found.

TXT
ip6:2607:13c0:0001:0000:0000:0000:0000:7000/116

2607:13c0:1::7000
okInfo: Compress your ipv6. Remove left-hand zeros, replace zero-blocks with ::.

TXT
ip6:2607:13c0:0002:0000:0000:0000:0000:1000/116

2607:13c0:2::1000
okInfo: Compress your ipv6. Remove left-hand zeros, replace zero-blocks with ::.
_dmarc
TXT
_dmarc.illiyy.in

v=DMARC1; p=none; rua=mailto:inboxriau@illiyy.in
ok


16. Cipher Suites
No results 

17. Portchecks



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





Permalink: https://check-your-website.server-daten.de/?i=6db2f1c9-4bee-4068-937e-94e6e085aab9



Last Result: https://check-your-website.server-daten.de/?q=illiyy.in - 2024-09-04 18:33:06

Do you like this page? Support this tool, add a link on your page:
<a href="https://check-your-website.server-daten.de/?q=illiyy.in" target="_blank">Check this Site: illiyy.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=illiyy.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