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

0 in Queue, 0 of max. 8 Checks (00:31:57)
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. Html-Parsing | 13. NameServer-IPAddresses | 14. CAA | 15. TXT | 16. DomainServiceEntries | 17. Cipher Suites | 18. Portchecks |

 

X

 

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

 

Checked:
15.01.2025 15:38:14

 

Older results

 

X - 10.01.2025 16:54:44
U - 10.01.2025 16:03:07
U - 10.01.2025 14:33:17

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
sevasvpn.ru
A
185.233.200.191
Moscow/Russia (RU) - First Server Limited
Hostname: sevasvpn.ru
yes
1
0

AAAA

yes


www.sevasvpn.ru
A
185.233.200.191
Moscow/Russia (RU) - First Server Limited
Hostname: sevasvpn.ru
yes
1
0

AAAA

yes


*.sevasvpn.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






3 DNSKEY RR found






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






Public Key with Algorithm 8, KeyTag 26470, Flags 256






Public Key with Algorithm 8, KeyTag 38696, 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: 01.02.2025, 00:00:00 +, Signature-Inception: 11.01.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: ru

ru
1 DS RR in the parent zone found






DS with Algorithm 8, KeyTag 18374, DigestType 2 and Digest gFjQwIjZs/fzAIDiuMmASUQwFyKizOnuZvasdP6y4gA=






1 RRSIG RR to validate DS RR found






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






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






2 DNSKEY RR found






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






Public Key with Algorithm 8, KeyTag 55728, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner ru., Algorithm: 8, 1 Labels, original TTL: 345600 sec, Signature-expiration: 29.01.2025, 00:00:00 +, Signature-Inception: 09.01.2025, 00:00:00 +, KeyTag 18374, Signer-Name: ru






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






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



Zone: sevasvpn.ru

sevasvpn.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 "btuvu5eticchnhu0lkd3fi41atmf38sh" between the hashed NSEC3-owner "btut6k8g0ug0jlgi4eoter0a2f52bs05" and the hashed NextOwner "bu26mkrdga64ppf1ddv23nl95e0sdb96". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner btut6k8g0ug0jlgi4eoter0a2f52bs05.ru., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 30.01.2025, 05:44:15 +, Signature-Inception: 24.12.2024, 14:14:51 +, KeyTag 55728, 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 "sevasvpn.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: 30.01.2025, 16:17:45 +, Signature-Inception: 24.12.2024, 14:14:51 +, KeyTag 55728, Signer-Name: ru






0 DNSKEY RR found









Zone: www.sevasvpn.ru

www.sevasvpn.ru
0 DS RR in the parent zone found

 

3. Name Servers

DomainNameserverNS-IP
www.sevasvpn.ru
•  firstbytedns.net

sevasvpn.ru
X  firstbytedns.net


•  ns1.firstbytedns.net
185.104.248.26
Moscow/Russia (RU) - First Server Limited		•

• 
2a04:5200:ffff::320b
Moscow/Russia (RU) - NTX Technologies s.r.o.		•

•  ns1.firstbytedns.ru
185.104.248.26
Moscow/Russia (RU) - First Server Limited		•

• 
2a04:5200:ffff::320b
Moscow/Russia (RU) - NTX Technologies s.r.o.		•

•  ns2.firstbytedns.net
185.104.248.27
Moscow/Russia (RU) - First Server Limited		•

• 
2a04:5200:ffff::35de
Moscow/Russia (RU) - NTX Technologies s.r.o.		•

T  ns2.firstbytedns.ru
185.104.248.27
Moscow/Russia (RU) - First Server Limited		•

• 
2a04:5200:ffff::35de
Moscow/Russia (RU) - NTX Technologies s.r.o.		•

•  ns3.firstbytedns.net
185.180.230.222
Moscow/Russia (RU) - NTX Technologies s.r.o.		•

T 
2a04:5200:ffff::115d
Moscow/Russia (RU) - NTX Technologies s.r.o.		•

•  ns3.firstbytedns.ru
185.180.230.222
Moscow/Russia (RU) - NTX Technologies s.r.o.		•

• 
2a04:5200:ffff::115d
Moscow/Russia (RU) - NTX Technologies s.r.o.		•
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 / tau-ekt.ripn.net
•

•  f.dns.ripn.net / tau-vlv.ripn.net
•

 

4. SOA-Entries


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


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


Domain:sevasvpn.ru
Zone-Name:sevasvpn.ru
Primary:firstbytedns.net
Mail:w0w4lolnn.mail.ru
Serial:2025011001
Refresh:3600
Retry:3600
Expire:604800
TTL:86400
num Entries:11


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


5. Screenshots

Startaddress: https://sevasvpn.ru/, address used: https://sevasvpn.ru/, Screenshot created 2025-01-15 15:43:01 +00:0 url is insecure, certificate invalid

 

Mobil (412px x 732px)

 

1042 milliseconds

 

Screenshot mobile - https://sevasvpn.ru/
Mobil + Landscape (732px x 412px)

 

1034 milliseconds

 

Screenshot mobile landscape - https://sevasvpn.ru/
Screen (1280px x 1680px)

 

1127 milliseconds

 

Screenshot Desktop - https://sevasvpn.ru/

 

Mobile- and other Chrome-Checks


widthheight
visual Viewport396716
content Size496992

 

Fatal: Horizontal scrollbar detected. Content-size width is greater then visual Viewport width.

 

6. Url-Checks


:

:
DomainnameHttp-StatusredirectSec.G
• http://sevasvpn.ru/
185.233.200.191 gzip used - 1378 / 4059 - 66.05 %
200

Html is minified: 303.14 %
0.104
H
Date: Wed, 15 Jan 2025 14:40:43 GMT
Server: Apache/2.4.52,(Ubuntu)
ETag: "fdb-62bac2ac22600-gzip"
Accept-Ranges: bytes
Vary: Accept-Encoding
Last-Modified: Tue, 14 Jan 2025 15:25:12 GMT
Content-Encoding: gzip
Content-Length: 1378
Content-Type: text/html

• http://www.sevasvpn.ru/
185.233.200.191 gzip used - 1378 / 4059 - 66.05 %
200

Html is minified: 303.14 %
0.053
H
Date: Wed, 15 Jan 2025 14:40:43 GMT
Server: Apache/2.4.52,(Ubuntu)
ETag: "fdb-62bac2ac22600-gzip"
Accept-Ranges: bytes
Vary: Accept-Encoding
Last-Modified: Tue, 14 Jan 2025 15:25:12 GMT
Content-Encoding: gzip
Content-Length: 1378
Content-Type: text/html

• https://sevasvpn.ru/
185.233.200.191 gzip used - 1378 / 4059 - 66.05 %
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 1/1953		200

Html is minified: 303.14 %
Other inline scripts (∑/total): 0/0		3.080
N
Certificate error: RemoteCertificateNameMismatch
Date: Wed, 15 Jan 2025 14:40:43 GMT
Server: Apache/2.4.52,(Ubuntu)
ETag: "fdb-62bac2ac22600-gzip"
Accept-Ranges: bytes
Vary: Accept-Encoding
Last-Modified: Tue, 14 Jan 2025 15:25:12 GMT
Content-Encoding: gzip
Content-Length: 1378
Content-Type: text/html

• https://www.sevasvpn.ru/
185.233.200.191 gzip used - 1378 / 4059 - 66.05 %
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 1/1953		200

Html is minified: 303.14 %
Other inline scripts (∑/total): 0/0		2.914
N
Certificate error: RemoteCertificateNameMismatch
Date: Wed, 15 Jan 2025 14:40:49 GMT
Server: Apache/2.4.52,(Ubuntu)
ETag: "fdb-62bac2ac22600-gzip"
Accept-Ranges: bytes
Vary: Accept-Encoding
Last-Modified: Tue, 14 Jan 2025 15:25:12 GMT
Content-Encoding: gzip
Content-Length: 1378
Content-Type: text/html

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

Html is minified: 103.41 %
Other inline scripts (∑/total): 0/0		0.104
A
Not Found
Visible Content:
Date: Wed, 15 Jan 2025 14:40:54 GMT
Server: Apache/2.4.52,(Ubuntu)
Content-Length: 273
Content-Type: text/html; charset=iso-8859-1

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

Html is minified: 103.36 %
Other inline scripts (∑/total): 0/0		0.054
A
Not Found
Visible Content:
Date: Wed, 15 Jan 2025 14:40:55 GMT
Server: Apache/2.4.52,(Ubuntu)
Content-Length: 277
Content-Type: text/html; charset=iso-8859-1

• https://185.233.200.191/
185.233.200.191 gzip used - 1378 / 4059 - 66.05 %
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 1/1953		200

Html is minified: 303.14 %
Other inline scripts (∑/total): 0/0		2.840
N
Certificate error: RemoteCertificateNameMismatch
Date: Wed, 15 Jan 2025 14:40:56 GMT
Server: Apache/2.4.52,(Ubuntu)
ETag: "fdb-62bac2ac22600-gzip"
Accept-Ranges: bytes
Vary: Accept-Encoding
Last-Modified: Tue, 14 Jan 2025 15:25:12 GMT
Content-Encoding: gzip
Content-Length: 1378
Content-Type: text/html

 

7. Comments


1. General Results, most used to calculate the result

Aname "sevasvpn.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: 3093 (complete: 263653)
AGood: All ip addresses are public addresses
Warning: Only one ip address found: sevasvpn.ru has only one ip address.
Warning: Only one ip address found: www.sevasvpn.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: sevasvpn.ru 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.sevasvpn.ru has no ipv6 address.
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):2 complete Content-Type - header (7 urls)
http://sevasvpn.ru/ 185.233.200.191


Url with incomplete Content-Type - header - missing charset
http://www.sevasvpn.ru/ 185.233.200.191


Url with incomplete Content-Type - header - missing charset
https://sevasvpn.ru/ 185.233.200.191


Url with incomplete Content-Type - header - missing charset
https://www.sevasvpn.ru/ 185.233.200.191


Url with incomplete Content-Type - header - missing charset
https://185.233.200.191/ 185.233.200.191


Url with incomplete Content-Type - header - missing charset
Bhttps://sevasvpn.ru/ 185.233.200.191
200

Missing HSTS-Header
Bhttps://www.sevasvpn.ru/ 185.233.200.191
200

Missing HSTS-Header
CError - no preferred version www or non-www. Select one version as preferred version, then add a redirect https + not-preferred version to https + preferred version. Perhaps in your port 443 vHost something like "RewriteEngine on" + "RewriteCond %{SERVER_NAME} = example.com" + "ReWriteRule ^ https://www.example.com%{REQUEST_URI} [END,QSA,R=permanent]" (three rows, without the "). That should create a redirect https + example.com ⇒ https + www.example.com. Or switch both values to use the non-www version as your preferred version.
CError - more then one version with Http-Status 200. After all redirects, all users (and search engines) should see the same https url: Non-www or www, but not both with http status 200.
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.
Nhttps://sevasvpn.ru/ 185.233.200.191
200

Error - Certificate isn't trusted, RemoteCertificateNameMismatch
Nhttps://www.sevasvpn.ru/ 185.233.200.191
200

Error - Certificate isn't trusted, RemoteCertificateNameMismatch
Nhttps://185.233.200.191/ 185.233.200.191
200

Error - Certificate isn't trusted, RemoteCertificateNameMismatch
XFatal error: Nameserver doesn't support TCP connection: firstbytedns.net: Timeout
Info: Checking all ip addresses of that domain without sending the hostname only one certificate found. Checking all ip addresses and sending the hostname only one certificate found. Both certificates are the same. So that domain doesn't require Server Name Indication (SNI), it's the primary certificate of that set of ip addresses.: Domain sevasvpn.ru, 1 ip addresses, 1 different http results.
Info: Checking all ip addresses of that domain without sending the hostname only one certificate found. Checking all ip addresses and sending the hostname only one certificate found. Both certificates are the same. So that domain doesn't require Server Name Indication (SNI), it's the primary certificate of that set of ip addresses.: Domain www.sevasvpn.ru, 1 ip addresses, 1 different http results.
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.sevasvpn.ru

2. Header-Checks

Fsevasvpn.ru 185.233.200.191
Content-Security-Policy
Critical: Missing Header:
Fsevasvpn.ru 185.233.200.191
X-Content-Type-Options
Critical: Missing Header:
Fsevasvpn.ru 185.233.200.191
Referrer-Policy
Critical: Missing Header:
Fsevasvpn.ru 185.233.200.191
Permissions-Policy
Critical: Missing Header:
Bsevasvpn.ru 185.233.200.191
Cross-Origin-Embedder-Policy
Info: Missing Header
Bsevasvpn.ru 185.233.200.191
Cross-Origin-Opener-Policy
Info: Missing Header
Bsevasvpn.ru 185.233.200.191
Cross-Origin-Resource-Policy
Info: Missing Header
Fwww.sevasvpn.ru 185.233.200.191
Content-Security-Policy
Critical: Missing Header:
Fwww.sevasvpn.ru 185.233.200.191
X-Content-Type-Options
Critical: Missing Header:
Fwww.sevasvpn.ru 185.233.200.191
Referrer-Policy
Critical: Missing Header:
Fwww.sevasvpn.ru 185.233.200.191
Permissions-Policy
Critical: Missing Header:
Bwww.sevasvpn.ru 185.233.200.191
Cross-Origin-Embedder-Policy
Info: Missing Header
Bwww.sevasvpn.ru 185.233.200.191
Cross-Origin-Opener-Policy
Info: Missing Header
Bwww.sevasvpn.ru 185.233.200.191
Cross-Origin-Resource-Policy
Info: Missing Header

3. DNS- and NameServer - Checks

AInfo:: 12 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 6 Name Servers.
AInfo:: 12 Queries complete, 6 with IPv6, 4 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.
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.ns1.firstbytedns.net (185.104.248.26), ns2.firstbytedns.net (185.104.248.27), ns3.firstbytedns.net (185.180.230.222)
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:: 7 different Name Servers found: firstbytedns.net, ns1.firstbytedns.net, ns1.firstbytedns.ru, ns2.firstbytedns.net, ns2.firstbytedns.ru, ns3.firstbytedns.net, ns3.firstbytedns.ru, 2 Name Servers included in Delegation: ns1.firstbytedns.net, ns2.firstbytedns.net, 6 Name Servers included in 2 Zone definitions: ns1.firstbytedns.net, ns1.firstbytedns.ru, ns2.firstbytedns.net, ns2.firstbytedns.ru, ns3.firstbytedns.net, ns3.firstbytedns.ru, 1 Name Servers listed in SOA.Primary: firstbytedns.net.
AGood: Only one SOA.Primary Name Server found.: firstbytedns.net.
Error: SOA.Primary Name Server not included in the delegation set.: firstbytedns.net.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns1.firstbytedns.net (185.104.248.26): Delegation: ns1.firstbytedns.net, ns2.firstbytedns.net, Zone: ns1.firstbytedns.net, ns1.firstbytedns.ru, ns2.firstbytedns.net, ns2.firstbytedns.ru, ns3.firstbytedns.net, ns3.firstbytedns.ru. Name Servers defined in Zone, missing in Delegation: ns1.firstbytedns.ru, ns2.firstbytedns.ru, ns3.firstbytedns.net, ns3.firstbytedns.ru.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns1.firstbytedns.net (2a04:5200:ffff::320b): Delegation: ns1.firstbytedns.net, ns2.firstbytedns.net, Zone: ns1.firstbytedns.net, ns1.firstbytedns.ru, ns2.firstbytedns.net, ns2.firstbytedns.ru, ns3.firstbytedns.net, ns3.firstbytedns.ru. Name Servers defined in Zone, missing in Delegation: ns1.firstbytedns.ru, ns2.firstbytedns.ru, ns3.firstbytedns.net, ns3.firstbytedns.ru.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns1.firstbytedns.ru (185.104.248.26): Delegation: ns1.firstbytedns.net, ns2.firstbytedns.net, Zone: ns1.firstbytedns.net, ns1.firstbytedns.ru, ns2.firstbytedns.net, ns2.firstbytedns.ru, ns3.firstbytedns.net, ns3.firstbytedns.ru. Name Servers defined in Zone, missing in Delegation: ns1.firstbytedns.ru, ns2.firstbytedns.ru, ns3.firstbytedns.net, ns3.firstbytedns.ru.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns1.firstbytedns.ru (2a04:5200:ffff::320b): Delegation: ns1.firstbytedns.net, ns2.firstbytedns.net, Zone: ns1.firstbytedns.net, ns1.firstbytedns.ru, ns2.firstbytedns.net, ns2.firstbytedns.ru, ns3.firstbytedns.net, ns3.firstbytedns.ru. Name Servers defined in Zone, missing in Delegation: ns1.firstbytedns.ru, ns2.firstbytedns.ru, ns3.firstbytedns.net, ns3.firstbytedns.ru.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns2.firstbytedns.net (185.104.248.27): Delegation: ns1.firstbytedns.net, ns2.firstbytedns.net, Zone: ns1.firstbytedns.net, ns1.firstbytedns.ru, ns2.firstbytedns.net, ns2.firstbytedns.ru, ns3.firstbytedns.net, ns3.firstbytedns.ru. Name Servers defined in Zone, missing in Delegation: ns1.firstbytedns.ru, ns2.firstbytedns.ru, ns3.firstbytedns.net, ns3.firstbytedns.ru.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns2.firstbytedns.net (2a04:5200:ffff::35de): Delegation: ns1.firstbytedns.net, ns2.firstbytedns.net, Zone: ns1.firstbytedns.net, ns1.firstbytedns.ru, ns2.firstbytedns.net, ns2.firstbytedns.ru, ns3.firstbytedns.net, ns3.firstbytedns.ru. Name Servers defined in Zone, missing in Delegation: ns1.firstbytedns.ru, ns2.firstbytedns.ru, ns3.firstbytedns.net, ns3.firstbytedns.ru.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns3.firstbytedns.net (185.180.230.222): Delegation: ns1.firstbytedns.net, ns2.firstbytedns.net, Zone: ns1.firstbytedns.net, ns1.firstbytedns.ru, ns2.firstbytedns.net, ns2.firstbytedns.ru, ns3.firstbytedns.net, ns3.firstbytedns.ru. Name Servers defined in Zone, missing in Delegation: ns1.firstbytedns.ru, ns2.firstbytedns.ru, ns3.firstbytedns.net, ns3.firstbytedns.ru.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns3.firstbytedns.net (2a04:5200:ffff::115d): Delegation: ns1.firstbytedns.net, ns2.firstbytedns.net, Zone: ns1.firstbytedns.net, ns1.firstbytedns.ru, ns2.firstbytedns.net, ns2.firstbytedns.ru, ns3.firstbytedns.net, ns3.firstbytedns.ru. Name Servers defined in Zone, missing in Delegation: ns1.firstbytedns.ru, ns2.firstbytedns.ru, ns3.firstbytedns.net, ns3.firstbytedns.ru.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns3.firstbytedns.ru (185.180.230.222): Delegation: ns1.firstbytedns.net, ns2.firstbytedns.net, Zone: ns1.firstbytedns.net, ns1.firstbytedns.ru, ns2.firstbytedns.net, ns2.firstbytedns.ru, ns3.firstbytedns.net, ns3.firstbytedns.ru. Name Servers defined in Zone, missing in Delegation: ns1.firstbytedns.ru, ns2.firstbytedns.ru, ns3.firstbytedns.net, ns3.firstbytedns.ru.
XFatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns3.firstbytedns.ru (2a04:5200:ffff::115d): Delegation: ns1.firstbytedns.net, ns2.firstbytedns.net, Zone: ns1.firstbytedns.net, ns1.firstbytedns.ru, ns2.firstbytedns.net, ns2.firstbytedns.ru, ns3.firstbytedns.net, ns3.firstbytedns.ru. Name Servers defined in Zone, missing in Delegation: ns1.firstbytedns.ru, ns2.firstbytedns.ru, ns3.firstbytedns.net, ns3.firstbytedns.ru.
AGood: All Name Server Domain Names have a Public Suffix.
Error: Name Server Domain Names with Public Suffix and without ip address found.: 1 Name Servers without ipv4 and ipv6: 1

AGood: Minimal 2 different name servers (public suffix and public ip address) found: 6 different Name Servers found
AGood: All name servers have ipv4- and ipv6-addresses.: 6 different Name Servers found
AGood: Name servers with different Top Level Domains / Public Suffix List entries found: 6 Name Servers, 2 Top Level Domains: ru, net
AGood: Name Servers with different domain names found.: 3 different Domains found
Warning: All Name Servers from the same Country / IP location.: 6 Name Servers, 1 Countries: RU
AInfo: Ipv4-Subnet-list: 6 Name Servers, 1 different subnets (first Byte): 185., 2 different subnets (first two Bytes): 185.104., 185.180., 2 different subnets (first three Bytes): 185.104.248., 185.180.230.
AGood: Name Server IPv4-addresses from different subnet found:
AInfo: IPv6-Subnet-list: 6 Name Servers with IPv6, 1 different subnets (first block): 2a04:, 1 different subnets (first two blocks): 2a04:5200:, 1 different subnets (first three blocks): 2a04:5200:ffff:, 1 different subnets (first four blocks): 2a04:5200:ffff:0000:
Fatal: All Name Server IPv6 addresses from the same subnet.
XNameserver Timeout checking Echo Capitalization: ns3.firstbytedns.net / 2a04:5200:ffff::115d
XNameserver Timeout checking EDNS512: ns2.firstbytedns.ru / 185.104.248.27
Nameserver doesn't pass all EDNS-Checks: firstbytedns.net: 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: firstbytedns.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.
Nameserver doesn't pass all EDNS-Checks: ns1.firstbytedns.net / 185.104.248.26: OP100: ok. FLAGS: ok. V1: ok. V1OP100: fatal timeout. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns1.firstbytedns.net / 2a04:5200:ffff::320b: OP100: ok. FLAGS: fatal timeout. V1: ok. V1OP100: fatal timeout. V1FLAGS: ok. DNSSEC: fatal timeout. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns1.firstbytedns.ru / 185.104.248.26: OP100: ok. FLAGS: ok. V1: fatal timeout. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns1.firstbytedns.ru / 2a04:5200:ffff::320b: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: fatal timeout. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns2.firstbytedns.net / 185.104.248.27: OP100: ok. FLAGS: ok. V1: fatal timeout. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: fatal timeout.
Nameserver doesn't pass all EDNS-Checks: ns2.firstbytedns.net / 2a04:5200:ffff::35de: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: fatal timeout. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns2.firstbytedns.ru / 185.104.248.27: OP100: ok. FLAGS: ok. V1: fatal timeout. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns2.firstbytedns.ru / 2a04:5200:ffff::35de: OP100: ok. FLAGS: fatal timeout. V1: ok. V1OP100: ok. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns3.firstbytedns.net / 2a04:5200:ffff::115d: OP100: fatal timeout. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns3.firstbytedns.ru / 2a04:5200:ffff::115d: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: fatal timeout. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
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: Every https result with status 200 and greater 1024 Bytes is compressed (gzip, deflate, br checked).
https://sevasvpn.ru/ 185.233.200.191
200

Warning: Https + http status 200 + Inline CSS / JavaScript found. Don't use inline CSS / JavaScript. These are compiled and re-used ressources, save these with a long Cache-Control max-age - header.
https://www.sevasvpn.ru/ 185.233.200.191
200

Warning: Https + http status 200 + Inline CSS / JavaScript found. Don't use inline CSS / JavaScript. These are compiled and re-used ressources, save these with a long Cache-Control max-age - header.
https://185.233.200.191/ 185.233.200.191
200

Warning: Https + http status 200 + Inline CSS / JavaScript found. Don't use inline CSS / JavaScript. These are compiled and re-used ressources, save these with a long Cache-Control max-age - header.
https://sevasvpn.ru/ 185.233.200.191
200

Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space.
https://www.sevasvpn.ru/ 185.233.200.191
200

Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space.
https://185.233.200.191/ 185.233.200.191
200

Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space.
https://sevasvpn.ru/ 185.233.200.191
200

Warning: Https connections (Standard Port 443) found without support of the http/2 protocol via ALPN. Http/2 is the new Http-Version (old: http 1.1) with some important new features. Update your server software so http/2 is available. Only one TCP-connection per Server (that's a performance boost), Header-Compression and Server Pushs are available. Domain Sharding and Inline-CSS/Javascript shouldn't used with http/2.
https://www.sevasvpn.ru/ 185.233.200.191
200

Warning: Https connections (Standard Port 443) found without support of the http/2 protocol via ALPN. Http/2 is the new Http-Version (old: http 1.1) with some important new features. Update your server software so http/2 is available. Only one TCP-connection per Server (that's a performance boost), Header-Compression and Server Pushs are available. Domain Sharding and Inline-CSS/Javascript shouldn't used with http/2.
https://185.233.200.191/ 185.233.200.191
200

Warning: Https connections (Standard Port 443) found without support of the http/2 protocol via ALPN. Http/2 is the new Http-Version (old: http 1.1) with some important new features. Update your server software so http/2 is available. Only one TCP-connection per Server (that's a performance boost), Header-Compression and Server Pushs are available. Domain Sharding and Inline-CSS/Javascript shouldn't used with http/2.
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: 294783 milliseconds, 294.783 seconds

 

8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
sevasvpn.ru
185.233.200.191
443
name does not match
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok
sevasvpn.ru
185.233.200.191
443
name does not match
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok
no http/2 via ALPN 
Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
no http/2 via ALPN
 Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
Chain (complete)

1CN=newbot.sevasvpn.ru


2CN=R11, O=Let's Encrypt, C=US


www.sevasvpn.ru
185.233.200.191
443
name does not match
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok

www.sevasvpn.ru
185.233.200.191
443
name does not match
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok
no http/2 via ALPN 
Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
no http/2 via ALPN
 Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
Chain (complete)

1CN=newbot.sevasvpn.ru


2CN=R11, O=Let's Encrypt, C=US


185.233.200.191
185.233.200.191
443
name does not match
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok

185.233.200.191
185.233.200.191
443
name does not match
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok
no http/2 via ALPN 
Cert sent without SNI 		Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
no http/2 via ALPN
Cert sent without SNI 		Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
Chain (complete)

1CN=newbot.sevasvpn.ru


2CN=R11, O=Let's Encrypt, C=US

 

9. Certificates

1.
1.
CN=newbot.sevasvpn.ru
10.01.2025
10.04.2025
expires in 79 days		newbot.sevasvpn.ru - 1 entry
1.
1.
CN=newbot.sevasvpn.ru
10.01.2025

10.04.2025
expires in 79 days


newbot.sevasvpn.ru - 1 entry

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:044654F38B561D3FD1592ADCF50B0583F2BB
Thumbprint:5732BB46B2385860DDB2ACAFE95DEC27905223CC
SHA256 / Certificate:qijQ86SDzG/YZzwn9UXiYHl6xBCPigoGno2U0UJGIKQ=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):9d542e066238645fbf2271b64933edd32cbe7fb65cb44d98c1379b6c283698ad
SHA256 hex / Subject Public Key Information (SPKI):9d542e066238645fbf2271b64933edd32cbe7fb65cb44d98c1379b6c283698ad (is buggy, ignore the result)
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://r11.o.lencr.org
OCSP - must staple:no
Certificate Transparency:yes
Enhanced Key Usage:Serverauthentifizierung (1.3.6.1.5.5.7.3.1), Clientauthentifizierung (1.3.6.1.5.5.7.3.2)




2.
CN=R11, O=Let's Encrypt, C=US
13.03.2024
13.03.2027
expires in 781 days

2.
CN=R11, O=Let's Encrypt, C=US
13.03.2024

13.03.2027
expires in 781 days




KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:008A7D3E13D62F30EF2386BD29076B34F8
Thumbprint:696DB3AF0DFFC17E65C6A20D925C5A7BD24DEC7E
SHA256 / Certificate:WR6c5shj06B56fq+FHjHM5omshJp3eeVIRNhAkrjGkQ=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):6ddac18698f7f1f7e1c69b9bce420d974ac6f94ca8b2c761701623f99c767dc7
SHA256 hex / Subject Public Key Information (SPKI):
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:Clientauthentifizierung (1.3.6.1.5.5.7.3.2), Serverauthentifizierung (1.3.6.1.5.5.7.3.1)




3.
CN=ISRG Root X1, O=Internet Security Research Group, C=US
04.06.2015
04.06.2035
expires in 3786 days

3.
CN=ISRG Root X1, O=Internet Security Research Group, C=US
04.06.2015

04.06.2035
expires in 3786 days




KeyalgorithmRSA encryption (4096 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:008210CFB0D240E3594463E0BB63828B00
Thumbprint:CABD2A79A1076A31F21D253635CB039D4329A5E8
SHA256 / Certificate:lrzsBiZJdvN0YHeazyjFp8/oo8Cq4RqP/O4FwL3fCMY=
SHA256 hex / Cert (DANE * 0 1):96bcec06264976f37460779acf28c5a7cfe8a3c0aae11a8ffcee05c0bddf08c6
SHA256 hex / PublicKey (DANE * 1 1):0b9fa5a59eed715c26c1020c711b4f6ec42d58b0015e14337a39dad301c5afc3
SHA256 hex / Subject Public Key Information (SPKI):0b9fa5a59eed715c26c1020c711b4f6ec42d58b0015e14337a39dad301c5afc3
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:




 

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

Summary


Subresource Integrity (SRI)
DomainnameHtmlElementrel/property∑∑ size∑ problems∑ int.∑ ext.∑ Origin poss.∑ SRI ParseErrors∑ SRI valid∑ SRI missing
https://sevasvpn.ru/
185.233.200.191		a

4

0


0
0
0


meta
other
2

0


0
0
0

https://www.sevasvpn.ru/
185.233.200.191		a

4

0


0
0
0


meta
other
2

0


0
0
0

https://185.233.200.191/
185.233.200.191		a

4

0


0
0
0


meta
other
2

0


0
0
0

 

Details (currently limited to 500 rows - some problems with spam users)

DomainnameHtml-Elementname/equiv/ property/relhref/src/contentHttpStatusmsg∑Status
https://sevasvpn.ru/
185.233.200.191
a

https://t.me/sev_vpn


4
ok















meta
charset
 UTF-8


1
ok















meta
viewport
width=device-width, initial-scale=1.0


1
ok














https://www.sevasvpn.ru/
185.233.200.191
a

https://t.me/sev_vpn


4
ok















meta
charset
 UTF-8


1
ok















meta
viewport
width=device-width, initial-scale=1.0


1
ok














 

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

Url used (first standard-https-result with http status 200): https://sevasvpn.ru/

Summary

Good: No non-document-errors
0 errors
0 warnings

 

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: ns1.firstbytedns.net, ns1.firstbytedns.ru, ns2.firstbytedns.net, ns2.firstbytedns.ru, ns3.firstbytedns.net, ns3.firstbytedns.ru

 

QNr.DomainTypeNS used
1
net
NS
a.root-servers.net (2001:503:ba3e::2:30)

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

Answer: ns2.firstbytedns.net
185.104.248.27

Answer: ns3.firstbytedns.net
185.180.230.222
3
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
4
ns1.firstbytedns.ru
NS
a.dns.ripn.net (2001:678:17:0:193:232:128:6)

Answer: ns1.firstbytedns.RU, ns2.firstbytedns.RU, ns3.firstbytedns.RU

Answer: ns1.firstbytedns.RU
185.104.248.26

Answer: ns2.firstbytedns.RU
185.104.248.27

Answer: ns3.firstbytedns.RU
185.180.230.222
5
ns2.firstbytedns.ru
NS
a.dns.ripn.net (2001:678:17:0:193:232:128:6)

Answer: ns1.firstbytedns.RU, ns2.firstbytedns.RU, ns3.firstbytedns.RU

Answer: ns1.firstbytedns.RU
185.104.248.26

Answer: ns2.firstbytedns.RU
185.104.248.27

Answer: ns3.firstbytedns.RU
185.180.230.222
6
ns3.firstbytedns.ru
NS
a.dns.ripn.net (2001:678:17:0:193:232:128:6)

Answer: ns1.firstbytedns.RU, ns2.firstbytedns.RU, ns3.firstbytedns.RU

Answer: ns1.firstbytedns.RU
185.104.248.26

Answer: ns2.firstbytedns.RU
185.104.248.27

Answer: ns3.firstbytedns.RU
185.180.230.222
7
ns1.firstbytedns.ru: 185.104.248.26
A
ns1.firstbytedns.ru (185.104.248.26)
9
ns2.firstbytedns.ru: 185.104.248.27
A
ns1.firstbytedns.ru (185.104.248.26)
10
ns2.firstbytedns.ru: 2a04:5200:ffff::35de
AAAA
ns1.firstbytedns.ru (185.104.248.26)
12
ns3.firstbytedns.ru: 2a04:5200:ffff::115d
AAAA
ns1.firstbytedns.ru (185.104.248.26)

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.sevasvpn.ru
0

no CAA entry found
2
1
sevasvpn.ru
0

no CAA entry found
2
1
ru
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
sevasvpn.ru

ok
1
0
www.sevasvpn.ru

ok
1
0
_acme-challenge.sevasvpn.ru

Name Error - The domain name does not exist
1
0
_acme-challenge.www.sevasvpn.ru

Name Error - The domain name does not exist
1
0
_acme-challenge.sevasvpn.ru.sevasvpn.ru

Name Error - The domain name does not exist
1
0
_acme-challenge.www.sevasvpn.ru.www.sevasvpn.ru

Name Error - The domain name does not exist
1
0

 

16. DomainService - Entries

TypeDomainPrefValueDNS-errornum AnswersStatusDescription
MX

sevasvpn.ru
10
mail.sevasvpn.ru
02ok

A


185.233.200.191
01ok

CNAME


ok

CNAME


00ok
MX

sevasvpn.ru
20
mail.sevasvpn.ru
02ok

A


185.233.200.191
01ok

CNAME


00ok

				 
			

				 
			
17. Cipher Suites
Summary
DomainIPPortnum CipherstimeStd.ProtocolForward Secrecy
sevasvpn.ru
185.233.200.191
443
5 Ciphers47.65 sec
0 without, 5 FS
100.00 %
www.sevasvpn.ru
185.233.200.191
443
5 Ciphers48.11 sec
0 without, 5 FS
100.00 %
Complete

2
10 Ciphers
5.00 Ciphers/Check		95.76 sec47.88 sec/Check
0 without, 10 FS
100.00 %

Details
DomainIPPortCipher (OpenSsl / IANA)
sevasvpn.ru
185.233.200.191
443
ECDHE-RSA-CHACHA20-POLY1305
 (Secure)
TLSv1.2
0xCC,0xA8
 FS
5 Ciphers, 

47.65 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

www.sevasvpn.ru
185.233.200.191
443
ECDHE-RSA-CHACHA20-POLY1305
 (Secure)
TLSv1.2
0xCC,0xA8
 FS
5 Ciphers, 

48.11 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


				 
			
18. Portchecks
DomainIPPortDescriptionResultAnswer
sevasvpn.ru
185.233.200.191
21
FTP



sevasvpn.ru
185.233.200.191
21
FTP



sevasvpn.ru
185.233.200.191
22
SSH
open
SSH-2.0-OpenSSH_8.9p1 Ubuntu-3ubuntu0.10  

sevasvpn.ru
185.233.200.191
22
SSH
open
SSH-2.0-OpenSSH_8.9p1 Ubuntu-3ubuntu0.10  
Bad: SSH without DNS SSHFP Record found
sevasvpn.ru
185.233.200.191
25
SMTP



sevasvpn.ru
185.233.200.191
25
SMTP



sevasvpn.ru
185.233.200.191
53
DNS



sevasvpn.ru
185.233.200.191
53
DNS



sevasvpn.ru
185.233.200.191
110
POP3



sevasvpn.ru
185.233.200.191
110
POP3



sevasvpn.ru
185.233.200.191
143
IMAP



sevasvpn.ru
185.233.200.191
143
IMAP



sevasvpn.ru
185.233.200.191
465
SMTP (encrypted)



sevasvpn.ru
185.233.200.191
465
SMTP (encrypted)



sevasvpn.ru
185.233.200.191
587
SMTP (encrypted, submission)



sevasvpn.ru
185.233.200.191
587
SMTP (encrypted, submission)



sevasvpn.ru
185.233.200.191
993
IMAP (encrypted)



sevasvpn.ru
185.233.200.191
993
IMAP (encrypted)



sevasvpn.ru
185.233.200.191
995
POP3 (encrypted)



sevasvpn.ru
185.233.200.191
995
POP3 (encrypted)



sevasvpn.ru
185.233.200.191
1433
MS SQL



sevasvpn.ru
185.233.200.191
1433
MS SQL



sevasvpn.ru
185.233.200.191
2082
cPanel (http)



sevasvpn.ru
185.233.200.191
2082
cPanel (http)



sevasvpn.ru
185.233.200.191
2083
cPanel (https)



sevasvpn.ru
185.233.200.191
2083
cPanel (https)



sevasvpn.ru
185.233.200.191
2086
WHM (http)



sevasvpn.ru
185.233.200.191
2086
WHM (http)



sevasvpn.ru
185.233.200.191
2087
WHM (https)



sevasvpn.ru
185.233.200.191
2087
WHM (https)



sevasvpn.ru
185.233.200.191
2089
cPanel Licensing



sevasvpn.ru
185.233.200.191
2089
cPanel Licensing



sevasvpn.ru
185.233.200.191
2095
cPanel Webmail (http)



sevasvpn.ru
185.233.200.191
2095
cPanel Webmail (http)



sevasvpn.ru
185.233.200.191
2096
cPanel Webmail (https)



sevasvpn.ru
185.233.200.191
2096
cPanel Webmail (https)



sevasvpn.ru
185.233.200.191
2222
DirectAdmin (http)



sevasvpn.ru
185.233.200.191
2222
DirectAdmin (http)



sevasvpn.ru
185.233.200.191
2222
DirectAdmin (https)



sevasvpn.ru
185.233.200.191
2222
DirectAdmin (https)



sevasvpn.ru
185.233.200.191
3306
mySql



sevasvpn.ru
185.233.200.191
3306
mySql



sevasvpn.ru
185.233.200.191
5224
Plesk Licensing



sevasvpn.ru
185.233.200.191
5224
Plesk Licensing



sevasvpn.ru
185.233.200.191
5432
PostgreSQL



sevasvpn.ru
185.233.200.191
5432
PostgreSQL



sevasvpn.ru
185.233.200.191
8080
Ookla Speedtest (http)



sevasvpn.ru
185.233.200.191
8080
Ookla Speedtest (http)



sevasvpn.ru
185.233.200.191
8080
Ookla Speedtest (https)



sevasvpn.ru
185.233.200.191
8080
Ookla Speedtest (https)



sevasvpn.ru
185.233.200.191
8083
VestaCP http



sevasvpn.ru
185.233.200.191
8083
VestaCP http



sevasvpn.ru
185.233.200.191
8083
VestaCP https



sevasvpn.ru
185.233.200.191
8083
VestaCP https



sevasvpn.ru
185.233.200.191
8443
Plesk Administration (https)



sevasvpn.ru
185.233.200.191
8443
Plesk Administration (https)



sevasvpn.ru
185.233.200.191
8447
Plesk Installer + Updates



sevasvpn.ru
185.233.200.191
8447
Plesk Installer + Updates



sevasvpn.ru
185.233.200.191
8880
Plesk Administration (http)



sevasvpn.ru
185.233.200.191
8880
Plesk Administration (http)



sevasvpn.ru
185.233.200.191
10000
Webmin (http)



sevasvpn.ru
185.233.200.191
10000
Webmin (http)



sevasvpn.ru
185.233.200.191
10000
Webmin (https)



sevasvpn.ru
185.233.200.191
10000
Webmin (https)



www.sevasvpn.ru
185.233.200.191
21
FTP



www.sevasvpn.ru
185.233.200.191
21
FTP



www.sevasvpn.ru
185.233.200.191
22
SSH
open
SSH-2.0-OpenSSH_8.9p1 Ubuntu-3ubuntu0.10  

www.sevasvpn.ru
185.233.200.191
22
SSH
open
SSH-2.0-OpenSSH_8.9p1 Ubuntu-3ubuntu0.10  
Bad: SSH without DNS SSHFP Record found
www.sevasvpn.ru
185.233.200.191
25
SMTP



www.sevasvpn.ru
185.233.200.191
25
SMTP



www.sevasvpn.ru
185.233.200.191
53
DNS



www.sevasvpn.ru
185.233.200.191
53
DNS



www.sevasvpn.ru
185.233.200.191
110
POP3



www.sevasvpn.ru
185.233.200.191
110
POP3



www.sevasvpn.ru
185.233.200.191
143
IMAP



www.sevasvpn.ru
185.233.200.191
143
IMAP



www.sevasvpn.ru
185.233.200.191
465
SMTP (encrypted)



www.sevasvpn.ru
185.233.200.191
465
SMTP (encrypted)



www.sevasvpn.ru
185.233.200.191
587
SMTP (encrypted, submission)



www.sevasvpn.ru
185.233.200.191
587
SMTP (encrypted, submission)



www.sevasvpn.ru
185.233.200.191
993
IMAP (encrypted)



www.sevasvpn.ru
185.233.200.191
993
IMAP (encrypted)



www.sevasvpn.ru
185.233.200.191
995
POP3 (encrypted)



www.sevasvpn.ru
185.233.200.191
995
POP3 (encrypted)



www.sevasvpn.ru
185.233.200.191
1433
MS SQL



www.sevasvpn.ru
185.233.200.191
1433
MS SQL



www.sevasvpn.ru
185.233.200.191
2082
cPanel (http)



www.sevasvpn.ru
185.233.200.191
2082
cPanel (http)



www.sevasvpn.ru
185.233.200.191
2083
cPanel (https)



www.sevasvpn.ru
185.233.200.191
2083
cPanel (https)



www.sevasvpn.ru
185.233.200.191
2086
WHM (http)



www.sevasvpn.ru
185.233.200.191
2086
WHM (http)



www.sevasvpn.ru
185.233.200.191
2087
WHM (https)



www.sevasvpn.ru
185.233.200.191
2087
WHM (https)



www.sevasvpn.ru
185.233.200.191
2089
cPanel Licensing



www.sevasvpn.ru
185.233.200.191
2089
cPanel Licensing



www.sevasvpn.ru
185.233.200.191
2095
cPanel Webmail (http)



www.sevasvpn.ru
185.233.200.191
2095
cPanel Webmail (http)



www.sevasvpn.ru
185.233.200.191
2096
cPanel Webmail (https)



www.sevasvpn.ru
185.233.200.191
2096
cPanel Webmail (https)



www.sevasvpn.ru
185.233.200.191
2222
DirectAdmin (http)



www.sevasvpn.ru
185.233.200.191
2222
DirectAdmin (http)



www.sevasvpn.ru
185.233.200.191
2222
DirectAdmin (https)



www.sevasvpn.ru
185.233.200.191
2222
DirectAdmin (https)



www.sevasvpn.ru
185.233.200.191
3306
mySql



www.sevasvpn.ru
185.233.200.191
3306
mySql



www.sevasvpn.ru
185.233.200.191
5224
Plesk Licensing



www.sevasvpn.ru
185.233.200.191
5224
Plesk Licensing



www.sevasvpn.ru
185.233.200.191
5432
PostgreSQL



www.sevasvpn.ru
185.233.200.191
5432
PostgreSQL



www.sevasvpn.ru
185.233.200.191
8080
Ookla Speedtest (http)



www.sevasvpn.ru
185.233.200.191
8080
Ookla Speedtest (http)



www.sevasvpn.ru
185.233.200.191
8080
Ookla Speedtest (https)



www.sevasvpn.ru
185.233.200.191
8080
Ookla Speedtest (https)



www.sevasvpn.ru
185.233.200.191
8083
VestaCP http



www.sevasvpn.ru
185.233.200.191
8083
VestaCP http



www.sevasvpn.ru
185.233.200.191
8083
VestaCP https



www.sevasvpn.ru
185.233.200.191
8083
VestaCP https



www.sevasvpn.ru
185.233.200.191
8443
Plesk Administration (https)



www.sevasvpn.ru
185.233.200.191
8443
Plesk Administration (https)



www.sevasvpn.ru
185.233.200.191
8447
Plesk Installer + Updates



www.sevasvpn.ru
185.233.200.191
8447
Plesk Installer + Updates



www.sevasvpn.ru
185.233.200.191
8880
Plesk Administration (http)



www.sevasvpn.ru
185.233.200.191
8880
Plesk Administration (http)



www.sevasvpn.ru
185.233.200.191
10000
Webmin (http)



www.sevasvpn.ru
185.233.200.191
10000
Webmin (http)



www.sevasvpn.ru
185.233.200.191
10000
Webmin (https)



www.sevasvpn.ru
185.233.200.191
10000
Webmin (https)




				 
			

				 
			

Permalink: https://check-your-website.server-daten.de/?i=6c63f660-ea4b-4bf8-ae25-20c2a14e1d87

				 
			


Last Result: https://check-your-website.server-daten.de/?q=sevasvpn.ru - 2025-01-15 15:38:14

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

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

				 
			

				 
			



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