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




V

Connect failure - perhaps firewall

Checked:
10.07.2024 13:48:29


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
vpn239.ru
A
94.158.218.157
Riga/Latvia (LV) - SIA VEESP
No Hostname found
yes
1
0

AAAA

yes


www.vpn239.ru
A
94.158.218.157
Riga/Latvia (LV) - SIA VEESP
No Hostname found
yes
1
0

AAAA

yes


*.vpn239.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 5613, Flags 256



Public Key with Algorithm 8, KeyTag 20038, Flags 256



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



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 22.07.2024, 00:00:00 +, Signature-Inception: 01.07.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: 23.07.2024, 05:00:00 +, Signature-Inception: 10.07.2024, 04:00:00 +, KeyTag 20038, Signer-Name: (root)



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



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 35739, 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: 28.07.2024, 00:00:00 +, Signature-Inception: 08.07.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: vpn239.ru
vpn239.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 "ng14ssbm04scmm4suf2t6ko6tkb564ic" between the hashed NSEC3-owner "ng0nnjh5lpn76g1b06jsflsir20daqd1" and the hashed NextOwner "ng3j69loib1ikrsg9grcrqv8lch6k3c8". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner ng0nnjh5lpn76g1b06jsflsir20daqd1.ru., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 18.08.2024, 14:46:47 +, Signature-Inception: 05.07.2024, 08:18:34 +, KeyTag 35739, 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 "vpn239.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: 11.08.2024, 15:31:26 +, Signature-Inception: 05.07.2024, 08:18:34 +, KeyTag 35739, Signer-Name: ru



0 DNSKEY RR found




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


3. Name Servers

DomainNameserverNS-IP
www.vpn239.ru
  ns1.reg.ru / ns12.reg.ru

vpn239.ru
  ns1.reg.ru / ns9.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 / ns16.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 / tau-vlv.ripn.net


4. SOA-Entries


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


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


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


Domain:www.vpn239.ru
Zone-Name:vpn239.ru
Primary:ns1.reg.ru
Mail:hostmaster.ns1.reg.ru
Serial:1720605967
Refresh:14400
Retry:3600
Expire:604800
TTL:10800
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://vpn239.ru/
94.158.218.157 GZip used - 186 / 235 - 20.85 %
200

Html is minified: 118.09 %
0.054
H
Date: Wed, 10 Jul 2024 11:49:52 GMT
Server: Apache/2.4.41, (Ubuntu)
Vary: Accept-Encoding
Connection: close
Content-Encoding: gzip
Content-Length: 186
Content-Type: text/html; charset=UTF-8

• http://www.vpn239.ru/
94.158.218.157 GZip used - 186 / 235 - 20.85 %
200

Html is minified: 118.09 %
0.050
H
Date: Wed, 10 Jul 2024 11:49:52 GMT
Server: Apache/2.4.41, (Ubuntu)
Vary: Accept-Encoding
Connection: close
Content-Encoding: gzip
Content-Length: 186
Content-Type: text/html; charset=UTF-8

• https://vpn239.ru/
94.158.218.157
-16

1.080
V
UnknownError - Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. [::ffff:94.158.218.157]:443 (94.158.218.157:443)

• https://www.vpn239.ru/
94.158.218.157
-16

1.080
V
UnknownError - Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. [::ffff:94.158.218.157]:443 (94.158.218.157:443)

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

Html is minified: 100.00 %
0.050
A
Not Found
Visible Content:
Date: Wed, 10 Jul 2024 11:49:54 GMT
Server: Apache/2.4.41, (Ubuntu)
Connection: close
Content-Length: 271
Content-Type: text/html; charset=iso-8859-1

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

Html is minified: 100.00 %
0.043
A
Not Found
Visible Content:
Date: Wed, 10 Jul 2024 11:49:54 GMT
Server: Apache/2.4.41, (Ubuntu)
Connection: close
Content-Length: 275
Content-Type: text/html; charset=iso-8859-1

• https://94.158.218.157/
94.158.218.157
-16

1.076
V
UnknownError - Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. [::ffff:94.158.218.157]:443 (94.158.218.157:443)

7. Comments


1. General Results, most used to calculate the result

Aname "vpn239.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: 2974 (complete: 245733)
AGood: All ip addresses are public addresses
Warning: Only one ip address found: vpn239.ru has only one ip address.
Warning: Only one ip address found: www.vpn239.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: vpn239.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.vpn239.ru has no ipv6 address.
AGood: No asked Authoritative Name Server had a timeout
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: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct 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.
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 vpn239.ru, 1 ip addresses.
Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain www.vpn239.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.vpn239.ru

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

U

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

3. DNS- and NameServer - Checks

AInfo:: 6 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 0 Name Servers.
AInfo:: 6 Queries complete, 6 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
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: 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: ns1.reg.ru, ns2.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.
AGood: Minimal 2 different name servers (public suffix and public ip address) found: 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: ru
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: reg.ru
Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: RU
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
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 22 good Nameserver
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.
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: 290330 milliseconds, 290.330 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. 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
g.root-servers.net (2001:500:12::d0d)

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: 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

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
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: 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

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
4
RU
NS
j.root-servers.net (2001:503:c27::2:30)

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

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

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

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
6
ns2.reg.RU
NS
a.dns.ripn.net (2001:678:17:0:193:232:128:6)

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

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

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


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.vpn239.ru
0

no CAA entry found
1
0
vpn239.ru
0

no CAA entry found
1
0
ru
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
vpn239.ru

ok
1
0
www.vpn239.ru

ok
1
0
_acme-challenge.vpn239.ru

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

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

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

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

Name Error - The domain name does not exist
1
0


15. DomainService - Entries (SPF-Check is alpha - 2024-06-22, DMARC-Detailcheck is alpha - 2024-07-06)

No DomainServiceEntries entries found



16. Cipher Suites

No results


17. Portchecks

DomainIPPortDescriptionResultAnswer
vpn239.ru
94.158.218.157
21
FTP



vpn239.ru
94.158.218.157
21
FTP



vpn239.ru
94.158.218.157
22
SSH
open
SSH-2.0-OpenSSH_8.2p1 Ubuntu-4ubuntu0.11

vpn239.ru
94.158.218.157
22
SSH
open
SSH-2.0-OpenSSH_8.2p1 Ubuntu-4ubuntu0.11
Bad: SSH without DNS SSHFP Record found
Possible DNS SSHFP Entries:
vpn239.ru IN SSHFP 1 2 777d5a25083b66ffac2190fd2332c134ac76e9996ac3c4f64dd4c399bb2c7a93
vpn239.ru IN SSHFP 3 2 6450c8143fd7dd229c33755e5eafa8f5d51b649dddd8ffe4922bd4e21d1efc2e
vpn239.ru IN SSHFP 4 2 cb42a4f711ae05d9625227a2efdf862c75253dc12659a4b563df2901d32a8e82
vpn239.ru
94.158.218.157
25
SMTP



vpn239.ru
94.158.218.157
25
SMTP



vpn239.ru
94.158.218.157
53
DNS



vpn239.ru
94.158.218.157
53
DNS



vpn239.ru
94.158.218.157
110
POP3



vpn239.ru
94.158.218.157
110
POP3



vpn239.ru
94.158.218.157
143
IMAP



vpn239.ru
94.158.218.157
143
IMAP



vpn239.ru
94.158.218.157
465
SMTP (encrypted)



vpn239.ru
94.158.218.157
465
SMTP (encrypted)



vpn239.ru
94.158.218.157
587
SMTP (encrypted, submission)



vpn239.ru
94.158.218.157
587
SMTP (encrypted, submission)



vpn239.ru
94.158.218.157
993
IMAP (encrypted)



vpn239.ru
94.158.218.157
993
IMAP (encrypted)



vpn239.ru
94.158.218.157
995
POP3 (encrypted)



vpn239.ru
94.158.218.157
995
POP3 (encrypted)



vpn239.ru
94.158.218.157
1433
MS SQL



vpn239.ru
94.158.218.157
1433
MS SQL



vpn239.ru
94.158.218.157
2082
cPanel (http)



vpn239.ru
94.158.218.157
2082
cPanel (http)



vpn239.ru
94.158.218.157
2083
cPanel (https)



vpn239.ru
94.158.218.157
2083
cPanel (https)



vpn239.ru
94.158.218.157
2086
WHM (http)



vpn239.ru
94.158.218.157
2086
WHM (http)



vpn239.ru
94.158.218.157
2087
WHM (https)



vpn239.ru
94.158.218.157
2087
WHM (https)



vpn239.ru
94.158.218.157
2089
cPanel Licensing



vpn239.ru
94.158.218.157
2089
cPanel Licensing



vpn239.ru
94.158.218.157
2095
cPanel Webmail (http)



vpn239.ru
94.158.218.157
2095
cPanel Webmail (http)



vpn239.ru
94.158.218.157
2096
cPanel Webmail (https)



vpn239.ru
94.158.218.157
2096
cPanel Webmail (https)



vpn239.ru
94.158.218.157
2222
DirectAdmin (http)



vpn239.ru
94.158.218.157
2222
DirectAdmin (http)



vpn239.ru
94.158.218.157
2222
DirectAdmin (https)



vpn239.ru
94.158.218.157
2222
DirectAdmin (https)



vpn239.ru
94.158.218.157
3306
mySql



vpn239.ru
94.158.218.157
3306
mySql



vpn239.ru
94.158.218.157
5224
Plesk Licensing



vpn239.ru
94.158.218.157
5224
Plesk Licensing



vpn239.ru
94.158.218.157
5432
PostgreSQL



vpn239.ru
94.158.218.157
5432
PostgreSQL



vpn239.ru
94.158.218.157
8080
Ookla Speedtest (http)



vpn239.ru
94.158.218.157
8080
Ookla Speedtest (http)



vpn239.ru
94.158.218.157
8080
Ookla Speedtest (https)



vpn239.ru
94.158.218.157
8080
Ookla Speedtest (https)



vpn239.ru
94.158.218.157
8083
VestaCP http



vpn239.ru
94.158.218.157
8083
VestaCP http



vpn239.ru
94.158.218.157
8083
VestaCP https



vpn239.ru
94.158.218.157
8083
VestaCP https



vpn239.ru
94.158.218.157
8443
Plesk Administration (https)



vpn239.ru
94.158.218.157
8443
Plesk Administration (https)



vpn239.ru
94.158.218.157
8447
Plesk Installer + Updates



vpn239.ru
94.158.218.157
8447
Plesk Installer + Updates



vpn239.ru
94.158.218.157
8880
Plesk Administration (http)



vpn239.ru
94.158.218.157
8880
Plesk Administration (http)



vpn239.ru
94.158.218.157
10000
Webmin (http)



vpn239.ru
94.158.218.157
10000
Webmin (http)



vpn239.ru
94.158.218.157
10000
Webmin (https)



vpn239.ru
94.158.218.157
10000
Webmin (https)



www.vpn239.ru
94.158.218.157
21
FTP



www.vpn239.ru
94.158.218.157
21
FTP



www.vpn239.ru
94.158.218.157
22
SSH
open
SSH-2.0-OpenSSH_8.2p1 Ubuntu-4ubuntu0.11

www.vpn239.ru
94.158.218.157
22
SSH
open
SSH-2.0-OpenSSH_8.2p1 Ubuntu-4ubuntu0.11
Bad: SSH without DNS SSHFP Record found
Possible DNS SSHFP Entries:
www.vpn239.ru IN SSHFP 1 2 777d5a25083b66ffac2190fd2332c134ac76e9996ac3c4f64dd4c399bb2c7a93
www.vpn239.ru IN SSHFP 3 2 6450c8143fd7dd229c33755e5eafa8f5d51b649dddd8ffe4922bd4e21d1efc2e
www.vpn239.ru IN SSHFP 4 2 cb42a4f711ae05d9625227a2efdf862c75253dc12659a4b563df2901d32a8e82
www.vpn239.ru
94.158.218.157
25
SMTP



www.vpn239.ru
94.158.218.157
25
SMTP



www.vpn239.ru
94.158.218.157
53
DNS



www.vpn239.ru
94.158.218.157
53
DNS



www.vpn239.ru
94.158.218.157
110
POP3



www.vpn239.ru
94.158.218.157
110
POP3



www.vpn239.ru
94.158.218.157
143
IMAP



www.vpn239.ru
94.158.218.157
143
IMAP



www.vpn239.ru
94.158.218.157
465
SMTP (encrypted)



www.vpn239.ru
94.158.218.157
465
SMTP (encrypted)



www.vpn239.ru
94.158.218.157
587
SMTP (encrypted, submission)



www.vpn239.ru
94.158.218.157
587
SMTP (encrypted, submission)



www.vpn239.ru
94.158.218.157
993
IMAP (encrypted)



www.vpn239.ru
94.158.218.157
993
IMAP (encrypted)



www.vpn239.ru
94.158.218.157
995
POP3 (encrypted)



www.vpn239.ru
94.158.218.157
995
POP3 (encrypted)



www.vpn239.ru
94.158.218.157
1433
MS SQL



www.vpn239.ru
94.158.218.157
1433
MS SQL



www.vpn239.ru
94.158.218.157
2082
cPanel (http)



www.vpn239.ru
94.158.218.157
2082
cPanel (http)



www.vpn239.ru
94.158.218.157
2083
cPanel (https)



www.vpn239.ru
94.158.218.157
2083
cPanel (https)



www.vpn239.ru
94.158.218.157
2086
WHM (http)



www.vpn239.ru
94.158.218.157
2086
WHM (http)



www.vpn239.ru
94.158.218.157
2087
WHM (https)



www.vpn239.ru
94.158.218.157
2087
WHM (https)



www.vpn239.ru
94.158.218.157
2089
cPanel Licensing



www.vpn239.ru
94.158.218.157
2089
cPanel Licensing



www.vpn239.ru
94.158.218.157
2095
cPanel Webmail (http)



www.vpn239.ru
94.158.218.157
2095
cPanel Webmail (http)



www.vpn239.ru
94.158.218.157
2096
cPanel Webmail (https)



www.vpn239.ru
94.158.218.157
2096
cPanel Webmail (https)



www.vpn239.ru
94.158.218.157
2222
DirectAdmin (http)



www.vpn239.ru
94.158.218.157
2222
DirectAdmin (http)



www.vpn239.ru
94.158.218.157
2222
DirectAdmin (https)



www.vpn239.ru
94.158.218.157
2222
DirectAdmin (https)



www.vpn239.ru
94.158.218.157
3306
mySql



www.vpn239.ru
94.158.218.157
3306
mySql



www.vpn239.ru
94.158.218.157
5224
Plesk Licensing



www.vpn239.ru
94.158.218.157
5224
Plesk Licensing



www.vpn239.ru
94.158.218.157
5432
PostgreSQL



www.vpn239.ru
94.158.218.157
5432
PostgreSQL



www.vpn239.ru
94.158.218.157
8080
Ookla Speedtest (http)



www.vpn239.ru
94.158.218.157
8080
Ookla Speedtest (http)



www.vpn239.ru
94.158.218.157
8080
Ookla Speedtest (https)



www.vpn239.ru
94.158.218.157
8080
Ookla Speedtest (https)



www.vpn239.ru
94.158.218.157
8083
VestaCP http



www.vpn239.ru
94.158.218.157
8083
VestaCP http



www.vpn239.ru
94.158.218.157
8083
VestaCP https



www.vpn239.ru
94.158.218.157
8083
VestaCP https



www.vpn239.ru
94.158.218.157
8443
Plesk Administration (https)



www.vpn239.ru
94.158.218.157
8443
Plesk Administration (https)



www.vpn239.ru
94.158.218.157
8447
Plesk Installer + Updates



www.vpn239.ru
94.158.218.157
8447
Plesk Installer + Updates



www.vpn239.ru
94.158.218.157
8880
Plesk Administration (http)



www.vpn239.ru
94.158.218.157
8880
Plesk Administration (http)



www.vpn239.ru
94.158.218.157
10000
Webmin (http)



www.vpn239.ru
94.158.218.157
10000
Webmin (http)



www.vpn239.ru
94.158.218.157
10000
Webmin (https)



www.vpn239.ru
94.158.218.157
10000
Webmin (https)





Permalink: https://check-your-website.server-daten.de/?i=8f867660-b907-4746-b0f8-80f4f622c22e


Last Result: https://check-your-website.server-daten.de/?q=vpn239.ru - 2024-07-10 13:48:29


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

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