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




Q

http sent over port 443

Checked:
25.01.2023 03:46:28


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
2ulz.com
A
23.184.48.11
Coeur d'Alene/Idaho/United States (US) - IncogNET LLC
No Hostname found
yes
1
0

AAAA
2602:fc24:18:760::1
Coeur d'Alene/Idaho/United States (US) - IncogNet LLC

yes


www.2ulz.com
A
23.184.48.11
Coeur d'Alene/Idaho/United States (US) - IncogNET LLC
No Hostname found
yes
1
0

AAAA
2602:fc24:18:760::1
Coeur d'Alene/Idaho/United States (US) - IncogNet LLC

yes


*.2ulz.com
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes



2. DNSSEC

Zone (*)DNSSEC - Informations

Zone: (root)
(root)
1 DS RR published



DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest 4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=



Status: Valid because published



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 951, Flags 256



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



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 11.02.2023, 00:00:00 +, Signature-Inception: 21.01.2023, 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: com
com
1 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 30909, DigestType 2 and Digest 4tPJFvbe6scylOgmj7WIUESoM/xUWViPSpGEz8QaV2Y=



1 RRSIG RR to validate DS RR found



RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 06.02.2023, 22:00:00 +, Signature-Inception: 24.01.2023, 21:00:00 +, KeyTag 951, Signer-Name: (root)



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



2 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 36739, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 04.02.2023, 18:24:21 +, Signature-Inception: 20.01.2023, 18:19:21 +, KeyTag 30909, Signer-Name: com



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



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

Zone: 2ulz.com
2ulz.com
1 DS RR in the parent zone found



DS with Algorithm 13, KeyTag 40061, DigestType 2 and Digest 7gAhSERchUyfgYKM6y0tW+D1wJGFcJG00fnZUUDD/Fw=



1 RRSIG RR to validate DS RR found



RRSIG-Owner 2ulz.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 30.01.2023, 04:52:01 +, Signature-Inception: 23.01.2023, 03:42:01 +, KeyTag 36739, Signer-Name: com



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



1 DNSKEY RR found



Public Key with Algorithm 13, KeyTag 40061, Flags 257 (SEP = Secure Entry Point)



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner 2ulz.com., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 02.02.2023, 00:00:00 +, Signature-Inception: 12.01.2023, 00:00:00 +, KeyTag 40061, Signer-Name: 2ulz.com



Status: Good - Algorithmus 13 and DNSKEY with KeyTag 40061 used to validate the DNSKEY RRSet



Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 40061, DigestType 2 and Digest "7gAhSERchUyfgYKM6y0tW+D1wJGFcJG00fnZUUDD/Fw=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone



RRSIG Type 1 validates the A - Result: 23.184.48.11
Validated: RRSIG-Owner 2ulz.com., Algorithm: 13, 2 Labels, original TTL: 300 sec, Signature-expiration: 02.02.2023, 00:00:00 +, Signature-Inception: 12.01.2023, 00:00:00 +, KeyTag 40061, Signer-Name: 2ulz.com



RRSIG Type 28 validates the AAAA - Result: 2602:FC24:0018:0760:0000:0000:0000:0001
Validated: RRSIG-Owner 2ulz.com., Algorithm: 13, 2 Labels, original TTL: 300 sec, Signature-expiration: 02.02.2023, 00:00:00 +, Signature-Inception: 12.01.2023, 00:00:00 +, KeyTag 40061, Signer-Name: 2ulz.com



CNAME-Query sends a valid NSEC RR as result with the query name "2ulz.com" equal the NSEC-owner "2ulz.com" and the NextOwner "www.2ulz.com". So the zone confirmes the not-existence of that CNAME RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, NS, SOA, AAAA, RRSIG, NSEC, DNSKEY Validated: RRSIG-Owner 2ulz.com., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 02.02.2023, 00:00:00 +, Signature-Inception: 12.01.2023, 00:00:00 +, KeyTag 40061, Signer-Name: 2ulz.com



Status: Good. NoData-Proof required and found.



TXT-Query sends a valid NSEC RR as result with the query name "2ulz.com" equal the NSEC-owner "2ulz.com" and the NextOwner "www.2ulz.com". So the zone confirmes the not-existence of that TXT RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, NS, SOA, AAAA, RRSIG, NSEC, DNSKEY Validated: RRSIG-Owner 2ulz.com., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 02.02.2023, 00:00:00 +, Signature-Inception: 12.01.2023, 00:00:00 +, KeyTag 40061, Signer-Name: 2ulz.com



Status: Good. NoData-Proof required and found.



TLSA-Query (_443._tcp.2ulz.com) sends a valid NSEC RR as result with the owner name 2ulz.com. So that's the Closest Encloser of the query name. TLSA-Query sends a valid NSEC RR as result and covers the Wildcard expansion of the ClosestEncloser with the owner "2ulz.com" and the NextOwner "www.2ulz.com". So that NSEC confirms the not-existence of the Wildcard expansion. TLSA-Query (_443._tcp.2ulz.com) sends a valid NSEC RR as result with the query name "_443._tcp.2ulz.com" between the NSEC-owner "2ulz.com" and the NextOwner "www.2ulz.com". So the zone confirmes the not-existence of that TLSA RR.TLSA-Query (_443._tcp.2ulz.com) sends a valid NSEC RR as result with the parent Wildcard "*._tcp.2ulz.com" between the NSEC-owner "2ulz.com" and the NextOwner "www.2ulz.com". So the zone confirmes the not-existence of that Wildcard-expansion.
Bitmap: A, NS, SOA, AAAA, RRSIG, NSEC, DNSKEY Validated: RRSIG-Owner 2ulz.com., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 02.02.2023, 00:00:00 +, Signature-Inception: 12.01.2023, 00:00:00 +, KeyTag 40061, Signer-Name: 2ulz.com



Status: Good. NXDomain-Proof required and found.



CAA-Query sends a valid NSEC RR as result with the query name "2ulz.com" equal the NSEC-owner "2ulz.com" and the NextOwner "www.2ulz.com". So the zone confirmes the not-existence of that CAA RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, NS, SOA, AAAA, RRSIG, NSEC, DNSKEY Validated: RRSIG-Owner 2ulz.com., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 02.02.2023, 00:00:00 +, Signature-Inception: 12.01.2023, 00:00:00 +, KeyTag 40061, Signer-Name: 2ulz.com



Status: Good. NoData-Proof required and found.

Zone: www.2ulz.com
www.2ulz.com
0 DS RR in the parent zone found



DS-Query in the parent zone has a valid NSEC RR as result with the domain name between the NSEC-Owner "www.2ulz.com" and the NextOwner "2ulz.com". So the parent zone confirmes the non-existence of a DS RR.
Bitmap: A, AAAA, RRSIG, NSEC



RRSIG Type 1 validates the A - Result: 23.184.48.11
Validated: RRSIG-Owner www.2ulz.com., Algorithm: 13, 3 Labels, original TTL: 300 sec, Signature-expiration: 02.02.2023, 00:00:00 +, Signature-Inception: 12.01.2023, 00:00:00 +, KeyTag 40061, Signer-Name: 2ulz.com



RRSIG Type 28 validates the AAAA - Result: 2602:FC24:0018:0760:0000:0000:0000:0001
Validated: RRSIG-Owner www.2ulz.com., Algorithm: 13, 3 Labels, original TTL: 300 sec, Signature-expiration: 02.02.2023, 00:00:00 +, Signature-Inception: 12.01.2023, 00:00:00 +, KeyTag 40061, Signer-Name: 2ulz.com



CNAME-Query sends a valid NSEC RR as result with the query name "www.2ulz.com" equal the NSEC-owner "www.2ulz.com" and the NextOwner "2ulz.com". So the zone confirmes the not-existence of that CNAME RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, AAAA, RRSIG, NSEC Validated: RRSIG-Owner www.2ulz.com., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 02.02.2023, 00:00:00 +, Signature-Inception: 12.01.2023, 00:00:00 +, KeyTag 40061, Signer-Name: 2ulz.com



Status: Good. NoData-Proof required and found.



TXT-Query sends a valid NSEC RR as result with the query name "www.2ulz.com" equal the NSEC-owner "www.2ulz.com" and the NextOwner "2ulz.com". So the zone confirmes the not-existence of that TXT RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, AAAA, RRSIG, NSEC Validated: RRSIG-Owner www.2ulz.com., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 02.02.2023, 00:00:00 +, Signature-Inception: 12.01.2023, 00:00:00 +, KeyTag 40061, Signer-Name: 2ulz.com



Status: Good. NoData-Proof required and found.



TLSA-Query (_443._tcp.www.2ulz.com) sends a valid NSEC RR as result with the owner name www.2ulz.com. So that's the Closest Encloser of the query name. TLSA-Query sends a valid NSEC RR as result and covers the Wildcard expansion of the ClosestEncloser with the owner "www.2ulz.com" and the NextOwner "2ulz.com". So that NSEC confirms the not-existence of the Wildcard expansion. TLSA-Query (_443._tcp.www.2ulz.com) sends a valid NSEC RR as result with the query name "_443._tcp.www.2ulz.com" between the NSEC-owner "www.2ulz.com" and the NextOwner "2ulz.com". So the zone confirmes the not-existence of that TLSA RR.TLSA-Query (_443._tcp.www.2ulz.com) sends a valid NSEC RR as result with the parent Wildcard "*._tcp.www.2ulz.com" between the NSEC-owner "www.2ulz.com" and the NextOwner "2ulz.com". So the zone confirmes the not-existence of that Wildcard-expansion.
Bitmap: A, AAAA, RRSIG, NSEC Validated: RRSIG-Owner www.2ulz.com., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 02.02.2023, 00:00:00 +, Signature-Inception: 12.01.2023, 00:00:00 +, KeyTag 40061, Signer-Name: 2ulz.com



Status: Good. NXDomain-Proof required and found.



CAA-Query sends a valid NSEC RR as result with the query name "www.2ulz.com" equal the NSEC-owner "www.2ulz.com" and the NextOwner "2ulz.com". So the zone confirmes the not-existence of that CAA RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, AAAA, RRSIG, NSEC Validated: RRSIG-Owner www.2ulz.com., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 02.02.2023, 00:00:00 +, Signature-Inception: 12.01.2023, 00:00:00 +, KeyTag 40061, Signer-Name: 2ulz.com



Status: Good. NoData-Proof required and found.


3. Name Servers

DomainNameserverNS-IP
www.2ulz.com
  ns3.epik.com / dns-ams-nl.epik.com

2ulz.com
  ns3.epik.com / dns-ams-nl.epik.com
45.88.202.88
Sammamish/Washington/United States (US) - K4X OU


 
91.149.194.88
Zurich/Switzerland (CH) - K4X OU


  ns4.epik.com / dns-ams-nl.epik.com
45.88.202.188
Sammamish/Washington/United States (US) - K4X OU


 
91.149.194.188
Zurich/Switzerland (CH) - K4X OU

com
  a.gtld-servers.net / nnn1-fra6


  b.gtld-servers.net / nnn1-elpar7


  c.gtld-servers.net / nnn1-fra6


  d.gtld-servers.net / nnn1-fra6


  e.gtld-servers.net / nnn1-fra6


  f.gtld-servers.net / nnn1-fra5


  g.gtld-servers.net / nnn1-fra5


  h.gtld-servers.net / nnn1-fra5


  i.gtld-servers.net / nnn1-fra5


  j.gtld-servers.net / nnn1-nlams-1d


  k.gtld-servers.net / nnn1-nlams-1c


  l.gtld-servers.net / nnn1-nlams-1c


  m.gtld-servers.net / nnn1-nlams-1d


4. SOA-Entries


Domain:com
Zone-Name:com
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1674614770
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:8


Domain:com
Zone-Name:com
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1674614785
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:5


Domain:2ulz.com
Zone-Name:2ulz.com
Primary:ns3.epik.com
Mail:support.epik.com
Serial:2023012402
Refresh:10800
Retry:3600
Expire:604800
TTL:3600
num Entries:4


Domain:www.2ulz.com
Zone-Name:2ulz.com
Primary:ns3.epik.com
Mail:support.epik.com
Serial:2023012402
Refresh:10800
Retry:3600
Expire:604800
TTL:3600
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://2ulz.com/
23.184.48.11 GZip used - 3121 / 10671 - 70.75 %
200

Html is minified: 213.76 %
0.357
H
Date: Wed, 25 Jan 2023 02:47:18 GMT
Server: Apache/2.4.52 (Ubuntu)
Last-Modified: Tue, 24 Jan 2023 06:54:21 GMT
ETag: "29af-5f2fcfc3e6f2c-gzip"
Accept-Ranges: bytes
Vary: Accept-Encoding
Content-Encoding: gzip
Content-Length: 3121
Connection: close
Content-Type: text/html

• http://2ulz.com/
2602:fc24:18:760::1
-14

10.044
T
Timeout - The operation has timed out

• http://www.2ulz.com/
23.184.48.11 GZip used - 3121 / 10671 - 70.75 %
200

Html is minified: 213.76 %
0.366
H
Date: Wed, 25 Jan 2023 02:47:28 GMT
Server: Apache/2.4.52 (Ubuntu)
Last-Modified: Tue, 24 Jan 2023 06:54:21 GMT
ETag: "29af-5f2fcfc3e6f2c-gzip"
Accept-Ranges: bytes
Vary: Accept-Encoding
Content-Encoding: gzip
Content-Length: 3121
Connection: close
Content-Type: text/html

• http://www.2ulz.com/
2602:fc24:18:760::1
-14

10.034
T
Timeout - The operation has timed out

• https://2ulz.com/
23.184.48.11
-4

0.686
W
SendFailure - The underlying connection was closed: An unexpected error occurred on a send.

• https://2ulz.com/
2602:fc24:18:760::1
-14

10.053
T
Timeout - The operation has timed out

• https://www.2ulz.com/
23.184.48.11
-4

0.684
W
SendFailure - The underlying connection was closed: An unexpected error occurred on a send.

• https://www.2ulz.com/
2602:fc24:18:760::1
-14

10.036
T
Timeout - The operation has timed out

• http://2ulz.com:443/
23.184.48.11 GZip used - 3121 / 10671 - 70.75 %
200

Html is minified: 213.76 %
0.520
Q
Visible Content: Apache2 Default Page It works! This is the default welcome page used to test the correct operation of the Apache2 server after installation on Ubuntu systems. It is based on the equivalent page on Debian, from which the Ubuntu Apache packaging is derived. If you can read this page, it means that the Apache HTTP server installed at this site is working properly. You should replace this file (located at /var/www/html/index.html ) before continuing to operate your HTTP server. If you are a normal user of this web site and don't know what this page is about, this probably means that the site is currently unavailable due to maintenance. If the problem persists, please contact the site's administrator. Configuration Overview Ubuntu's Apache2 default configuration is different from the upstream default configuration, and split into several files optimized for interaction with Ubuntu tools. The configuration system is fully documented in /usr/share/doc/apache2/README.Debian.gz . Refer to this for the full documentation. Documentation for the web server itself can be found by accessing the manual if the apache2-doc package was installed on this server. The configuration layout for an Apache2 web server installation on Ubuntu systems is as follows: /etc/apache2/ |-- apache2.conf | `-- ports.conf |-- mods-enabled | |-- *.load | `-- *.conf |-- conf-enabled | `-- *.conf |-- sites-enabled | `-- *.conf apache2.conf is the main configuration file. It puts the pieces together by including all remaining configuration files when starting up the web server. ports.conf is always included from the main configuration file. It is used to determine the listening ports for incoming connections, and this file can be customized anytime. Configuration files in the mods-enabled/ , conf-enabled/ and sites-enabled/ directories contain particular configuration snippets which manage modules, global configuration fragments, or virtual host configurations, respectively. They are activated by symlinking available configuration files from their respective *-available/ counterparts. These should be managed by using our helpers a2enmod, a2dismod, a2ensite, a2dissite, and a2enconf, a2disconf . See their respective man pages for detailed information. The binary is called apache2 and is managed using systemd, so to start/stop the service use systemctl start apache2 and systemctl stop apache2 , and use systemctl status apache2 and journalctl -u apache2 to check status. system and apache2ctl can also be used for service management if desired. Calling /usr/bin/apache2 directly will not work with the default configuration. Document Roots By default, Ubuntu does not allow access through the web browser to any file outside of those located in /var/www , public_html directories (when enabled) and /usr/share (for web applications). If your site is using a web document root located elsewhere (such as in /srv ) you may need to whitelist your document root directory in /etc/apache2/apache2.conf . The default Ubuntu document root is /var/www/html . You can make your own virtual hosts under /var/www. Reporting Problems Please use the ubuntu-bug tool to report bugs in the Apache2 package with Ubuntu. However, check existing bug reports before reporting a new bug. Please report bugs specific to modules (such as PHP and others) to their respective packages, not to the web server itself.
Date: Wed, 25 Jan 2023 02:48:22 GMT
Server: Apache/2.4.52 (Ubuntu)
Last-Modified: Tue, 24 Jan 2023 06:54:21 GMT
ETag: "29af-5f2fcfc3e6f2c-gzip"
Accept-Ranges: bytes
Vary: Accept-Encoding
Content-Encoding: gzip
Content-Length: 3121
Connection: close
Content-Type: text/html

• http://2ulz.com:443/
2602:fc24:18:760::1
-14

10.033
A
Timeout - The operation has timed out
Visible Content:

• http://www.2ulz.com:443/
23.184.48.11 GZip used - 3121 / 10671 - 70.75 %
200

Html is minified: 213.76 %
0.347
Q
Visible Content: Apache2 Default Page It works! This is the default welcome page used to test the correct operation of the Apache2 server after installation on Ubuntu systems. It is based on the equivalent page on Debian, from which the Ubuntu Apache packaging is derived. If you can read this page, it means that the Apache HTTP server installed at this site is working properly. You should replace this file (located at /var/www/html/index.html ) before continuing to operate your HTTP server. If you are a normal user of this web site and don't know what this page is about, this probably means that the site is currently unavailable due to maintenance. If the problem persists, please contact the site's administrator. Configuration Overview Ubuntu's Apache2 default configuration is different from the upstream default configuration, and split into several files optimized for interaction with Ubuntu tools. The configuration system is fully documented in /usr/share/doc/apache2/README.Debian.gz . Refer to this for the full documentation. Documentation for the web server itself can be found by accessing the manual if the apache2-doc package was installed on this server. The configuration layout for an Apache2 web server installation on Ubuntu systems is as follows: /etc/apache2/ |-- apache2.conf | `-- ports.conf |-- mods-enabled | |-- *.load | `-- *.conf |-- conf-enabled | `-- *.conf |-- sites-enabled | `-- *.conf apache2.conf is the main configuration file. It puts the pieces together by including all remaining configuration files when starting up the web server. ports.conf is always included from the main configuration file. It is used to determine the listening ports for incoming connections, and this file can be customized anytime. Configuration files in the mods-enabled/ , conf-enabled/ and sites-enabled/ directories contain particular configuration snippets which manage modules, global configuration fragments, or virtual host configurations, respectively. They are activated by symlinking available configuration files from their respective *-available/ counterparts. These should be managed by using our helpers a2enmod, a2dismod, a2ensite, a2dissite, and a2enconf, a2disconf . See their respective man pages for detailed information. The binary is called apache2 and is managed using systemd, so to start/stop the service use systemctl start apache2 and systemctl stop apache2 , and use systemctl status apache2 and journalctl -u apache2 to check status. system and apache2ctl can also be used for service management if desired. Calling /usr/bin/apache2 directly will not work with the default configuration. Document Roots By default, Ubuntu does not allow access through the web browser to any file outside of those located in /var/www , public_html directories (when enabled) and /usr/share (for web applications). If your site is using a web document root located elsewhere (such as in /srv ) you may need to whitelist your document root directory in /etc/apache2/apache2.conf . The default Ubuntu document root is /var/www/html . You can make your own virtual hosts under /var/www. Reporting Problems Please use the ubuntu-bug tool to report bugs in the Apache2 package with Ubuntu. However, check existing bug reports before reporting a new bug. Please report bugs specific to modules (such as PHP and others) to their respective packages, not to the web server itself.
Date: Wed, 25 Jan 2023 02:48:32 GMT
Server: Apache/2.4.52 (Ubuntu)
Last-Modified: Tue, 24 Jan 2023 06:54:21 GMT
ETag: "29af-5f2fcfc3e6f2c-gzip"
Accept-Ranges: bytes
Vary: Accept-Encoding
Content-Encoding: gzip
Content-Length: 3121
Connection: close
Content-Type: text/html

• http://www.2ulz.com:443/
2602:fc24:18:760::1
-14

10.007
A
Timeout - The operation has timed out
Visible Content:

• http://2ulz.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
23.184.48.11
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
404

Html is minified: 100.00 %
0.354
A
Not Found
Visible Content: Not Found The requested URL was not found on this server. Apache/2.4.52 (Ubuntu) Server at 2ulz.com Port 80
Date: Wed, 25 Jan 2023 02:48:00 GMT
Server: Apache/2.4.52 (Ubuntu)
Content-Length: 270
Connection: close
Content-Type: text/html; charset=iso-8859-1

• http://2ulz.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
2602:fc24:18:760::1
-14

10.027
T
Timeout - The operation has timed out
Visible Content:

• http://www.2ulz.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
23.184.48.11
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
404

Html is minified: 100.00 %
0.350
A
Not Found
Visible Content: Not Found The requested URL was not found on this server. Apache/2.4.52 (Ubuntu) Server at www.2ulz.com Port 80
Date: Wed, 25 Jan 2023 02:48:11 GMT
Server: Apache/2.4.52 (Ubuntu)
Content-Length: 274
Connection: close
Content-Type: text/html; charset=iso-8859-1

• http://www.2ulz.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
2602:fc24:18:760::1
-14

10.044
T
Timeout - The operation has timed out
Visible Content:

• https://23.184.48.11/
23.184.48.11
-4

0.700
W
SendFailure - The underlying connection was closed: An unexpected error occurred on a send.

• https://[2602:fc24:0018:0760:0000:0000:0000:0001]/
2602:fc24:18:760::1
-14

10.037
T
Timeout - The operation has timed out

7. Comments


1. General Results, most used to calculate the result

Aname "2ulz.com" is domain, public suffix is ".com", top-level-domain is ".com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .com-domains preloaded: 83852 (complete: 216710)
AGood: All ip addresses are public addresses
AGood: Minimal 2 ip addresses per domain name found: 2ulz.com has 2 different ip addresses (authoritative).
AGood: Minimal 2 ip addresses per domain name found: www.2ulz.com has 2 different ip addresses (authoritative).
AGood: Ipv4 and Ipv6 addresses per domain name found: 2ulz.com has 1 ipv4, 1 ipv6 addresses
AGood: Ipv4 and Ipv6 addresses per domain name found: www.2ulz.com has 1 ipv4, 1 ipv6 addresses
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: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):2 complete Content-Type - header (6 urls)
http://2ulz.com/ 23.184.48.11


Url with incomplete Content-Type - header - missing charset
http://2ulz.com:443/ 23.184.48.11


Url with incomplete Content-Type - header - missing charset
http://www.2ulz.com:443/ 23.184.48.11


Url with incomplete Content-Type - header - missing charset
http://www.2ulz.com/ 23.184.48.11


Url with incomplete Content-Type - header - missing charset
HFatal error: No https - result with http-status 200, no encryption
HFatal error: http result with http-status 200, no encryption. Add a redirect http ⇒ https, so every connection is secure. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop.
Khttp://2ulz.com/ 23.184.48.11, Status 200

http://2ulz.com/ 2602:fc24:18:760::1, Status -14
Configuration problem - different ip addresses with different status
Khttp://www.2ulz.com/ 23.184.48.11, Status 200

http://www.2ulz.com/ 2602:fc24:18:760::1, Status -14
Configuration problem - different ip addresses with different status
Khttps://2ulz.com/ 23.184.48.11, Status -4

https://2ulz.com/ 2602:fc24:18:760::1, Status -14
Configuration problem - different ip addresses with different status
Khttps://www.2ulz.com/ 23.184.48.11, Status -4

https://www.2ulz.com/ 2602:fc24:18:760::1, Status -14
Configuration problem - different ip addresses with different status
Khttp://2ulz.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 23.184.48.11, Status 404

http://2ulz.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2602:fc24:18:760::1, Status -14
Configuration problem - different ip addresses with different status
Khttp://www.2ulz.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 23.184.48.11, Status 404

http://www.2ulz.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2602:fc24:18:760::1, Status -14
Configuration problem - different ip addresses with different status
Khttp://2ulz.com:443/ 23.184.48.11, Status 200

http://2ulz.com:443/ 2602:fc24:18:760::1, Status -14
Configuration problem - different ip addresses with different status
Khttp://www.2ulz.com:443/ 23.184.48.11, Status 200

http://www.2ulz.com:443/ 2602:fc24:18:760::1, Status -14
Configuration problem - different ip addresses with different status
Qhttp://2ulz.com:443/ 23.184.48.11
200

Misconfiguration: http sent over port 443. Wrong port forwarding port 443 to port 80 or wrong vHost definition. If you use a virtual Host <VirtualHost ip-address:443>, try <VirtualHost *:443>.
Qhttp://www.2ulz.com:443/ 23.184.48.11
200

Misconfiguration: http sent over port 443. Wrong port forwarding port 443 to port 80 or wrong vHost definition. If you use a virtual Host <VirtualHost ip-address:443>, try <VirtualHost *:443>.
AGood: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain 2ulz.com, 2 ip addresses.
AGood: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain www.2ulz.com, 2 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 2ulz.com, 2 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.2ulz.com, 2 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.2ulz.com

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

U

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

3. DNS- and NameServer - Checks

AInfo:: 2 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
AInfo:: 2 Queries complete, 2 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
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.ns3.epik.com (45.88.202.88, 91.149.194.88), ns4.epik.com (45.88.202.188, 91.149.194.188)
AGood (1 - 3.0):: An average of 1.0 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 2 different Name Servers found: ns3.epik.com, ns4.epik.com, 2 Name Servers included in Delegation: ns3.epik.com, ns4.epik.com, 2 Name Servers included in 1 Zone definitions: ns3.epik.com, ns4.epik.com, 1 Name Servers listed in SOA.Primary: ns3.epik.com.
AGood: Only one SOA.Primary Name Server found.: ns3.epik.com.
AGood: SOA.Primary Name Server included in the delegation set.: ns3.epik.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: ns3.epik.com, ns4.epik.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: 2 different Name Servers found
Warning: No Name Server IPv6 address found. IPv6 is the future, so your name servers should be visible via IPv6.: 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: 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: epik.com
AGood: Name servers with different Country locations found: 2 Name Servers, 2 Countries: CH, US
AInfo: Ipv4-Subnet-list: 4 Name Servers, 2 different subnets (first Byte): 45., 91., 2 different subnets (first two Bytes): 45.88., 91.149., 2 different subnets (first three Bytes): 45.88.202., 91.149.194.
AGood: Name Server IPv4-addresses from different subnet found:
AGood: Nameserver supports TCP connections: 4 good Nameserver
AGood: Nameserver supports Echo Capitalization: 4 good Nameserver
XFatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: ns3.epik.com
XFatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: ns4.epik.com
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 4 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

http://2ulz.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2602:fc24:18:760::1
-14

Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
http://www.2ulz.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2602:fc24:18:760::1
-14

Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
http://2ulz.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2602:fc24:18:760::1, Status -14

http://2ulz.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 23.184.48.11, Status 404
Fatal: Check of /.well-known/acme-challenge/random-filename has different answers checking ipv6 / ipv4. Ipv6 doesn't have the expected result http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 validation may not work. Checking the validation file in /.well-known/acme-challenge Letsencrypt prefers ipv6. Two options: Remove your ipv6 / AAAA DNS entry or (better) fix your ipv6, so your webserver handles ipv6 correct. Perhaps add "Listen [::]:80". Don't use <VirtualHost ip-address:80>, switch to <VirtualHost *:80>. If you use IIS, check your bindings. Don't select a single ip address. Use this tool to check your raw ipv6 address. Add your domain name in the "Hostname" - field. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
http://www.2ulz.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2602:fc24:18:760::1, Status -14

http://www.2ulz.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 23.184.48.11, Status 404
Fatal: Check of /.well-known/acme-challenge/random-filename has different answers checking ipv6 / ipv4. Ipv6 doesn't have the expected result http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 validation may not work. Checking the validation file in /.well-known/acme-challenge Letsencrypt prefers ipv6. Two options: Remove your ipv6 / AAAA DNS entry or (better) fix your ipv6, so your webserver handles ipv6 correct. Perhaps add "Listen [::]:80". Don't use <VirtualHost ip-address:80>, switch to <VirtualHost *:80>. If you use IIS, check your bindings. Don't select a single ip address. Use this tool to check your raw ipv6 address. Add your domain name in the "Hostname" - field. 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: 189620 milliseconds, 189.620 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: ns3.epik.com, ns4.epik.com

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

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
ns3.epik.com: 45.88.202.88, 91.149.194.88
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns4.epik.com
45.88.202.188, 91.149.194.188


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.2ulz.com
0

no CAA entry found
1
0
2ulz.com
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
2ulz.com

ok
1
0
www.2ulz.com

ok
1
0
_acme-challenge.2ulz.com

Name Error - The domain name does not exist
1
0
_acme-challenge.www.2ulz.com

Name Error - The domain name does not exist
1
0
_acme-challenge.2ulz.com.2ulz.com

Name Error - The domain name does not exist
1
0
_acme-challenge.www.2ulz.com.2ulz.com

Name Error - The domain name does not exist
1
0
_acme-challenge.www.2ulz.com.www.2ulz.com

Name Error - The domain name does not exist
1
0


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

No DomainServiceEntries entries found



16. Cipher Suites

No results


17. Portchecks

No open Ports <> 80 / 443 found, so no additional Ports checked.



Permalink: https://check-your-website.server-daten.de/?i=98399bd1-26d4-446a-834c-ca07d9556a2f


Last Result: https://check-your-website.server-daten.de/?q=2ulz.com - 2023-01-25 03:46:28


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

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

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