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




O

old / weak connection

Checked:
03.04.2024 04:55:04


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
rogoproxy.xyz
A
134.122.122.203
North Bergen/New Jersey/United States (US) - DigitalOcean, LLC
No Hostname found
yes
1
0

AAAA

yes


www.rogoproxy.xyz

Name Error
yes
1
0
*.rogoproxy.xyz
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 20326, Flags 257 (SEP = Secure Entry Point)



Public Key with Algorithm 8, KeyTag 30903, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 22.04.2024, 00:00:00 +, Signature-Inception: 01.04.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: xyz
xyz
2 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 3599, DigestType 2 and Digest uXM4abyEyGu1nRArpdprJ7IIhVIzKjnc1UvE6NZrBJk=



DS with Algorithm 8, KeyTag 18130, DigestType 2 and Digest WqWWEmZZTM6sUJSamSGf4ATxMOGGSkJxQ+n/LmQcrG8=



1 RRSIG RR to validate DS RR found



RRSIG-Owner xyz., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 15.04.2024, 18:00:00 +, Signature-Inception: 02.04.2024, 17:00:00 +, KeyTag 5613, Signer-Name: (root)



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



2 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 65206, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner xyz., Algorithm: 8, 1 Labels, original TTL: 3600 sec, Signature-expiration: 02.05.2024, 08:33:50 +, Signature-Inception: 02.04.2024, 07:03:50 +, KeyTag 18130, Signer-Name: xyz



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



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

Zone: rogoproxy.xyz
rogoproxy.xyz
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 "on6akv9mm34lfir5silrik870t3tiduo" between the hashed NSEC3-owner "on613ub8v427cs6q5eptbr35dcq5ipim" and the hashed NextOwner "on6hginu8bd4673jh9vhbgettaahj18d". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner on613ub8v427cs6q5eptbr35dcq5ipim.xyz., Algorithm: 8, 2 Labels, original TTL: 900 sec, Signature-expiration: 02.05.2024, 08:33:50 +, Signature-Inception: 02.04.2024, 07:03:50 +, KeyTag 65206, Signer-Name: xyz



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "2tjms8vm0h8n7j9e748d19gpnujm0emj" as Owner. That's the Hash of "xyz" with the NextHashedOwnerName "2tk402ni9id6k9m9fq8phvqjhvtfq9o6". So that domain name is the Closest Encloser of "rogoproxy.xyz". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 2tjms8vm0h8n7j9e748d19gpnujm0emj.xyz., Algorithm: 8, 2 Labels, original TTL: 900 sec, Signature-expiration: 02.05.2024, 08:33:50 +, Signature-Inception: 02.04.2024, 07:03:50 +, KeyTag 65206, Signer-Name: xyz



0 DNSKEY RR found




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


3. Name Servers

DomainNameserverNS-IP
www.rogoproxy.xyz
  ns1.digitalocean.com

rogoproxy.xyz
  ns1.digitalocean.com / 67m46
173.245.58.51
San Francisco/California/United States (US) - Cloudflare, Inc.


 
2400:cb00:2049:1::adf5:3a33
San Francisco/California/United States (US) - Cloudflare


  ns2.digitalocean.com / 67m43
173.245.59.41
San Francisco/California/United States (US) - Cloudflare, Inc.


 
2400:cb00:2049:1::adf5:3b29
San Francisco/California/United States (US) - Cloudflare


  ns3.digitalocean.com / 67m78
198.41.222.173
Toronto/Ontario/Canada (CA) - Cloudflare, Inc.


 
2400:cb00:2049:1::c629:dead
San Francisco/California/United States (US) - Cloudflare

xyz
  generationxyz.nic.xyz / PDUS-VJ5JVS-CTI2KM


  ns0.centralnic.net


  x.nic.xyz / SFQY-BG7AF9-XTW0MS


  y.nic.xyz / PDUS-VJ5JVS-CTI2KM


  z.nic.xyz / SFQY-BG7AF9-XTW0MS


4. SOA-Entries


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


Domain:xyz
Zone-Name:xyz
Primary:ns0.centralnic.net
Mail:hostmaster.centralnic.net
Serial:3000784779
Refresh:900
Retry:1800
Expire:6048000
TTL:3600
num Entries:2


Domain:xyz
Zone-Name:xyz
Primary:ns0.centralnic.net
Mail:hostmaster.centralnic.net
Serial:3000784780
Refresh:900
Retry:1800
Expire:6048000
TTL:3600
num Entries:2


Domain:rogoproxy.xyz
Zone-Name:rogoproxy.xyz
Primary:ns1.digitalocean.com
Mail:hostmaster.rogoproxy.xyz
Serial:1585800513
Refresh:10800
Retry:3600
Expire:604800
TTL:1800
num Entries:6


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


5. Screenshots

No Screenshot listed, because no screenshot found. Perhaps the check is too old, the feature startet 2019-12-23.

6. Url-Checks


:

:
DomainnameHttp-StatusredirectSec.G
• http://rogoproxy.xyz/
134.122.122.203
301
https://rogoproxy.xyz/
Html is minified: 107.78 %
0.210
A
Server: nginx/1.10.3, (Ubuntu)
Date: Wed, 03 Apr 2024 02:55:34 GMT
Connection: close
Location: https://rogoproxy.xyz/
Content-Type: text/html
Content-Length: 194

• https://rogoproxy.xyz/
134.122.122.203 No GZip used - 910 / 1410 - 64.54 % possible
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
200

Html is minified: 103.83 %
5.093
B
Server: nginx/1.10.3, (Ubuntu)
Date: Wed, 03 Apr 2024 02:55:35 GMT
Transfer-Encoding: chunked
Connection: close
Access-Control-Allow-Origin: *
Access-Control-Expose-Headers: access-control-allow-origin
Content-Type: text/plain

• http://rogoproxy.xyz/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
134.122.122.203
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
301
https://rogoproxy.xyz/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Html is minified: 107.78 %
0.206
A
Visible Content:
Server: nginx/1.10.3, (Ubuntu)
Date: Wed, 03 Apr 2024 02:55:41 GMT
Connection: close
Location: https://rogoproxy.xyz/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Content-Type: text/html
Content-Length: 194

• https://rogoproxy.xyz/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
404

Html is minified: 100.00 %
4.880
A
Invalid host
Visible Content:
Server: nginx/1.10.3, (Ubuntu)
Date: Wed, 03 Apr 2024 02:55:48 GMT
Transfer-Encoding: chunked
Connection: close
Access-Control-Allow-Origin: *
Access-Control-Expose-Headers: access-control-allow-origin

• https://134.122.122.203/
134.122.122.203 No GZip used - 910 / 1410 - 64.54 % possible
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
200

Html is minified: 103.83 %
4.827
N
Certificate error: RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Server: nginx/1.10.3, (Ubuntu)
Date: Wed, 03 Apr 2024 02:55:42 GMT
Transfer-Encoding: chunked
Connection: close
Access-Control-Allow-Origin: *
Access-Control-Expose-Headers: access-control-allow-origin
Content-Type: text/plain

7. Comments


1. General Results, most used to calculate the result

Aname "rogoproxy.xyz" is domain, public suffix is ".xyz", top-level-domain is ".xyz", top-level-domain-type is "generic", tld-manager is "XYZ.COM LLC", num .xyz-domains preloaded: 1764 (complete: 240622)
AGood: All ip addresses are public addresses
Warning: Only one ip address found: rogoproxy.xyz 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: rogoproxy.xyz 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: destination is https
AGood - only one version with Http-Status 200
AGood: one preferred version: non-www is preferred
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.
https://rogoproxy.xyz/ 134.122.122.203


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


Url with incomplete Content-Type - header - missing charset
Ahttp://rogoproxy.xyz/ 134.122.122.203
301
https://rogoproxy.xyz/
Correct redirect http - https with the same domain name
Bhttps://rogoproxy.xyz/ 134.122.122.203
200

Missing HSTS-Header
Bhttps://rogoproxy.xyz/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
404

Missing HSTS-Header
Nhttps://134.122.122.203/ 134.122.122.203
200

Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Orogoproxy.xyz / 134.122.122.203 / 443


Old connection: Cipher Suites without Forward Secrecy (FS) found. Remove all of these Cipher Suites, use only Cipher Suites with Forward Secrecy: Starting with ECDHE- or DHE - the last "E" says: "ephemeral". Or use Tls.1.3, then all Cipher Suites use FS. 7 Cipher Suites without Forward Secrecy found
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 different. So that domain requires Server Name Indication (SNI), so the server is able to select the correct certificate.: Domain rogoproxy.xyz, 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.rogoproxy.xyz

2. Header-Checks

Frogoproxy.xyz 134.122.122.203
Content-Security-Policy
Critical: Missing Header:
Frogoproxy.xyz 134.122.122.203
X-Content-Type-Options
Critical: Missing Header:
Frogoproxy.xyz 134.122.122.203
Referrer-Policy
Critical: Missing Header:
Frogoproxy.xyz 134.122.122.203
Permissions-Policy
Critical: Missing Header:

3. DNS- and NameServer - Checks

AInfo:: 10 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 3 Name Servers.
AInfo:: 10 Queries complete, 10 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
Ok (4 - 8):: An average of 3.3 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 3 different Name Servers found: ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com, 3 Name Servers included in Delegation: ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com, 3 Name Servers included in 1 Zone definitions: ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com, 1 Name Servers listed in SOA.Primary: ns1.digitalocean.com.
AGood: Only one SOA.Primary Name Server found.: ns1.digitalocean.com.
AGood: SOA.Primary Name Server included in the delegation set.: ns1.digitalocean.com.
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.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com
AGood: All Name Server Domain Names have a Public Suffix.
AGood: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
AGood: All Name Server ip addresses are public.
AGood: Minimal 2 different name servers (public suffix and public ip address) found: 3 different Name Servers found
AGood: All name servers have ipv4- and ipv6-addresses.: 3 different Name Servers found
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.: 3 Name Servers, 1 Top Level Domain: com
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: digitalocean.com
AGood: Name servers with different Country locations found: 3 Name Servers, 2 Countries: CA, US
AInfo: Ipv4-Subnet-list: 3 Name Servers, 2 different subnets (first Byte): 173., 198., 2 different subnets (first two Bytes): 173.245., 198.41., 3 different subnets (first three Bytes): 173.245.58., 173.245.59., 198.41.222.
AGood: Name Server IPv4-addresses from different subnet found:
AInfo: IPv6-Subnet-list: 3 Name Servers with IPv6, 1 different subnets (first block): 2400:, 1 different subnets (first two blocks): 2400:cb00:, 1 different subnets (first three blocks): 2400:cb00:2049:, 1 different subnets (first four blocks): 2400:cb00:2049:0001:
Fatal: All Name Server IPv6 addresses from the same subnet.
AGood: Nameserver supports TCP connections: 6 good Nameserver
AGood: Nameserver supports Echo Capitalization: 6 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 6 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 6 good Nameserver
Nameserver doesn't pass all EDNS-Checks: ns0.centralnic.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.digitalocean.com: 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: x.nic.xyz: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (SFQY-BG7AF9-XTW0MS). COOKIE: SOA expected, but NOT found, NOERR expected, BADVER found, Version 0 expectend and found. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: z.nic.xyz: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (SFQY-BG7AF9-XTW0MS). COOKIE: SOA expected, but NOT found, NOERR expected, BADVER found, Version 0 expectend and found. CLIENTSUBNET: ok.
AGood: All SOA have the same Serial Number
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.
https://rogoproxy.xyz/ 134.122.122.203
200

Warning: https result with status 200 and size greater then 1024 Bytes without GZip found. Add GZip support so the html content is compressed.
https://134.122.122.203/ 134.122.122.203
200

Warning: https result with status 200 and size greater then 1024 Bytes without GZip found. Add GZip support so the html content is compressed.
AGood: No https + http status 200 with inline CSS / JavaScript found
AGood: Every https result with status 200 has a minified Html-Content with a quota lower then 110 %.
https://rogoproxy.xyz/ 134.122.122.203
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://134.122.122.203/ 134.122.122.203
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.
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
https://rogoproxy.xyz/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
404
4.880 seconds
Warning: 404 needs more then one second
ADuration: 180906 milliseconds, 180.906 seconds


8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
rogoproxy.xyz
134.122.122.203
443
ok
Tls12
ECDH Ephermal
256
Aes128
128
Sha256
not supported
ok
rogoproxy.xyz
134.122.122.203
443
ok
Tls12

ECDH Ephermal
256
Aes128
128
Sha256
not supported
ok
no http/2 via ALPN 
SNI required
Tls.1.2
Tls.1.1
Tls.1.0
no Ssl3
no Ssl2
no http/2 via ALPN
SNI required
Tls.1.2
Tls.1.1
Tls.1.0
no Ssl3
no Ssl2
Chain (complete)
1CN=rogoproxy.xyz

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


rogoproxy.xyz
rogoproxy.xyz
443
ok
Tls12
ECDH Ephermal
256
Aes128
128
Sha256
not supported
ok

rogoproxy.xyz
rogoproxy.xyz
443
ok
Tls12

ECDH Ephermal
256
Aes128
128
Sha256
not supported
ok
no http/2 via ALPN 
Tls.1.2
Tls.1.1
Tls.1.0
no Ssl3
no Ssl2
no http/2 via ALPN
Tls.1.2
Tls.1.1
Tls.1.0
no Ssl3
no Ssl2
Chain (complete)
1CN=rogoproxy.xyz

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


134.122.122.203
134.122.122.203
443
Certificate/chain invalid and wrong name
Tls12
ECDH Ephermal
256
Aes256
256
Sha384
not supported
ok

134.122.122.203
134.122.122.203
443
Certificate/chain invalid and wrong name
Tls12

ECDH Ephermal
256
Aes256
256
Sha384
not supported
ok
no http/2 via ALPN 
Cert sent without SNI
Tls.1.2
Tls.1.1
Tls.1.0
no Ssl3
no Ssl2
no http/2 via ALPN
Cert sent without SNI
Tls.1.2
Tls.1.1
Tls.1.0
no Ssl3
no Ssl2
Self signed certificate
1CN=rogoproxy.xyz

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


9. Certificates

1.
1.
CN=rogoproxy.xyz
03.04.2024
02.07.2024
expires in 75 days
rogoproxy.xyz - 1 entry
1.
1.
CN=rogoproxy.xyz
03.04.2024

02.07.2024
expires in 75 days
rogoproxy.xyz - 1 entry

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:0309A99DFEE4ED7807262DB72AF78CCBA639
Thumbprint:8B2F96EB10C63EF8F8424A25C9DE16165D1A6D56
SHA256 / Certificate:ypEwqbuuL1D56KoAakI3DKHuCeoR9zBpeJMXCFh1G88=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):56cde35c57864e9240a2a8526595afd0a4000607bee1564483ddaa8433b08a31
SHA256 hex / Subject Public Key Information (SPKI):56cde35c57864e9240a2a8526595afd0a4000607bee1564483ddaa8433b08a31 (is buggy, ignore the result)
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Check unknown. No result 404 / 200
OCSP - Url:http://r3.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=R3, O=Let's Encrypt, C=US
04.09.2020
15.09.2025
expires in 515 days


2.
CN=R3, O=Let's Encrypt, C=US
04.09.2020

15.09.2025
expires in 515 days


KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:00912B084ACF0C18A753F6D62E25A75F5A
Thumbprint:A053375BFE84E8B748782C7CEE15827A6AF5A405
SHA256 / Certificate:Z63RFmsCCuYbj1/JaBPATCqliZYHloZVcqPH5zdhPf0=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):8d02536c887482bc34ff54e41d2ba659bf85b341a0a20afadb5813dcfbcf286d
SHA256 hex / Subject Public Key Information (SPKI):8d02536c887482bc34ff54e41d2ba659bf85b341a0a20afadb5813dcfbcf286d
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 4064 days


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

04.06.2035
expires in 4064 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:


2.
1.
E=tossedrichi16@gmail.com, CN=CEN, OU=Groga, O=Roga, L=Chihuahua, S=Chihuahua, C=MX
02.04.2020
02.04.2021
1112 days expired

2.
1.
E=tossedrichi16@gmail.com, CN=CEN, OU=Groga, O=Roga, L=Chihuahua, S=Chihuahua, C=MX
02.04.2020

02.04.2021
1112 days expired


KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:009C30750530A84E30
Thumbprint:2EDDA66E964F90B8AB4B749FBE85356B661D07EF
SHA256 / Certificate:I7utKOmZm12UXQbuJWqsz0syTkIdCyE1OC5tf1mEE/E=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):dd4e8abf3ea2d5e77b49d27aaa201562d243b7dee5a89a81ed68d96a6de62ec6
SHA256 hex / Subject Public Key Information (SPKI):dd4e8abf3ea2d5e77b49d27aaa201562d243b7dee5a89a81ed68d96a6de62ec6 (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.
NotTimeValid: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.


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
0
1
2

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
6952160272
leaf cert
CN=R3, O=Let's Encrypt, C=US
2024-03-17 15:48:59
2024-06-15 15:48:58
rogoproxy.xyz - 1 entries


6577059024
leaf cert
CN=R3, O=Let's Encrypt, C=US
2024-01-17 06:12:32
2024-04-16 06:12:31
rogoproxy.xyz - 1 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
0 /0 new
1
3

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
12416010707
leaf cert
CN=R3, O=Let's Encrypt, C=US
2024-03-17 14:48:59
2024-06-15 13:48:58
rogoproxy.xyz
1 entries


11777838467
leaf cert
CN=R3, O=Let's Encrypt, C=US
2024-01-17 05:12:32
2024-04-16 04:12:31
rogoproxy.xyz
1 entries


11138343970
precert
CN=R3, O=Let's Encrypt, C=US
2023-11-18 06:05:46
2024-02-16 06:05:45
rogoproxy.xyz
1 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: ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com

QNr.DomainTypeNS used
1
com
NS
b.root-servers.net (2001:500:200::b)

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.digitalocean.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: kim.ns.cloudflare.com, walt.ns.cloudflare.com

Answer: kim.ns.cloudflare.com
108.162.192.126, 172.64.32.126, 173.245.58.126, 2606:4700:50::adf5:3a7e, 2803:f800:50::6ca2:c07e, 2a06:98c1:50::ac40:207e

Answer: walt.ns.cloudflare.com
108.162.193.148, 172.64.33.148, 173.245.59.148, 2606:4700:58::adf5:3b94, 2803:f800:50::6ca2:c194, 2a06:98c1:50::ac40:2194
3
ns2.digitalocean.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: kim.ns.cloudflare.com, walt.ns.cloudflare.com

Answer: kim.ns.cloudflare.com
108.162.192.126, 172.64.32.126, 173.245.58.126, 2606:4700:50::adf5:3a7e, 2803:f800:50::6ca2:c07e, 2a06:98c1:50::ac40:207e

Answer: walt.ns.cloudflare.com
108.162.193.148, 172.64.33.148, 173.245.59.148, 2606:4700:58::adf5:3b94, 2803:f800:50::6ca2:c194, 2a06:98c1:50::ac40:2194
4
ns3.digitalocean.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: kim.ns.cloudflare.com, walt.ns.cloudflare.com

Answer: kim.ns.cloudflare.com
108.162.192.126, 172.64.32.126, 173.245.58.126, 2606:4700:50::adf5:3a7e, 2803:f800:50::6ca2:c07e, 2a06:98c1:50::ac40:207e

Answer: walt.ns.cloudflare.com
108.162.193.148, 172.64.33.148, 173.245.59.148, 2606:4700:58::adf5:3b94, 2803:f800:50::6ca2:c194, 2a06:98c1:50::ac40:2194
5
ns1.digitalocean.com: 173.245.58.51
A
kim.ns.cloudflare.com (2606:4700:50::adf5:3a7e)
6
ns1.digitalocean.com: 2400:cb00:2049:1::adf5:3a33
AAAA
kim.ns.cloudflare.com (2606:4700:50::adf5:3a7e)
7
ns2.digitalocean.com: 173.245.59.41
A
kim.ns.cloudflare.com (2606:4700:50::adf5:3a7e)
8
ns2.digitalocean.com: 2400:cb00:2049:1::adf5:3b29
AAAA
kim.ns.cloudflare.com (2606:4700:50::adf5:3a7e)
9
ns3.digitalocean.com: 198.41.222.173
A
kim.ns.cloudflare.com (2606:4700:50::adf5:3a7e)
10
ns3.digitalocean.com: 2400:cb00:2049:1::c629:dead
AAAA
kim.ns.cloudflare.com (2606:4700:50::adf5:3a7e)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
rogoproxy.xyz
0

no CAA entry found
1
0
xyz
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
rogoproxy.xyz

ok
1
0
_acme-challenge.rogoproxy.xyz

Name Error - The domain name does not exist
1
0
_acme-challenge.rogoproxy.xyz.rogoproxy.xyz

Name Error - The domain name does not exist
1
0


15. DomainService - Entries

No DomainServiceEntries entries found



16. Cipher Suites

DomainIPPortCipher (OpenSsl / IANA)
rogoproxy.xyz
134.122.122.203
443
ECDHE-RSA-AES256-GCM-SHA384
(Secure)
TLSv1.2
0xC0,0x30
FS
20 Ciphers, 113.79 sec
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



ECDHE-RSA-AES256-SHA384
(Weak)
TLSv1.2
0xC0,0x28
FS

TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
ECDH
RSA
AES(256)
SHA384



DHE-RSA-AES256-SHA256
(Weak)
TLSv1.2
0x00,0x6B
FS

TLS_DHE_RSA_WITH_AES_256_CBC_SHA256
DH
RSA
AES(256)
SHA256



AES256-GCM-SHA384
(Weak)
TLSv1.2
0x00,0x9D
No FS

TLS_RSA_WITH_AES_256_GCM_SHA384
RSA
RSA
AESGCM(256)
AEAD



AES256-SHA256
(Weak)
TLSv1.2
0x00,0x3D
No FS

TLS_RSA_WITH_AES_256_CBC_SHA256
RSA
RSA
AES(256)
SHA256



ECDHE-RSA-AES128-SHA256
(Weak)
TLSv1.2
0xC0,0x27
FS

TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
ECDH
RSA
AES(128)
SHA256



DHE-RSA-AES128-SHA256
(Weak)
TLSv1.2
0x00,0x67
FS

TLS_DHE_RSA_WITH_AES_128_CBC_SHA256
DH
RSA
AES(128)
SHA256



AES128-GCM-SHA256
(Weak)
TLSv1.2
0x00,0x9C
No FS

TLS_RSA_WITH_AES_128_GCM_SHA256
RSA
RSA
AESGCM(128)
AEAD



AES128-SHA256
(Weak)
TLSv1.2
0x00,0x3C
No FS

TLS_RSA_WITH_AES_128_CBC_SHA256
RSA
RSA
AES(128)
SHA256



ECDHE-RSA-AES256-SHA
(Weak)
TLSv1
0xC0,0x14
FS

TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
ECDH
RSA
AES(256)
SHA1



ECDHE-RSA-AES128-SHA
(Weak)
TLSv1
0xC0,0x13
FS

TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
ECDH
RSA
AES(128)
SHA1



DHE-RSA-AES256-SHA
(Weak)
SSLv3
0x00,0x39
FS

TLS_DHE_RSA_WITH_AES_256_CBC_SHA
DH
RSA
AES(256)
SHA1



AES256-SHA
(Weak)
SSLv3
0x00,0x35
No FS

TLS_RSA_WITH_AES_256_CBC_SHA
RSA
RSA
AES(256)
SHA1



ECDHE-RSA-DES-CBC3-SHA
(Weak)
SSLv3
0xC0,0x12
FS

TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA
ECDH
RSA
3DES(168)
SHA1



DES-CBC3-SHA
(Weak)
SSLv3
0x00,0x0A
No FS

TLS_RSA_WITH_3DES_EDE_CBC_SHA
RSA
RSA
3DES(168)
SHA1



DHE-RSA-AES128-SHA
(Weak)
SSLv3
0x00,0x33
FS

TLS_DHE_RSA_WITH_AES_128_CBC_SHA
DH
RSA
AES(128)
SHA1



AES128-SHA
(Weak)
SSLv3
0x00,0x2F
No FS

TLS_RSA_WITH_AES_128_CBC_SHA
RSA
RSA
AES(128)
SHA1


17. Portchecks

DomainIPPortDescriptionResultAnswer
rogoproxy.xyz
134.122.122.203
21
FTP



rogoproxy.xyz
134.122.122.203
21
FTP



rogoproxy.xyz
134.122.122.203
22
SSH
open
SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.8

rogoproxy.xyz
134.122.122.203
22
SSH
open
SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.8
Bad: SSH without DNS SSHFP Record found
Possible DNS SSHFP Entries:
rogoproxy.xyz IN SSHFP 1 2 7fe02a37395e3ccf585666f3da11333d0ea88ae4fac12a43e1d2a492ef32f846
rogoproxy.xyz IN SSHFP 3 2 37659cacc570289c3b4f16eb83fab17a860b3d80891d93f9de9d95aa1466ec9a
rogoproxy.xyz IN SSHFP 4 2 b969a31769731589b4b38a427aeaac3d85398f8c568f4283c77e524ab5f01590
rogoproxy.xyz
134.122.122.203
25
SMTP



rogoproxy.xyz
134.122.122.203
25
SMTP



rogoproxy.xyz
134.122.122.203
53
DNS



rogoproxy.xyz
134.122.122.203
53
DNS



rogoproxy.xyz
134.122.122.203
110
POP3



rogoproxy.xyz
134.122.122.203
110
POP3



rogoproxy.xyz
134.122.122.203
143
IMAP



rogoproxy.xyz
134.122.122.203
143
IMAP



rogoproxy.xyz
134.122.122.203
465
SMTP (encrypted)



rogoproxy.xyz
134.122.122.203
465
SMTP (encrypted)



rogoproxy.xyz
134.122.122.203
587
SMTP (encrypted, submission)



rogoproxy.xyz
134.122.122.203
587
SMTP (encrypted, submission)



rogoproxy.xyz
134.122.122.203
993
IMAP (encrypted)



rogoproxy.xyz
134.122.122.203
993
IMAP (encrypted)



rogoproxy.xyz
134.122.122.203
995
POP3 (encrypted)



rogoproxy.xyz
134.122.122.203
995
POP3 (encrypted)



rogoproxy.xyz
134.122.122.203
1433
MS SQL



rogoproxy.xyz
134.122.122.203
1433
MS SQL



rogoproxy.xyz
134.122.122.203
2082
cPanel (http)



rogoproxy.xyz
134.122.122.203
2082
cPanel (http)



rogoproxy.xyz
134.122.122.203
2083
cPanel (https)



rogoproxy.xyz
134.122.122.203
2083
cPanel (https)



rogoproxy.xyz
134.122.122.203
2086
WHM (http)



rogoproxy.xyz
134.122.122.203
2086
WHM (http)



rogoproxy.xyz
134.122.122.203
2087
WHM (https)



rogoproxy.xyz
134.122.122.203
2087
WHM (https)



rogoproxy.xyz
134.122.122.203
2089
cPanel Licensing



rogoproxy.xyz
134.122.122.203
2089
cPanel Licensing



rogoproxy.xyz
134.122.122.203
2095
cPanel Webmail (http)



rogoproxy.xyz
134.122.122.203
2095
cPanel Webmail (http)



rogoproxy.xyz
134.122.122.203
2096
cPanel Webmail (https)



rogoproxy.xyz
134.122.122.203
2096
cPanel Webmail (https)



rogoproxy.xyz
134.122.122.203
2222
DirectAdmin (http)



rogoproxy.xyz
134.122.122.203
2222
DirectAdmin (http)



rogoproxy.xyz
134.122.122.203
2222
DirectAdmin (https)



rogoproxy.xyz
134.122.122.203
2222
DirectAdmin (https)



rogoproxy.xyz
134.122.122.203
3306
mySql



rogoproxy.xyz
134.122.122.203
3306
mySql



rogoproxy.xyz
134.122.122.203
5224
Plesk Licensing



rogoproxy.xyz
134.122.122.203
5224
Plesk Licensing



rogoproxy.xyz
134.122.122.203
5432
PostgreSQL



rogoproxy.xyz
134.122.122.203
5432
PostgreSQL



rogoproxy.xyz
134.122.122.203
8080
Ookla Speedtest (http)
open
http://134.122.122.203:8080/
Http-Status: 200

rogoproxy.xyz
134.122.122.203
8080
Ookla Speedtest (http)
open
http://134.122.122.203:8080/
Http-Status: 200

rogoproxy.xyz
134.122.122.203
8080
Ookla Speedtest (https)
open
https://134.122.122.203:8080/
Http-Status: -16
UnknownError - The SSL connection could not be established, see inner exception. - Received an unexpected EOF or 0 bytes from the transport stream (FF: PR_END_OF_FILE_ERROR)

rogoproxy.xyz
134.122.122.203
8080
Ookla Speedtest (https)
open
https://134.122.122.203:8080/
Http-Status: -16
UnknownError - The SSL connection could not be established, see inner exception. - Received an unexpected EOF or 0 bytes from the transport stream (FF: PR_END_OF_FILE_ERROR)

rogoproxy.xyz
134.122.122.203
8083
VestaCP http



rogoproxy.xyz
134.122.122.203
8083
VestaCP http



rogoproxy.xyz
134.122.122.203
8083
VestaCP https



rogoproxy.xyz
134.122.122.203
8083
VestaCP https



rogoproxy.xyz
134.122.122.203
8443
Plesk Administration (https)



rogoproxy.xyz
134.122.122.203
8443
Plesk Administration (https)



rogoproxy.xyz
134.122.122.203
8447
Plesk Installer + Updates



rogoproxy.xyz
134.122.122.203
8447
Plesk Installer + Updates



rogoproxy.xyz
134.122.122.203
8880
Plesk Administration (http)



rogoproxy.xyz
134.122.122.203
8880
Plesk Administration (http)



rogoproxy.xyz
134.122.122.203
10000
Webmin (http)



rogoproxy.xyz
134.122.122.203
10000
Webmin (http)



rogoproxy.xyz
134.122.122.203
10000
Webmin (https)



rogoproxy.xyz
134.122.122.203
10000
Webmin (https)





Permalink: https://check-your-website.server-daten.de/?i=2718b4e7-21af-43bb-9038-09fe219221ec


Last Result: https://check-your-website.server-daten.de/?q=rogoproxy.xyz - 2024-04-03 04:55:04


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

<a href="https://check-your-website.server-daten.de/?q=rogoproxy.xyz" target="_blank">Check this Site: rogoproxy.xyz</a>

Do you really want to support this project? Donate: Check-your-website, IBAN DE98 1001 0010 0575 2211 07, SWIFT/BIC PBNKDEFF, Euro