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


 

 

U

 

No dns entry found - perhaps mistype. Or wrong IDN

 

Checked:
21.10.2024 12:34:18

 

Older results

 

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
web.tklstk.ru

Name Error
yes
1
0
www.web.tklstk.ru

Name Error
yes
1
0
*.tklstk.ru
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes


*.web.tklstk.ru
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






2 DNSKEY RR found






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






Public Key with Algorithm 8, KeyTag 61050, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 11.11.2024, 00:00:00 +, Signature-Inception: 21.10.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: ru

ru
1 DS RR in the parent zone found






DS with Algorithm 8, KeyTag 43786, DigestType 2 and Digest PFl0dUQJC8dEGdX2njLYybGOpIy9qjPAlDVhkSDO1DE=






1 RRSIG RR to validate DS RR found






RRSIG-Owner ru., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 03.11.2024, 05:00:00 +, Signature-Inception: 21.10.2024, 04:00:00 +, KeyTag 61050, Signer-Name: (root)






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






2 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 27405, Flags 256






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






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner ru., Algorithm: 8, 1 Labels, original TTL: 345600 sec, Signature-expiration: 08.11.2024, 23:00:00 +, Signature-Inception: 20.10.2024, 00:00:00 +, KeyTag 43786, Signer-Name: ru






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






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



Zone: tklstk.ru

tklstk.ru
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 "81vjtnbq2c3evuph007r8n9t11okstt0" between the hashed NSEC3-owner "81tm63g0j49i4skio77jrs2c14vjrqfa" and the hashed NextOwner "820g3aqqpmct4mmm82o0iaom7a3itj4a". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: No Bitmap? Validated: RRSIG-Owner 81tm63g0j49i4skio77jrs2c14vjrqfa.ru., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 08.11.2024, 21:09:13 +, Signature-Inception: 30.09.2024, 12:36:09 +, KeyTag 27405, Signer-Name: ru






DS-Query in the parent zone sends valid NSEC3 RR with the Hash "j20c0qkdhua3cumnkst289ff06u2sq91" as Owner. That's the Hash of "ru" with the NextHashedOwnerName "j21lulr2unpa28sere28ovnjnj67qp7v". So that domain name is the Closest Encloser of "tklstk.ru". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner j20c0qkdhua3cumnkst289ff06u2sq91.ru., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 10.11.2024, 15:53:06 +, Signature-Inception: 30.09.2024, 12:36:09 +, KeyTag 27405, Signer-Name: ru






0 DNSKEY RR found









Zone: web.tklstk.ru

web.tklstk.ru
0 DS RR in the parent zone found



Zone: www.web.tklstk.ru

www.web.tklstk.ru
0 DS RR in the parent zone found

 

3. Name Servers

DomainNameserverNS-IP
www.web.tklstk.ru
  ns1.reg.ru

web.tklstk.ru
  ns1.reg.ru

tklstk.ru
  ns1.reg.ru / ns8.reg.ru
176.99.13.11
Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd


 
176.99.13.13
Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd


 
176.99.13.15
Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd


 
176.99.13.17
Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd


 
194.58.117.11
Moscow/Russia (RU) - Reg.Ru


 
194.58.117.13
Moscow/Russia (RU) - Reg.Ru


 
194.58.117.15
Moscow/Russia (RU) - Reg.Ru


 
194.58.117.17
Moscow/Russia (RU) - Reg.Ru


 
194.67.73.173
Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd


 
194.67.73.174
Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd


 
2a00:f940:4::47
Moscow/Russia (RU) - Reg.Ru SRS Infrastructure


  ns2.reg.ru / ns9.reg.ru
176.99.13.12
Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd


 
176.99.13.14
Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd


 
176.99.13.16
Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd


 
176.99.13.18
Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd


 
194.58.117.12
Moscow/Russia (RU) - Reg.Ru


 
194.58.117.14
Moscow/Russia (RU) - Reg.Ru


 
194.58.117.16
Moscow/Russia (RU) - Reg.Ru


 
194.58.117.18
Moscow/Russia (RU) - Reg.Ru


 
194.67.73.175
Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd


 
194.67.73.176
Moscow/Russia (RU) - "Domain names registrar REG.RU", Ltd


 
2a00:f940:5::190
Moscow/Russia (RU) - Reg.Ru SRS Infrastructure

ru
  a.dns.ripn.net / tau.ripn.net


  b.dns.ripn.net / tau-std.ripn.net


  d.dns.ripn.net / tau-lax.ripn.net


  e.dns.ripn.net / gamma-ekt.ripn.net


  f.dns.ripn.net / gamma-vlv.ripn.net

 

4. SOA-Entries


Domain:ru
Zone-Name:ru
Primary:a.dns.ripn.net
Mail:hostmaster.ripn.net
Serial:4062027
Refresh:86400
Retry:14400
Expire:2592000
TTL:3600
num Entries:5


Domain:tklstk.ru
Zone-Name:tklstk.ru
Primary:ns1.reg.ru
Mail:hostmaster.ns1.reg.ru
Serial:1722517395
Refresh:14400
Retry:3600
Expire:604800
TTL:10800
num Entries:22


Domain:web.tklstk.ru
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


Domain:www.web.tklstk.ru
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

DomainnameHttp-StatusredirectSec.G








 

7. Comments


1. General Results, most used to calculate the result

Aname "web.tklstk.ru" is subdomain, public suffix is ".ru", top-level-domain is ".ru", top-level-domain-type is "country-code", Country is Russian Federation (the), tld-manager is "Coordination Center for TLD RU", num .ru-domains preloaded: 3024 (complete: 251685)
AGood: No asked Authoritative Name Server had a timeout
ADNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
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.web.tklstk.ru

2. Header-Checks

U

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

3. DNS- and NameServer - Checks

AInfo:: 7 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
AInfo:: 7 Queries complete, 7 with IPv6, 0 with IPv4.
AGood: 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.
AInfo:: 2 different Name Servers found: ns1.reg.ru, ns2.reg.ru, 2 Name Servers included in Delegation: ns1.reg.RU, ns2.reg.RU, 2 Name Servers included in 1 Zone definitions: ns1.reg.ru, ns2.reg.ru, 1 Name Servers listed in SOA.Primary: ns1.reg.ru.
AGood: Only one SOA.Primary Name Server found.: ns1.reg.ru.
AGood: SOA.Primary Name Server included in the delegation set.: ns1.reg.ru.
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.
AInfo: Ipv4-Subnet-list: 20 Name Servers, 2 different subnets (first Byte): 176., 194., 3 different subnets (first two Bytes): 176.99., 194.58., 194.67., 3 different subnets (first three Bytes): 176.99.13., 194.58.117., 194.67.73.
AGood: Name Server IPv4-addresses from different subnet found:
AInfo: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2a00:, 1 different subnets (first two blocks): 2a00:f940:, 2 different subnets (first three blocks): 2a00:f940:0004:, 2a00:f940:0005:, 2 different subnets (first four blocks): 2a00:f940:0004:0000:, 2a00:f940:0005:0000:
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 22 good Nameserver
AGood: Nameserver supports Echo Capitalization: 22 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 22 good Nameserver
Nameserver doesn't pass all EDNS-Checks: ns1.reg.ru: 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.reg.ru: 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.
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

Info: Creating a Letsencrypt certificate with that domain name isn't possible. To create a certificate you need a registered, worldwide unique domain name. The domain name ends with a public suffix, that's good (not Grade Z). But the domain isn't registered. If you want a certificate with that domain name, you have to proof that you are the domain owner. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
AGood: Domainname is not on the "Specially Designated Nationals And Blocked Persons List" (SDN). That's an US-list of individuals and companies owned or controlled by, or acting for or on behalf of, targeted countries. It also lists individuals, groups, and entities, such as terrorists and narcotics traffickers designated under programs that are not country-specific. Collectively, such individuals and companies are called "Specially Designated Nationals" or "SDNs." Their assets are blocked and U.S. persons are generally prohibited from dealing with them. So if a domain name is on that list, it's impossible to create a Letsencrypt certificate with that domain name. Check the list manual - https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx
ADuration: 156217 milliseconds, 156.217 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)

No CertSpotter - CT-Log entries found

 

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

No CRT - CT-Log entries found

 

11. Html-Content - Entries

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.reg.ru, ns2.reg.ru

 

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

Answer: a.dns.ripn.net, b.dns.ripn.net, d.dns.ripn.net, e.dns.ripn.net, f.dns.ripn.net
2
ns1.reg.ru
NS
a.dns.ripn.net (2001:678:17:0:193:232:128:6)

Answer: ns1.reg.RU, ns2.reg.RU

Answer: ns2.reg.RU
176.99.13.12, 176.99.13.14, 176.99.13.16, 176.99.13.18, 194.58.117.12, 194.58.117.14, 194.58.117.16, 194.58.117.18, 194.67.73.175, 194.67.73.176, 2a00:f940:5::190

Answer: ns1.reg.RU
176.99.13.11, 176.99.13.13, 176.99.13.15, 176.99.13.17, 194.58.117.11, 194.58.117.13, 194.58.117.15, 194.58.117.17, 194.67.73.173, 194.67.73.174, 2a00:f940:4::47
3
ns2.reg.ru
NS
a.dns.ripn.net (2001:678:17:0:193:232:128:6)

Answer: ns1.reg.RU, ns2.reg.RU

Answer: ns2.reg.RU
176.99.13.12, 176.99.13.14, 176.99.13.16, 176.99.13.18, 194.58.117.12, 194.58.117.14, 194.58.117.16, 194.58.117.18, 194.67.73.175, 194.67.73.176, 2a00:f940:5::190

Answer: ns1.reg.RU
176.99.13.11, 176.99.13.13, 176.99.13.15, 176.99.13.17, 194.58.117.11, 194.58.117.13, 194.58.117.15, 194.58.117.17, 194.67.73.173, 194.67.73.174, 2a00:f940:4::47
4
ns1.reg.ru: 176.99.13.11, 176.99.13.13, 176.99.13.15, 176.99.13.17, 194.58.117.11, 194.58.117.13, 194.58.117.15, 194.58.117.17, 194.67.73.173, 194.67.73.174
A
ns1.reg.ru (2a00:f940:4::47)
5
ns1.reg.ru: 2a00:f940:4::47
AAAA
ns1.reg.ru (2a00:f940:4::47)
6
ns2.reg.ru: 176.99.13.12, 176.99.13.14, 176.99.13.16, 176.99.13.18, 194.58.117.12, 194.58.117.14, 194.58.117.16, 194.58.117.18, 194.67.73.175, 194.67.73.176
A
ns1.reg.ru (2a00:f940:4::47)
7
ns2.reg.ru: 2a00:f940:5::190
AAAA
ns1.reg.ru (2a00:f940:4::47)

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
tklstk.ru
0

no CAA entry found
1
0
ru
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
tklstk.ru
v=spf1 a mx ip4:92.61.20.58 ip4:146.158.109.6 ~all
ok
1
0
_acme-challenge.web.tklstk.ru.tklstk.ru

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=f5eb6478-954c-46a2-a388-0fdb762fdb9a

 

Last Result: https://check-your-website.server-daten.de/?q=web.tklstk.ru - 2024-10-21 12:34:18

 

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

 

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