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



P

Tls-Protocol error

Checked:
24.11.2022 16:42:52


Older results


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
vr-tec.ru
A
217.66.20.162
Kazan’/Tatarstan Republic/Russia (RU) - "MTS" OJSC
No Hostname found
yes
1
0

AAAA

yes


www.vr-tec.ru

Name Error
yes
1
0
*.vr-tec.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 18733, 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: 11.12.2022, 00:00:00 +, Signature-Inception: 20.11.2022, 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 33257, DigestType 2 and Digest ZBoLoCehAn0v0XtXQ5MYBO67MpuLUUo1fR7ykPFZ158=



1 RRSIG RR to validate DS RR found



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



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



2 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 33540, Flags 256



1 RRSIG RR to validate DNSKEY RR found



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



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



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

Zone: vr-tec.ru
vr-tec.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 "vmsbbs1gftu376eukqr0pitsld95j8lo" between the hashed NSEC3-owner "vmkmfj1t96dl9jenc5l67rp3scj9qd06" and the hashed NextOwner "vn276s6u3h2n8783ii6gu8lsjasf2bk1". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner vmkmfj1t96dl9jenc5l67rp3scj9qd06.ru., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 05.01.2023, 17:22:45 +, Signature-Inception: 24.11.2022, 02:18:16 +, KeyTag 33540, 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 "j21c11shootmoeqkprm91c8agl4886m6". So that domain name is the Closest Encloser of "vr-tec.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: 29.12.2022, 23:37:43 +, Signature-Inception: 21.11.2022, 18:19:07 +, KeyTag 33540, Signer-Name: ru



0 DNSKEY RR found




Zone: www.vr-tec.ru
www.vr-tec.ru
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.vr-tec.ru
  dns1.yandex.net

vr-tec.ru
  dns1.yandex.net
213.180.204.213
Moscow/Russia (RU) - Yandex enterprise network


 
2a02:6b8::213
Moscow/Russia (RU) - Yandex network


  dns2.yandex.net
93.158.134.213
Moscow/Russia (RU) - Yandex enterprise network


 
2a02:6b8:0:1::213
Moscow/Russia (RU) - Yandex network

ru
  a.dns.ripn.net / gamma-m9-ns5.ripn.net


  b.dns.ripn.net / gamma-spb.ripn.net


  d.dns.ripn.net / gamma2-nsk.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:4053673
Refresh:86400
Retry:14400
Expire:2592000
TTL:3600
num Entries:5


Domain:vr-tec.ru
Zone-Name:vr-tec.ru
Primary:dns1.yandex.net
Mail:dns-hosting.yandex.ru
Serial:19
Refresh:900
Retry:90
Expire:86400
TTL:900
num Entries:4


Domain:www.vr-tec.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
• http://vr-tec.ru/
217.66.20.162 GZip used - 7208 / 32919 - 78.10 %
200

Html is minified: 189.27 %
0.357
H
small visible content (num chars: 433)
VR-Technology Мы позаботимся о Ваших заботах Перейти к содержимому Главная About Blog Home Магазин Мой аккаунт Корзина Оформление заказа Wishlist Wishlist Пример страницы Ничего не найдено Поищите используя форму ниже или просмотрите недавние записи. Найти: Search Найти: Archives Copyright 2022 custom footer text right Iconic One Theme | Powered by Wordpress Это демо-магазин для тестирования — заказы не исполняются. Закрыть
Date: Thu, 24 Nov 2022 15:43:33 GMT
Server: Apache
Link: <http://vr-tec.ru/wp-json/>; rel="https://api.w.org/"
Upgrade: h2,h2c
Connection: Upgrade, close
Vary: Accept-Encoding
Content-Encoding: gzip
Content-Length: 7208
Content-Type: text/html; charset=UTF-8

• https://vr-tec.ru/
217.66.20.162
-10

0.203
P
SecureChannelFailure - The request was aborted: Could not create SSL/TLS secure channel.

• http://vr-tec.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
217.66.20.162
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
404

Html is minified: 249.24 %
0.130
A
Not Found
Visible Content: ERROR 404 - Not Found! The following error occurred: The requested URL was not found on this server. Please check the URL or contact the webmaster. Powered by ISPConfig
Date: Thu, 24 Nov 2022 15:43:34 GMT
Server: Apache
Upgrade: h2,h2c
Connection: Upgrade, close
Last-Modified: Thu, 25 Aug 2022 17:40:01 GMT
ETag: "70f-5e714497252e3"
Accept-Ranges: bytes
Content-Length: 1807
Content-Type: text/html

• https://217.66.20.162/
217.66.20.162
-10

0.136
P
SecureChannelFailure - The request was aborted: Could not create SSL/TLS secure channel.

7. Comments


1. General Results, most used to calculate the result

Aname "vr-tec.ru" is domain, 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: 2310 (complete: 210599)
AGood: All ip addresses are public addresses
Warning: Only one ip address found: vr-tec.ru 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: vr-tec.ru has no ipv6 address.
AGood: No asked Authoritative Name Server had a timeout
ADNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
AGood - only one version with Http-Status 200
AGood: 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.
AGood: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):1 complete Content-Type - header (2 urls)
http://vr-tec.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 217.66.20.162


Url with incomplete Content-Type - header - missing charset
HFatal error: No https - result with http-status 200, no encryption
HFatal 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.
Nvr-tec.ru:8080


Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Phttps://vr-tec.ru/ 217.66.20.162
-10

Error creating a TLS-Connection: No more details available.
Phttps://217.66.20.162/ 217.66.20.162
-10

Error creating a TLS-Connection: No more details available.
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 vr-tec.ru, 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.vr-tec.ru

2. Header-Checks (alpha, started 2022-10-23, may be buggy / incomplete)

U

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

3. DNS- and NameServer - Checks

AInfo:: 21 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
AInfo:: 21 Queries complete, 21 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
Bad (greater 8):: An average of 10.5 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 2 different Name Servers found: dns1.yandex.net, dns2.yandex.net, 2 Name Servers included in Delegation: dns1.yandex.net, dns2.yandex.net, 2 Name Servers included in 1 Zone definitions: dns1.yandex.net, dns2.yandex.net, 1 Name Servers listed in SOA.Primary: dns1.yandex.net.
AGood: Only one SOA.Primary Name Server found.: dns1.yandex.net.
AGood: SOA.Primary Name Server included in the delegation set.: dns1.yandex.net.
AGood: Consistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Ordered list of name servers: dns1.yandex.net, dns2.yandex.net
AGood: All Name Server Domain Names have a Public Suffix.
AGood: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
AGood: All Name Server ip addresses are public.
AGood: Minimal 2 different name servers (public suffix and public ip address) found: 2 different Name Servers found
AGood: All name servers have ipv4- and ipv6-addresses.: 2 different Name Servers found
Warning: All Name Servers have the same Top Level Domain / Public Suffix. If there is a problem with that Top Level Domain, your domain may be affected. Better: Use Name Servers with different top level domains.: 2 Name Servers, 1 Top Level Domain: net
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: yandex.net
Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: RU
AInfo: Ipv4-Subnet-list: 2 Name Servers, 2 different subnets (first Byte): 213., 93., 2 different subnets (first two Bytes): 213.180., 93.158., 2 different subnets (first three Bytes): 213.180.204., 93.158.134.
AExcellent: Every Name Server IPv4-address starts with an unique Byte.
AInfo: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2a02:, 1 different subnets (first two blocks): 2a02:06b8:, 1 different subnets (first three blocks): 2a02:06b8:0000:, 2 different subnets (first four blocks): 2a02:06b8:0000:0000:, 2a02:06b8:0000:0001:
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 4 good Nameserver
AGood: Nameserver supports Echo Capitalization: 4 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 4 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 4 good Nameserver
Nameserver doesn't pass all EDNS-Checks: dns1.yandex.net: 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

AGood: All checks /.well-known/acme-challenge/random-filename without redirects answer with the expected http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 challenge should work. If it doesn't work: Check your vHost configuration (apachectl -S, httpd -S, nginx -T). Every combination of port and ServerName / ServerAlias (Apache) or Server (Nginx) must be unique. Merge duplicated entries in one vHost. If you use an IIS, extensionless files must be allowed in the /.well-known/acme-challenge subdirectory. Create a web.config in that directory. Content: <configuration><system.webServer><staticContent><mimeMap fileExtension="." mimeType="text/plain" /></staticContent></system.webServer></configuration>. If you have a redirect http ⇒ https, that's ok, Letsencrypt follows such redirects to port 80 / 443 (same or other server). There must be a certificate. But the certificate may be expired, self signed or with a not matching domain name. Checking the validation file Letsencrypt ignores such certificate errors. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
AGood: All checked attribute values are enclosed in quotation marks (" or ').
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: 114920 milliseconds, 114.920 seconds


8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
vr-tec.ru
217.66.20.162
8080
Certificate/chain invalid and wrong name
Tls12
ECDH Ephermal
255
Aes128
128
Sha256
not supported
ok
vr-tec.ru
217.66.20.162
8080
Certificate/chain invalid and wrong name
Tls12

ECDH Ephermal
255
Aes128
128
Sha256
not supported
ok
http/2 via ALPN supported 
Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
http/2 via ALPN supported
Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
Self signed certificate
1CN=server1.hstrobot.ru, OU=IT, O=None, L=None, C=DE, ST=None


9. Certificates

1.
1.
CN=server1.hstrobot.ru, OU=IT, O=None, L=None, S=None, C=DE
24.08.2022
21.08.2032
expires in 3556 days

1.
1.
CN=server1.hstrobot.ru, OU=IT, O=None, L=None, S=None, C=DE
24.08.2022

21.08.2032
expires in 3556 days


KeyalgorithmRSA encryption (4096 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:56981D6492C4010CCAEBF260E84C1712EE4C7C5E
Thumbprint:FA4A6B5811B5E63883E3F004B6BA9A39648D22F5
SHA256 / Certificate:81xLbAm1v+dFl/BeFuM1rd51PqEv4lewO38Hx8zAtx8=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):352ed004f6a5790c4e526fa840ac865c27c1f7b80862dd4bbae453f8b7b10fc7
SHA256 hex / Subject Public Key Information (SPKI):352ed004f6a5790c4e526fa840ac865c27c1f7b80862dd4bbae453f8b7b10fc7 (is buggy, ignore the result)
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Check unknown. No result 404 / 200
OCSP - Url:
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:

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


10. Last Certificates - Certificate Transparency Log Check

1. Source CertSpotter - active certificates (one check per day)

Issuerlast 7 daysactivenum Certs
CN=R3, O=Let's Encrypt, C=US
2
2
3

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
4460520704
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-11-23 20:27:04
2023-02-21 20:27:03
vr-tec.ru - 1 entries
duplicate nr. 2

4458965775
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-11-23 11:19:37
2023-02-21 11:19:36
vr-tec.ru - 1 entries
duplicate nr. 1

4101262002
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-08-25 04:37:21
2022-11-23 04:37:20
base.vr-tec.ru, lear.vr-tec.ru, logoskazka.ru, vernresh.ru, vr-tec.ru, y-b-b.ru - 6 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=R3, O=Let's Encrypt, C=US
2 /0 new
2
6

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
8046520249
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-11-23 19:27:04
2023-02-21 19:27:03
vr-tec.ru
1 entries
duplicate nr. 2

8043984683
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-11-23 10:19:37
2023-02-21 10:19:36
vr-tec.ru
1 entries
duplicate nr. 1

7407882142
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-08-25 14:25:52
2022-11-23 15:25:51
base.vr-tec.ru, lear.vr-tec.ru, logoskazka.ru, vernresh.ru, vr-tec.ru, y-b-b.ru
6 entries


7407476302
precert
CN=R3, O=Let's Encrypt, C=US
2022-08-25 13:01:33
2022-11-23 14:01:32
base.vr-tec.ru, lear.vr-tec.ru, logoskazka.ru, vernresh.ru, vr-tec.ru, y-b-b.ru
6 entries


7404567376
precert
CN=R3, O=Let's Encrypt, C=US
2022-08-25 02:37:21
2022-11-23 03:37:20
base.vr-tec.ru, lear.vr-tec.ru, logoskazka.ru, vernresh.ru, vr-tec.ru, y-b-b.ru
6 entries


5630783711
leaf cert
CN=R3, O=Let's Encrypt, C=US
2021-11-18 02:06:50
2022-02-16 02:06:49
logoskazka.ru, lovetatar.ru, vernresh.ru, vr-tec.ru, y-b-b.ru, yellow-blue-bus.ru, ркка.рф (xn--80ataw.xn--p1ai)
7 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: dns1.yandex.net, dns2.yandex.net

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

Answer: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net
2
dns1.yandex.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns1.yandex.ru, ns2.yandex.ru, ns9.z5h64q92x9.net

Answer: ns9.z5h64q92x9.net
154.47.36.189, 2001:2030:20::78, 2001:978:7401::78, 80.239.201.9
3
dns2.yandex.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns1.yandex.ru, ns2.yandex.ru, ns9.z5h64q92x9.net

Answer: ns9.z5h64q92x9.net
154.47.36.189, 2001:2030:20::78, 2001:978:7401::78, 80.239.201.9
4
ru
NS
b.root-servers.net (2001:500:200::b)

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

Answer: ns1.yandex.RU, ns2.yandex.RU, ns9.z5h64q92x9.net

Answer: ns1.YANDEX.RU
213.180.193.1, 2a02:6b8::1

Answer: ns2.YANDEX.RU
2a02:6b8:0:1::1, 93.158.134.1
6
ns2.yandex.ru
NS
a.dns.ripn.net (2001:678:17:0:193:232:128:6)

Answer: ns1.yandex.RU, ns2.yandex.RU, ns9.z5h64q92x9.net

Answer: ns1.YANDEX.RU
213.180.193.1, 2a02:6b8::1

Answer: ns2.YANDEX.RU
2a02:6b8:0:1::1, 93.158.134.1
7
RU
NS
a.root-servers.net (2001:503:ba3e::2:30)

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

Answer: ns1.yandex.RU, ns2.yandex.RU, ns9.z5h64q92x9.net

Answer: ns1.YANDEX.RU
213.180.193.1, 2a02:6b8::1

Answer: ns2.YANDEX.RU
2a02:6b8:0:1::1, 93.158.134.1
9
ns2.yandex.RU
NS
a.dns.ripn.net (2001:678:17:0:193:232:128:6)

Answer: ns1.yandex.RU, ns2.yandex.RU, ns9.z5h64q92x9.net

Answer: ns1.YANDEX.RU
213.180.193.1, 2a02:6b8::1

Answer: ns2.YANDEX.RU
2a02:6b8:0:1::1, 93.158.134.1
10
ns1.yandex.ru: 213.180.193.1
A
ns9.z5h64q92x9.net (2001:2030:20::78)
11
ns1.yandex.ru: 2a02:6b8::1
AAAA
ns9.z5h64q92x9.net (2001:2030:20::78)
12
ns2.yandex.ru: 93.158.134.1
A
ns9.z5h64q92x9.net (2001:2030:20::78)
13
ns2.yandex.ru: 2a02:6b8:0:1::1
AAAA
ns9.z5h64q92x9.net (2001:2030:20::78)
14
ns1.yandex.RU: 213.180.193.1
A
ns9.z5h64q92x9.net (2001:2030:20::78)
15
ns1.yandex.RU: 2a02:6b8::1
AAAA
ns9.z5h64q92x9.net (2001:2030:20::78)
16
ns2.yandex.RU: 93.158.134.1
A
ns1.yandex.ru (2a02:6b8::1)
17
ns2.yandex.RU: 2a02:6b8:0:1::1
AAAA
ns1.yandex.ru (2a02:6b8::1)
18
dns1.yandex.net: 213.180.204.213
A
ns1.yandex.ru (2a02:6b8::1)
19
dns1.yandex.net: 2a02:6b8::213
AAAA
ns1.yandex.ru (2a02:6b8::1)
20
dns2.yandex.net: 93.158.134.213
A
ns1.yandex.ru (2a02:6b8::1)
21
dns2.yandex.net: 2a02:6b8:0:1::213
AAAA
ns1.yandex.ru (2a02:6b8::1)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
vr-tec.ru
0

no CAA entry found
1
0
ru
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
vr-tec.ru
v=spf1 redirect=_spf.yandex.net
ok
1
0
_acme-challenge.vr-tec.ru
VapaVox-ZppqcL9g3VPI9_DSdA2095xxGcyqFMQnpc0
looks good, correct length, correct characters
1
0
_acme-challenge.vr-tec.ru.vr-tec.ru

Name Error - The domain name does not exist
1
0


15. DomainService - Entries (SSHFP Check is new - 2022-09-24, may be incomplete, alpha, some results are required)

TypeDomainPrefValueDNS-errornum AnswersStatusDescription
MX

vr-tec.ru
10
mx.yandex.net
0
1
ok


A


77.88.21.249
0
1
ok


AAAA


2a02:6b8::311
0
1
ok


CNAME



0
0
ok



16. Cipher Suites

DomainIPPortCipher (OpenSsl / IANA)
vr-tec.ru
217.66.20.162
8080
ECDHE-RSA-CHACHA20-POLY1305
(Secure)
TLSv1.2
0xCC,0xA8
FS
5 Ciphers, 56.45 sec
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
ECDH
RSA
CHACHA20/POLY1305(256)
AEAD



ECDHE-RSA-AES256-GCM-SHA384
(Secure)
TLSv1.2
0xC0,0x30
FS

TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
ECDH
RSA
AESGCM(256)
AEAD



DHE-RSA-AES256-GCM-SHA384
(Secure)
TLSv1.2
0x00,0x9F
FS

TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
DH
RSA
AESGCM(256)
AEAD



ECDHE-RSA-AES128-GCM-SHA256
(Secure)
TLSv1.2
0xC0,0x2F
FS

TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
ECDH
RSA
AESGCM(128)
AEAD



DHE-RSA-AES128-GCM-SHA256
(Secure)
TLSv1.2
0x00,0x9E
FS

TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
DH
RSA
AESGCM(128)
AEAD


17. Portchecks

DomainIPPortDescriptionResultAnswer
vr-tec.ru
217.66.20.162
21
FTP



vr-tec.ru
217.66.20.162
21
FTP



vr-tec.ru
217.66.20.162
22
SSH



vr-tec.ru
217.66.20.162
22
SSH



vr-tec.ru
217.66.20.162
25
SMTP



vr-tec.ru
217.66.20.162
25
SMTP



vr-tec.ru
217.66.20.162
53
DNS



vr-tec.ru
217.66.20.162
53
DNS



vr-tec.ru
217.66.20.162
110
POP3



vr-tec.ru
217.66.20.162
110
POP3



vr-tec.ru
217.66.20.162
143
IMAP



vr-tec.ru
217.66.20.162
143
IMAP



vr-tec.ru
217.66.20.162
465
SMTP (encrypted)



vr-tec.ru
217.66.20.162
465
SMTP (encrypted)



vr-tec.ru
217.66.20.162
587
SMTP (encrypted, submission)



vr-tec.ru
217.66.20.162
587
SMTP (encrypted, submission)



vr-tec.ru
217.66.20.162
993
IMAP (encrypted)



vr-tec.ru
217.66.20.162
993
IMAP (encrypted)



vr-tec.ru
217.66.20.162
995
POP3 (encrypted)



vr-tec.ru
217.66.20.162
995
POP3 (encrypted)



vr-tec.ru
217.66.20.162
1433
MS SQL



vr-tec.ru
217.66.20.162
1433
MS SQL



vr-tec.ru
217.66.20.162
2082
cPanel (http)



vr-tec.ru
217.66.20.162
2082
cPanel (http)



vr-tec.ru
217.66.20.162
2083
cPanel (https)



vr-tec.ru
217.66.20.162
2083
cPanel (https)



vr-tec.ru
217.66.20.162
2086
WHM (http)



vr-tec.ru
217.66.20.162
2086
WHM (http)



vr-tec.ru
217.66.20.162
2087
WHM (https)



vr-tec.ru
217.66.20.162
2087
WHM (https)



vr-tec.ru
217.66.20.162
2089
cPanel Licensing



vr-tec.ru
217.66.20.162
2089
cPanel Licensing



vr-tec.ru
217.66.20.162
2095
cPanel Webmail (http)



vr-tec.ru
217.66.20.162
2095
cPanel Webmail (http)



vr-tec.ru
217.66.20.162
2096
cPanel Webmail (https)



vr-tec.ru
217.66.20.162
2096
cPanel Webmail (https)



vr-tec.ru
217.66.20.162
2222
DirectAdmin (http)



vr-tec.ru
217.66.20.162
2222
DirectAdmin (http)



vr-tec.ru
217.66.20.162
2222
DirectAdmin (https)



vr-tec.ru
217.66.20.162
2222
DirectAdmin (https)



vr-tec.ru
217.66.20.162
3306
mySql



vr-tec.ru
217.66.20.162
3306
mySql



vr-tec.ru
217.66.20.162
5224
Plesk Licensing



vr-tec.ru
217.66.20.162
5224
Plesk Licensing



vr-tec.ru
217.66.20.162
5432
PostgreSQL



vr-tec.ru
217.66.20.162
5432
PostgreSQL



vr-tec.ru
217.66.20.162
8080
Ookla Speedtest (http)
open
http://217.66.20.162:8080/
Http-Status: 400
Bad Request

vr-tec.ru
217.66.20.162
8080
Ookla Speedtest (http)
open
http://217.66.20.162:8080/
Http-Status: 400
Bad Request

vr-tec.ru
217.66.20.162
8080
Ookla Speedtest (https)
open
https://217.66.20.162:8080/
Http-Status: 302
Certificate is invalid Redirect: /login/
vr-tec.ru
217.66.20.162
8080
Ookla Speedtest (https)
open
https://217.66.20.162:8080/
Http-Status: 302
Certificate is invalid Redirect: /login/
vr-tec.ru
217.66.20.162
8083
VestaCP http



vr-tec.ru
217.66.20.162
8083
VestaCP http



vr-tec.ru
217.66.20.162
8083
VestaCP https



vr-tec.ru
217.66.20.162
8083
VestaCP https



vr-tec.ru
217.66.20.162
8443
Plesk Administration (https)



vr-tec.ru
217.66.20.162
8443
Plesk Administration (https)



vr-tec.ru
217.66.20.162
8447
Plesk Installer + Updates



vr-tec.ru
217.66.20.162
8447
Plesk Installer + Updates



vr-tec.ru
217.66.20.162
8880
Plesk Administration (http)



vr-tec.ru
217.66.20.162
8880
Plesk Administration (http)



vr-tec.ru
217.66.20.162
10000
Webmin (http)



vr-tec.ru
217.66.20.162
10000
Webmin (http)



vr-tec.ru
217.66.20.162
10000
Webmin (https)



vr-tec.ru
217.66.20.162
10000
Webmin (https)





Permalink: https://check-your-website.server-daten.de/?i=1c9faafa-6efb-4e0b-ba10-44d915239e22


Last Result: https://check-your-website.server-daten.de/?q=vr-tec.ru - 2022-11-24 16:42:52


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

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