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

0 in Queue, 2 of max. 4 Checks (11:14:58)
Why should you only use Prefix - Cookies? |
Hall of Fame - A+ and A


Shortcuts: 1. IP-Addresses | 2. DNSSEC | 3. Name Servers | 4. SOA-Entries | 5. Screenshots | 6. Url-Checks | 7. Comments | 8. Connections | 9. Certificates | 10. CT-Logs | 11. Html-Content | 12. NameServer-IPAddresses | 13. CAA | 14. TXT | 15. DomainServiceEntries | 16. Cipher Suites | 17. Portchecks |


Q

http sent over port 443

Checked:
17.03.2023 20:16:15


Older results

Q - 17.03.2023 20:12:55


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
signaling.netzhammer.ch
CNAME
remote.netzhammer.ch
yes
1
0

A
178.174.29.18
Morat/Fribourg/Switzerland (CH) - Swisscom (Schweiz) AG - SME
Hostname: 18.29.174.178.static.wline.lns.sme.cust.swisscom.ch
yes


www.signaling.netzhammer.ch

Name Error
yes
1
0
*.netzhammer.ch
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes


*.signaling.netzhammer.ch
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: 02.04.2023, 00:00:00 +, Signature-Inception: 12.03.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: ch
ch
1 DS RR in the parent zone found



DS with Algorithm 13, KeyTag 10, DigestType 2 and Digest DhdVQ6dNkIPql3urK+6Yp3GZX4CYL7eWsrC5zGQT0aY=



2 RRSIG RR to validate DS RR found



RRSIG-Owner ch., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 30.03.2023, 17:00:00 +, Signature-Inception: 17.03.2023, 16: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



3 DNSKEY RR found



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



Public Key with Algorithm 13, KeyTag 38675, Flags 256



Public Key with Algorithm 13, KeyTag 40115, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner ch., Algorithm: 13, 1 Labels, original TTL: 86400 sec, Signature-expiration: 15.04.2023, 10:09:09 +, Signature-Inception: 28.02.2023, 09:09:09 +, KeyTag 10, Signer-Name: ch



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



• Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 10, DigestType 2 and Digest "DhdVQ6dNkIPql3urK+6Yp3GZX4CYL7eWsrC5zGQT0aY=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: netzhammer.ch
netzhammer.ch
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 "v12t5r2125kp6o87lfk3cl56n4nodpus" between the hashed NSEC3-owner "v12t3kfqs2m23vhartp1jslkn1q2s7c6" and the hashed NextOwner "v12u9ge3c0tk7flikogm8tssjrpkdqbd". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner v12t3kfqs2m23vhartp1jslkn1q2s7c6.ch., Algorithm: 13, 2 Labels, original TTL: 900 sec, Signature-expiration: 07.04.2023, 23:49:16 +, Signature-Inception: 08.03.2023, 23:03:08 +, KeyTag 40115, Signer-Name: ch



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "nd3e0cgf5ogc08781sojkfrioogbgc7e" as Owner. That's the Hash of "ch" with the NextHashedOwnerName "nd3fvij6p2hthsrmnp8blkrqo4274if6". So that domain name is the Closest Encloser of "netzhammer.ch". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner nd3e0cgf5ogc08781sojkfrioogbgc7e.ch., Algorithm: 13, 2 Labels, original TTL: 900 sec, Signature-expiration: 11.04.2023, 02:11:26 +, Signature-Inception: 12.03.2023, 02:03:00 +, KeyTag 40115, Signer-Name: ch



0 DNSKEY RR found




Zone: signaling.netzhammer.ch
signaling.netzhammer.ch
0 DS RR in the parent zone found

Zone: www.signaling.netzhammer.ch
www.signaling.netzhammer.ch
0 DS RR in the parent zone found

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: 02.04.2023, 00:00:00 +, Signature-Inception: 12.03.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: ch
ch
1 DS RR in the parent zone found



DS with Algorithm 13, KeyTag 10, DigestType 2 and Digest DhdVQ6dNkIPql3urK+6Yp3GZX4CYL7eWsrC5zGQT0aY=



2 RRSIG RR to validate DS RR found



RRSIG-Owner ch., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 30.03.2023, 17:00:00 +, Signature-Inception: 17.03.2023, 16: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



3 DNSKEY RR found



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



Public Key with Algorithm 13, KeyTag 38675, Flags 256



Public Key with Algorithm 13, KeyTag 40115, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner ch., Algorithm: 13, 1 Labels, original TTL: 86400 sec, Signature-expiration: 15.04.2023, 10:09:09 +, Signature-Inception: 28.02.2023, 09:09:09 +, KeyTag 10, Signer-Name: ch



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



• Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 10, DigestType 2 and Digest "DhdVQ6dNkIPql3urK+6Yp3GZX4CYL7eWsrC5zGQT0aY=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: netzhammer.ch
netzhammer.ch
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 "v12t5r2125kp6o87lfk3cl56n4nodpus" between the hashed NSEC3-owner "v12t3kfqs2m23vhartp1jslkn1q2s7c6" and the hashed NextOwner "v12u9ge3c0tk7flikogm8tssjrpkdqbd". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner v12t3kfqs2m23vhartp1jslkn1q2s7c6.ch., Algorithm: 13, 2 Labels, original TTL: 900 sec, Signature-expiration: 07.04.2023, 23:49:16 +, Signature-Inception: 08.03.2023, 23:03:08 +, KeyTag 40115, Signer-Name: ch



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "nd3e0cgf5ogc08781sojkfrioogbgc7e" as Owner. That's the Hash of "ch" with the NextHashedOwnerName "nd3fvij6p2hthsrmnp8blkrqo4274if6". So that domain name is the Closest Encloser of "netzhammer.ch". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner nd3e0cgf5ogc08781sojkfrioogbgc7e.ch., Algorithm: 13, 2 Labels, original TTL: 900 sec, Signature-expiration: 11.04.2023, 02:11:26 +, Signature-Inception: 12.03.2023, 02:03:00 +, KeyTag 40115, Signer-Name: ch



0 DNSKEY RR found




Zone: remote.netzhammer.ch
remote.netzhammer.ch
0 DS RR in the parent zone found



0 DNSKEY RR found




3. Name Servers

DomainNameserverNS-IP
www.signaling.netzhammer.ch
•  dns1.katta.ch

netzhammer.ch
•  dns1.katta.ch
62.12.134.50
Au/Zurich/Switzerland (CH) - Cyberlink Internet Services AG		•

•  dns2.katta.ch
62.12.134.61
Au/Zurich/Switzerland (CH) - Cyberlink Internet Services AG		•

•  dns3.katta.ch
83.150.62.67
Chur/Grisons/Switzerland (CH) - iWay AG		•
ch
•  a.nic.ch / lako.switch.ch
•

•  b.nic.ch / wako.switch.ch
•

•  d.nic.ch / tld-all-fam1@53039
•

•  e.nic.ch / 1.ber.pch
•

•  f.nic.ch / s2.wie
•
remote.netzhammer.ch
•  dns1.katta.ch
62.12.134.50
Au/Zurich/Switzerland (CH) - Cyberlink Internet Services AG		•
netzhammer.ch
•  dns1.katta.ch
62.12.134.50
Au/Zurich/Switzerland (CH) - Cyberlink Internet Services AG		•

•  dns2.katta.ch
62.12.134.61
Au/Zurich/Switzerland (CH) - Cyberlink Internet Services AG		•

•  dns3.katta.ch
83.150.62.67
Chur/Grisons/Switzerland (CH) - iWay AG		•
ch
•  a.nic.ch / lako.switch.ch
•

•  b.nic.ch / wako.switch.ch
•

•  d.nic.ch / tld-all-fam1@53039
•

•  e.nic.ch / 1.ber.pch
•

•  f.nic.ch / s2.wie
•


4. SOA-Entries


Domain:ch
Zone-Name:ch
Primary:a.nic.ch
Mail:dns-operation.switch.ch
Serial:2023031719
Refresh:900
Retry:600
Expire:1123200
TTL:900
num Entries:1


Domain:ch
Zone-Name:ch
Primary:a.nic.ch
Mail:dns-operation.switch.ch
Serial:2023031720
Refresh:900
Retry:600
Expire:1123200
TTL:900
num Entries:4


Domain:netzhammer.ch
Zone-Name:netzhammer.ch
Primary:dns1.katta.ch
Mail:hostmaster.asp.katta.ch
Serial:2016032424
Refresh:10800
Retry:3600
Expire:604800
TTL:86400
num Entries:3


Domain:www.signaling.netzhammer.ch
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


Domain:ch
Zone-Name:ch
Primary:a.nic.ch
Mail:dns-operation.switch.ch
Serial:2023031719
Refresh:900
Retry:600
Expire:1123200
TTL:900
num Entries:1


Domain:ch
Zone-Name:ch
Primary:a.nic.ch
Mail:dns-operation.switch.ch
Serial:2023031720
Refresh:900
Retry:600
Expire:1123200
TTL:900
num Entries:4


Domain:netzhammer.ch
Zone-Name:netzhammer.ch
Primary:dns1.katta.ch
Mail:hostmaster.asp.katta.ch
Serial:2016032424
Refresh:10800
Retry:3600
Expire:604800
TTL:86400
num Entries:3


Domain:remote.netzhammer.ch
Zone-Name:netzhammer.ch
Primary:dns1.katta.ch
Mail:hostmaster.asp.katta.ch
Serial:2016032424
Refresh:10800
Retry:3600
Expire:604800
TTL:86400
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://signaling.netzhammer.ch/
178.174.29.18 GZip used - 384 / 612 - 37.25 %
200

Html is minified: 129.94 %		0.053
H
small visible content (num chars: 273)
Welcome to nginx! If you see this page, the nginx web server is successfully installed and working. Further configuration is required. For online documentation and support please refer to nginx.org . Commercial support is available at nginx.com . Thank you for using nginx.
Server: nginx/1.18.0 (Ubuntu)
Date: Fri, 17 Mar 2023 19:17:01 GMT
Content-Type: text/html
Last-Modified: Fri, 17 Mar 2023 18:27:59 GMT
Transfer-Encoding: chunked
Connection: close
ETag: W/"6414b12f-264"
Content-Encoding: gzip

• https://signaling.netzhammer.ch/
178.174.29.18
-4

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

• http://signaling.netzhammer.ch:443/
178.174.29.18 GZip used - 384 / 612 - 37.25 %
200

Html is minified: 129.94 %		0.050
Q
Visible Content: Welcome to nginx! If you see this page, the nginx web server is successfully installed and working. Further configuration is required. For online documentation and support please refer to nginx.org . Commercial support is available at nginx.com . Thank you for using nginx.
Server: nginx/1.18.0 (Ubuntu)
Date: Fri, 17 Mar 2023 19:17:01 GMT
Content-Type: text/html
Last-Modified: Fri, 17 Mar 2023 18:27:59 GMT
Transfer-Encoding: chunked
Connection: close
ETag: W/"6414b12f-264"
Content-Encoding: gzip

• http://signaling.netzhammer.ch/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
178.174.29.18 GZip used - 123 / 162 - 24.07 %
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0		404

Html is minified: 109.46 %		0.054
A
Not Found
Visible Content: 404 Not Found nginx/1.18.0 (Ubuntu)
Server: nginx/1.18.0 (Ubuntu)
Date: Fri, 17 Mar 2023 19:17:01 GMT
Content-Type: text/html
Transfer-Encoding: chunked
Connection: close
Content-Encoding: gzip

• https://178.174.29.18/
178.174.29.18
-4

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

7. Comments


1. General Results, most used to calculate the result

Aname "signaling.netzhammer.ch" is subdomain, public suffix is ".ch", top-level-domain is ".ch", top-level-domain-type is "country-code", Country is Switzerland, tld-manager is "SWITCH The Swiss Education & Research Network", num .ch-domains preloaded: 2000 (complete: 220007)
AGood: All ip addresses are public addresses
Warning: Only one ip address found: signaling.netzhammer.ch 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: signaling.netzhammer.ch 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: 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):0 complete Content-Type - header (3 urls)
http://signaling.netzhammer.ch/ 178.174.29.18


Url with incomplete Content-Type - header - missing charset
http://signaling.netzhammer.ch:443/ 178.174.29.18


Url with incomplete Content-Type - header - missing charset
http://signaling.netzhammer.ch/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 178.174.29.18


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.
Qhttp://signaling.netzhammer.ch:443/ 178.174.29.18
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>.
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 signaling.netzhammer.ch, 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.signaling.netzhammer.ch

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 3 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.dns1.katta.ch (62.12.134.50), dns2.katta.ch (62.12.134.61), dns3.katta.ch (83.150.62.67)
AGood (1 - 3.0):: An average of 0.7 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 3 different Name Servers found: dns1.katta.ch, dns2.katta.ch, dns3.katta.ch, 3 Name Servers included in Delegation: dns1.katta.ch, dns2.katta.ch, dns3.katta.ch, 3 Name Servers included in 1 Zone definitions: dns1.katta.ch, dns2.katta.ch, dns3.katta.ch, 1 Name Servers listed in SOA.Primary: dns1.katta.ch.
AGood: Only one SOA.Primary Name Server found.: dns1.katta.ch.
AGood: SOA.Primary Name Server included in the delegation set.: dns1.katta.ch.
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.
AInfo: Ipv4-Subnet-list: 3 Name Servers, 2 different subnets (first Byte): 62., 83., 2 different subnets (first two Bytes): 62.12., 83.150., 2 different subnets (first three Bytes): 62.12.134., 83.150.62.
AGood: Name Server IPv4-addresses from different subnet found:
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: dns1.katta.ch: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
AGood: All SOA have the same Serial Number
Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries.

4. Content- and Performance-critical Checks

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

QNr.DomainTypeNS used
1
ch
NS
l.root-servers.net (2001:500:9f::42)

Answer: a.nic.ch, b.nic.ch, d.nic.ch, e.nic.ch, f.nic.ch
2
dns1.katta.ch: 62.12.134.50
NS
a.nic.ch (2001:620:0:ff::56)

Answer: dns2.katta.ch
62.12.134.61

Answer: dns3.katta.ch
83.150.62.67


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
signaling.netzhammer.ch



1
0
remote.netzhammer.ch
0

no CAA entry found
1
0
netzhammer.ch
0

no CAA entry found
1
0

0

no CAA entry found
1
0
ch
0

no CAA entry found
1
0

0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
netzhammer.ch
v=spf1 mx a:remote.netzhammer.ch a:smtp1.katta.ch/28 a:smtp2.katta.ch/28 -all
ok
1
0
signaling.netzhammer.ch


1
0
_acme-challenge.remote.netzhammer.ch

Name Error - The domain name does not exist
1
0
_acme-challenge.signaling.netzhammer.ch

Name Error - The domain name does not exist
1
0
_acme-challenge.signaling.netzhammer.ch.netzhammer.ch

Name Error - The domain name does not exist
1
0
_acme-challenge.remote.netzhammer.ch.remote.netzhammer.ch

Name Error - The domain name does not exist
1
0
_acme-challenge.signaling.netzhammer.ch.signaling.netzhammer.ch

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

DomainIPPortDescriptionResultAnswer
signaling.netzhammer.ch
178.174.29.18
21
FTP
open


signaling.netzhammer.ch
178.174.29.18
21
FTP
open


signaling.netzhammer.ch
178.174.29.18
22
SSH
open


signaling.netzhammer.ch
178.174.29.18
22
SSH
open


signaling.netzhammer.ch
178.174.29.18
25
SMTP
open


signaling.netzhammer.ch
178.174.29.18
25
SMTP
open


signaling.netzhammer.ch
178.174.29.18
53
DNS
open


signaling.netzhammer.ch
178.174.29.18
53
DNS
open


signaling.netzhammer.ch
178.174.29.18
110
POP3
open


signaling.netzhammer.ch
178.174.29.18
110
POP3
open

This port ist unencrypted and deprecated. Don't use it.
signaling.netzhammer.ch
178.174.29.18
143
IMAP
open


signaling.netzhammer.ch
178.174.29.18
143
IMAP
open

This port ist unencrypted and deprecated. Don't use it.
signaling.netzhammer.ch
178.174.29.18
465
SMTP (encrypted)
open


signaling.netzhammer.ch
178.174.29.18
465
SMTP (encrypted)
open


signaling.netzhammer.ch
178.174.29.18
587
SMTP (encrypted, submission)
open


signaling.netzhammer.ch
178.174.29.18
587
SMTP (encrypted, submission)
open


signaling.netzhammer.ch
178.174.29.18
993
IMAP (encrypted)
open


signaling.netzhammer.ch
178.174.29.18
993
IMAP (encrypted)
open


signaling.netzhammer.ch
178.174.29.18
995
POP3 (encrypted)
open


signaling.netzhammer.ch
178.174.29.18
995
POP3 (encrypted)
open


signaling.netzhammer.ch
178.174.29.18
1433
MS SQL
open


signaling.netzhammer.ch
178.174.29.18
1433
MS SQL
open


signaling.netzhammer.ch
178.174.29.18
2082
cPanel (http)
open
http://178.174.29.18:2082/
Http-Status: 200

signaling.netzhammer.ch
178.174.29.18
2082
cPanel (http)
open
http://178.174.29.18:2082/
Http-Status: 200

signaling.netzhammer.ch
178.174.29.18
2083
cPanel (https)
open
https://178.174.29.18:2083/
Http-Status: -4
SendFailure - The underlying connection was closed: An unexpected error occurred on a send.

signaling.netzhammer.ch
178.174.29.18
2083
cPanel (https)
open
https://178.174.29.18:2083/
Http-Status: -4
SendFailure - The underlying connection was closed: An unexpected error occurred on a send.

signaling.netzhammer.ch
178.174.29.18
2086
WHM (http)
open
http://178.174.29.18:2086/
Http-Status: 200

signaling.netzhammer.ch
178.174.29.18
2086
WHM (http)
open
http://178.174.29.18:2086/
Http-Status: 200

signaling.netzhammer.ch
178.174.29.18
2087
WHM (https)
open
https://178.174.29.18:2087/
Http-Status: -4
SendFailure - The underlying connection was closed: An unexpected error occurred on a send.

signaling.netzhammer.ch
178.174.29.18
2087
WHM (https)
open
https://178.174.29.18:2087/
Http-Status: -4
SendFailure - The underlying connection was closed: An unexpected error occurred on a send.

signaling.netzhammer.ch
178.174.29.18
2089
cPanel Licensing
open


signaling.netzhammer.ch
178.174.29.18
2089
cPanel Licensing
open


signaling.netzhammer.ch
178.174.29.18
2095
cPanel Webmail (http)
open
http://178.174.29.18:2095/
Http-Status: 200

signaling.netzhammer.ch
178.174.29.18
2095
cPanel Webmail (http)
open
http://178.174.29.18:2095/
Http-Status: 200

signaling.netzhammer.ch
178.174.29.18
2096
cPanel Webmail (https)
open
https://178.174.29.18:2096/
Http-Status: -4
SendFailure - The underlying connection was closed: An unexpected error occurred on a send.

signaling.netzhammer.ch
178.174.29.18
2096
cPanel Webmail (https)
open
https://178.174.29.18:2096/
Http-Status: -4
SendFailure - The underlying connection was closed: An unexpected error occurred on a send.

signaling.netzhammer.ch
178.174.29.18
2222
DirectAdmin (http)
open
http://178.174.29.18:2222/
Http-Status: 200

signaling.netzhammer.ch
178.174.29.18
2222
DirectAdmin (http)
open
http://178.174.29.18:2222/
Http-Status: 200

signaling.netzhammer.ch
178.174.29.18
2222
DirectAdmin (https)
open
https://178.174.29.18:2222/
Http-Status: -4
SendFailure - The underlying connection was closed: An unexpected error occurred on a send.

signaling.netzhammer.ch
178.174.29.18
2222
DirectAdmin (https)
open
https://178.174.29.18:2222/
Http-Status: -4
SendFailure - The underlying connection was closed: An unexpected error occurred on a send.

signaling.netzhammer.ch
178.174.29.18
3306
mySql
open


signaling.netzhammer.ch
178.174.29.18
3306
mySql
open


signaling.netzhammer.ch
178.174.29.18
5224
Plesk Licensing
open


signaling.netzhammer.ch
178.174.29.18
5224
Plesk Licensing
open


signaling.netzhammer.ch
178.174.29.18
5432
PostgreSQL
open


signaling.netzhammer.ch
178.174.29.18
5432
PostgreSQL
open


signaling.netzhammer.ch
178.174.29.18
8080
Ookla Speedtest (http)
open
http://178.174.29.18:8080/
Http-Status: 200

signaling.netzhammer.ch
178.174.29.18
8080
Ookla Speedtest (http)
open
http://178.174.29.18:8080/
Http-Status: 200

signaling.netzhammer.ch
178.174.29.18
8080
Ookla Speedtest (https)
open
https://178.174.29.18:8080/
Http-Status: -4
SendFailure - The underlying connection was closed: An unexpected error occurred on a send.

signaling.netzhammer.ch
178.174.29.18
8080
Ookla Speedtest (https)
open
https://178.174.29.18:8080/
Http-Status: -4
SendFailure - The underlying connection was closed: An unexpected error occurred on a send.

signaling.netzhammer.ch
178.174.29.18
8083
VestaCP http
open
http://178.174.29.18:8083/
Http-Status: 200

signaling.netzhammer.ch
178.174.29.18
8083
VestaCP http
open
http://178.174.29.18:8083/
Http-Status: 200

signaling.netzhammer.ch
178.174.29.18
8083
VestaCP https
open
https://178.174.29.18:8083/
Http-Status: -4
SendFailure - The underlying connection was closed: An unexpected error occurred on a send.

signaling.netzhammer.ch
178.174.29.18
8083
VestaCP https
open
https://178.174.29.18:8083/
Http-Status: -4
SendFailure - The underlying connection was closed: An unexpected error occurred on a send.

signaling.netzhammer.ch
178.174.29.18
8443
Plesk Administration (https)
open
https://178.174.29.18:8443/
Http-Status: -4
SendFailure - The underlying connection was closed: An unexpected error occurred on a send.

signaling.netzhammer.ch
178.174.29.18
8443
Plesk Administration (https)
open
https://178.174.29.18:8443/
Http-Status: -4
SendFailure - The underlying connection was closed: An unexpected error occurred on a send.

signaling.netzhammer.ch
178.174.29.18
8447
Plesk Installer + Updates
open


signaling.netzhammer.ch
178.174.29.18
8447
Plesk Installer + Updates
open


signaling.netzhammer.ch
178.174.29.18
8880
Plesk Administration (http)
open
http://178.174.29.18:8880/
Http-Status: 200

signaling.netzhammer.ch
178.174.29.18
8880
Plesk Administration (http)
open
http://178.174.29.18:8880/
Http-Status: 200

signaling.netzhammer.ch
178.174.29.18
10000
Webmin (http)
open
http://178.174.29.18:10000/
Http-Status: 200

signaling.netzhammer.ch
178.174.29.18
10000
Webmin (http)
open
http://178.174.29.18:10000/
Http-Status: 200

signaling.netzhammer.ch
178.174.29.18
10000
Webmin (https)
open
https://178.174.29.18:10000/
Http-Status: -4
SendFailure - The underlying connection was closed: An unexpected error occurred on a send.

signaling.netzhammer.ch
178.174.29.18
10000
Webmin (https)
open
https://178.174.29.18:10000/
Http-Status: -4
SendFailure - The underlying connection was closed: An unexpected error occurred on a send.



Permalink: https://check-your-website.server-daten.de/?i=a5d6b63a-ced8-4674-bd8e-79484514b195


Last Result: https://check-your-website.server-daten.de/?q=signaling.netzhammer.ch - 2023-03-17 20:16:15


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

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

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


Jürgen Auer • Friedenstr. 37 • 10249 Berlin • +49(0)30 420 200 60 • info@sql-und-xml.de • USt-IdNr.: DE221734518

Errors, ideas, questions? Use the Contact form • A project using Server-Daten - Web Database solutions