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

...

skip EDNS-Check

skip Content-Check

check links

http sent over port 443

Checked:
18.09.2023 14:42:14

Older results

No older results found

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
engine.dipa-sys.de	A	35.242.210.94 Frankfurt/Hesse/Germany (DE) - Google LLC Hostname: 94.210.242.35.bc.googleusercontent.com	yes	1	0
	AAAA		yes
www.engine.dipa-sys.de		Name Error	yes	1	0
*.dipa-sys.de	A	Refused	yes
	AAAA	Refused	yes
	CNAME	Refused	yes
*.engine.dipa-sys.de	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 11019, 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: 30.09.2023, 00:00:00 +, Signature-Inception: 09.09.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: de
de	1 DS RR in the parent zone found


	DS with Algorithm 8, KeyTag 26755, DigestType 2 and Digest 80E1eAmllUMRzLgq3hFMbB1ySnXAOVE3qjl4A1Ql540=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner de., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 01.10.2023, 05:00:00 +, Signature-Inception: 18.09.2023, 04:00:00 +, KeyTag 11019, Signer-Name: (root)


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


	2 DNSKEY RR found


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


	Public Key with Algorithm 8, KeyTag 44886, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner de., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 29.09.2023, 23:42:55 +, Signature-Inception: 15.09.2023, 22:12:55 +, KeyTag 26755, Signer-Name: de


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


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

Zone: dipa-sys.de
dipa-sys.de	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 "tabcds8j9u1achb8icg94barobloip28" between the hashed NSEC3-owner "tabafgtghrkkjltd38rgibf0g3n02vgp" and the hashed NextOwner "tabd5cctcr4576kn1ej1l4ucth3o3jjk". So the parent zone confirmes the not-existence of a DS RR. Bitmap: A, RRSIG Validated: RRSIG-Owner tabafgtghrkkjltd38rgibf0g3n02vgp.de., Algorithm: 8, 2 Labels, original TTL: 7200 sec, Signature-expiration: 01.10.2023, 06:56:29 +, Signature-Inception: 17.09.2023, 05:26:29 +, KeyTag 44886, Signer-Name: de


	DS-Query in the parent zone sends valid NSEC3 RR with the Hash "tjlb7qbojvmlf1s6gdriru7vsms1lg16" as Owner. That's the Hash of "de" with the NextHashedOwnerName "tjlf6jn42vl7a95rc3u0k1aoglkqj53o". So that domain name is the Closest Encloser of "dipa-sys.de". Opt-Out: True. Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner tjlb7qbojvmlf1s6gdriru7vsms1lg16.de., Algorithm: 8, 2 Labels, original TTL: 7200 sec, Signature-expiration: 02.10.2023, 02:36:46 +, Signature-Inception: 18.09.2023, 01:06:46 +, KeyTag 44886, Signer-Name: de


	0 DNSKEY RR found




Zone: engine.dipa-sys.de
engine.dipa-sys.de	0 DS RR in the parent zone found


	0 DNSKEY RR found




Zone: www.engine.dipa-sys.de
www.engine.dipa-sys.de	0 DS RR in the parent zone found

3. Name Servers

Domain	Nameserver	NS-IP
www.engine.dipa-sys.de	• ns-cloud-c1.googledomains.com
engine.dipa-sys.de	• ns-cloud-c1.googledomains.com	216.239.32.108 Mountain View/California/United States (US) - Google LLC	•
	•	2001:4860:4802:32::6c Mountain View/California/United States (US) - Google LLC	•
	• ns-cloud-c2.googledomains.com	216.239.34.108 Mountain View/California/United States (US) - Google LLC	•
	•	2001:4860:4802:34::6c Mountain View/California/United States (US) - Google LLC	•
	• ns-cloud-c3.googledomains.com	216.239.36.108 Mountain View/California/United States (US) - Google LLC	•
	•	2001:4860:4802:36::6c Mountain View/California/United States (US) - Google LLC	•
	• ns-cloud-c4.googledomains.com	216.239.38.108 Mountain View/California/United States (US) - Google LLC	•
	•	2001:4860:4802:38::6c Mountain View/California/United States (US) - Google LLC	•
dipa-sys.de	• docks06.rzone.de / dns-pub-de-fra-fr704.server.lan	217.160.80.133 Karlsruhe/Baden-Wurttemberg/Germany (DE) - 1&1 IONOS SE	•
	•	2001:8d8:fe:53:5747:2a74:d:6 Karlsruhe/Baden-Wurttemberg/Germany (DE) - 1&1 IONOS SE	•
	• shades02.rzone.de / dns-pub-15418-de-ber-rs02.server.lan	185.132.34.129 Madrid/Spain (ES) - DNSAS (eBGP DNS)	•
	•	2607:f1c0:fe:53:185:132:34:129 Madrid/Spain (ES) - Fasthosts Internet Limited	•
de	• a.nic.de / ns-2.de.de8.bind		•
	• f.nic.de / ns-2.de.de1		•
	• l.de.net / ns-1.de.fr1		•
	• n.de.net / s3.cph		•
	• s.de.net / ns-3.de.de9		•
	• z.nic.de / ns-2.de.de2.bind		•

4. SOA-Entries

Domain:	de
Zone-Name:	de
Primary:	f.nic.de
Mail:	dns-operations.denic.de
Serial:	1695040768
Refresh:	7200
Retry:	7200
Expire:	3600000
TTL:	7200
num Entries:	4

Domain:	de
Zone-Name:	de
Primary:	f.nic.de
Mail:	dns-operations.denic.de
Serial:	1695040892
Refresh:	7200
Retry:	7200
Expire:	3600000
TTL:	7200
num Entries:	2

Domain:	dipa-sys.de
Zone-Name:	dipa-sys.de
Primary:	docks06.rzone.de
Mail:	hostmaster.strato-rz.de
Serial:	2020052057
Refresh:	86400
Retry:	7200
Expire:	604800
TTL:	300
num Entries:	4

Domain:	engine.dipa-sys.de
Zone-Name:	engine.dipa-sys.de
Primary:	ns-cloud-c1.googledomains.com
Mail:	cloud-dns-hostmaster.google.com
Serial:	1
Refresh:	21600
Retry:	3600
Expire:	259200
TTL:	300
num Entries:	8

Domain:	www.engine.dipa-sys.de
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
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

show header:

Domainname	Http-Status	redirect	Sec.	G
• http://engine.dipa-sys.de/ 35.242.210.94	-14		10.057	T
Timeout - The operation has timed out

• https://engine.dipa-sys.de/ 35.242.210.94	-4		0.086	W
SendFailure - The underlying connection was closed: An unexpected error occurred on a send.

• http://engine.dipa-sys.de:443/ 35.242.210.94	404	Html is minified: 100.00 %	0.033	Q
Not Found
Visible Content: { "message": "Not Found"}
Connection: close
access-control-allow-origin: *
content-type: application/json; charset=utf-8
transfer-encoding: chunked

• http://engine.dipa-sys.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 35.242.210.94	-14		10.100	T
Timeout - The operation has timed out
Visible Content:

• https://35.242.210.94/ 35.242.210.94	-4		0.057	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
A	name "engine.dipa-sys.de" is subdomain, public suffix is ".de", top-level-domain is ".de", top-level-domain-type is "country-code", Country is Germany, tld-manager is "DENIC eG", num .de-domains preloaded: 9157 (complete: 231048)
A	Good: All ip addresses are public addresses
	Warning: Only one ip address found: engine.dipa-sys.de 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: engine.dipa-sys.de has no ipv6 address.
A	Good: No asked Authoritative Name Server had a timeout
A	DNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
A	Good: 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.
A	Good: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
C	Error - no version with Http-Status 200
H	Fatal error: No https - result with http-status 200, no encryption
M	http://engine.dipa-sys.de:443/ 35.242.210.94	404	Misconfiguration - main pages should never send http status 400 - 499
Q	http://engine.dipa-sys.de:443/ 35.242.210.94	404	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 engine.dipa-sys.de, 1 ip addresses.
B	No _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.engine.dipa-sys.de
	2. Header-Checks
U			No https result with http status 2 or 4 (standard-check) found, no header checked.
	3. DNS- and NameServer - Checks
A	Info:: 13 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers.
A	Info:: 13 Queries complete, 13 with IPv6, 0 with IPv4.
A	Good: 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.
A	Info:: 4 different Name Servers found: ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com, 4 Name Servers included in Delegation: ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com, 4 Name Servers included in 1 Zone definitions: ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com, 1 Name Servers listed in SOA.Primary: ns-cloud-c1.googledomains.com.
A	Good: Only one SOA.Primary Name Server found.: ns-cloud-c1.googledomains.com.
A	Good: SOA.Primary Name Server included in the delegation set.: ns-cloud-c1.googledomains.com.
A	Good: 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: ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com
A	Good: All Name Server Domain Names have a Public Suffix.
A	Good: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
A	Good: All Name Server ip addresses are public.
A	Good: Minimal 2 different name servers (public suffix and public ip address) found: 4 different Name Servers found
A	Good: All name servers have ipv4- and ipv6-addresses.: 4 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.: 4 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: googledomains.com
	Warning: All Name Servers from the same Country / IP location.: 4 Name Servers, 1 Countries: US
A	Info: Ipv4-Subnet-list: 4 Name Servers, 1 different subnets (first Byte): 216., 1 different subnets (first two Bytes): 216.239., 4 different subnets (first three Bytes): 216.239.32., 216.239.34., 216.239.36., 216.239.38.
A	Good: Name Server IPv4-addresses from different subnet found:
A	Info: IPv6-Subnet-list: 4 Name Servers with IPv6, 1 different subnets (first block): 2001:, 1 different subnets (first two blocks): 2001:4860:, 1 different subnets (first three blocks): 2001:4860:4802:, 4 different subnets (first four blocks): 2001:4860:4802:0032:, 2001:4860:4802:0034:, 2001:4860:4802:0036:, 2001:4860:4802:0038:
A	Good: Name Server IPv6 addresses from different subnets found.
A	Good: Nameserver supports TCP connections: 8 good Nameserver
A	Good: Nameserver supports Echo Capitalization: 8 good Nameserver
A	Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 8 good Nameserver
A	Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 8 good Nameserver
	Nameserver doesn't pass all EDNS-Checks: ns-cloud-c1.googledomains.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.
A	Good: 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://engine.dipa-sys.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 35.242.210.94	-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.
A	Info: No img element found, no alt attribute checked
A	Good: 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
A	Duration: 81983 milliseconds, 81.983 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

Issuer				last 7 days	active	num Certs
CN=RapidSSL Global TLS RSA4096 SHA256 2022 CA1, O="DigiCert, Inc.", C=US				0	0	1

CRT-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
8671500057 precert	CN=RapidSSL Global TLS RSA4096 SHA256 2022 CA1, O="DigiCert, Inc.", C=US	2023-02-16 23:00:00	2024-03-03 22:59:59	*.dipa-sys.de, dipa-sys.de 2 entries

11. Html-Content - Entries

No Html-Content entries found. Only checked if https + status 200/401/403/404

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

Small Code update, wait one minute

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com

QNr.	Domain	Type	NS used
1	com	NS	m.root-servers.net (2001:dc3::35)
	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	ns-cloud-c1.googledomains.com	NS	l.gtld-servers.net (2001:500:d937::30)
	Answer: ns5.googledomains.com, ns6.googledomains.com, ns7.googledomains.com, ns8.googledomains.com
	Answer: ns8.googledomains.com 2001:4860:4802:38::a, 216.239.38.10
	Answer: ns7.googledomains.com 2001:4860:4802:36::a, 216.239.36.10
	Answer: ns6.googledomains.com 2001:4860:4802:34::a, 216.239.34.10
	Answer: ns5.googledomains.com 2001:4860:4802:32::a, 216.239.32.10
3	ns-cloud-c2.googledomains.com	NS	l.gtld-servers.net (2001:500:d937::30)
	Answer: ns5.googledomains.com, ns6.googledomains.com, ns7.googledomains.com, ns8.googledomains.com
	Answer: ns8.googledomains.com 2001:4860:4802:38::a, 216.239.38.10
	Answer: ns7.googledomains.com 2001:4860:4802:36::a, 216.239.36.10
	Answer: ns6.googledomains.com 2001:4860:4802:34::a, 216.239.34.10
	Answer: ns5.googledomains.com 2001:4860:4802:32::a, 216.239.32.10
4	ns-cloud-c3.googledomains.com	NS	l.gtld-servers.net (2001:500:d937::30)
	Answer: ns5.googledomains.com, ns6.googledomains.com, ns7.googledomains.com, ns8.googledomains.com
	Answer: ns8.googledomains.com 2001:4860:4802:38::a, 216.239.38.10
	Answer: ns7.googledomains.com 2001:4860:4802:36::a, 216.239.36.10
	Answer: ns6.googledomains.com 2001:4860:4802:34::a, 216.239.34.10
	Answer: ns5.googledomains.com 2001:4860:4802:32::a, 216.239.32.10
5	ns-cloud-c4.googledomains.com	NS	l.gtld-servers.net (2001:500:d937::30)
	Answer: ns5.googledomains.com, ns6.googledomains.com, ns7.googledomains.com, ns8.googledomains.com
	Answer: ns8.googledomains.com 2001:4860:4802:38::a, 216.239.38.10
	Answer: ns7.googledomains.com 2001:4860:4802:36::a, 216.239.36.10
	Answer: ns6.googledomains.com 2001:4860:4802:34::a, 216.239.34.10
	Answer: ns5.googledomains.com 2001:4860:4802:32::a, 216.239.32.10
6	ns-cloud-c1.googledomains.com: 216.239.32.108	A	ns5.googledomains.com (2001:4860:4802:32::a)
7	ns-cloud-c1.googledomains.com: 2001:4860:4802:32::6c	AAAA	ns5.googledomains.com (2001:4860:4802:32::a)
8	ns-cloud-c2.googledomains.com: 216.239.34.108	A	ns5.googledomains.com (2001:4860:4802:32::a)
9	ns-cloud-c2.googledomains.com: 2001:4860:4802:34::6c	AAAA	ns5.googledomains.com (2001:4860:4802:32::a)
10	ns-cloud-c3.googledomains.com: 216.239.36.108	A	ns5.googledomains.com (2001:4860:4802:32::a)
11	ns-cloud-c3.googledomains.com: 2001:4860:4802:36::6c	AAAA	ns5.googledomains.com (2001:4860:4802:32::a)
12	ns-cloud-c4.googledomains.com: 216.239.38.108	A	ns5.googledomains.com (2001:4860:4802:32::a)
13	ns-cloud-c4.googledomains.com: 2001:4860:4802:38::6c	AAAA	ns5.googledomains.com (2001:4860:4802:32::a)

14. CAA - Entries

Domainname	Value	∑ Queries
engine.dipa-sys.de	no CAA entry found	1
dipa-sys.de	no CAA entry found	1
de	no CAA entry found	1

15. TXT - Entries

Domainname	TXT Entry	Status	∑ Queries
dipa-sys.de	firebase=uvvapp-ca8a2	ok	1
dipa-sys.de	v=spf1 include:_spf.firebasemail.com ~all	ok	1
engine.dipa-sys.de		ok	1
_acme-challenge.engine.dipa-sys.de		Name Error - The domain name does not exist	1
_acme-challenge.engine.dipa-sys.de.dipa-sys.de		perhaps wrong	1
_acme-challenge.engine.dipa-sys.de.engine.dipa-sys.de		Name Error - The domain name does not exist	1

16. DomainService - Entries

No DomainServiceEntries entries found

17. Cipher Suites

No results

18. Portchecks

Domain	IP	Port	Description	Result	Answer
engine.dipa-sys.de	35.242.210.94	21	FTP

engine.dipa-sys.de	35.242.210.94	21	FTP
engine.dipa-sys.de	35.242.210.94	22	SSH	open
SSH-2.0-OpenSSH_9.3
engine.dipa-sys.de	35.242.210.94	22	SSH	open	SSH-2.0-OpenSSH_9.3	Bad: SSH without DNS SSHFP Record found
					Possible DNS SSHFP Entries: engine.dipa-sys.de IN SSHFP 4 2 87e2e02cfadacea15070f3354b0daa97a9f9fb2ca20c2795084da1915e114f99
engine.dipa-sys.de	35.242.210.94	25	SMTP

engine.dipa-sys.de	35.242.210.94	25	SMTP
engine.dipa-sys.de	35.242.210.94	53	DNS

engine.dipa-sys.de	35.242.210.94	53	DNS
engine.dipa-sys.de	35.242.210.94	110	POP3

engine.dipa-sys.de	35.242.210.94	110	POP3
engine.dipa-sys.de	35.242.210.94	143	IMAP

engine.dipa-sys.de	35.242.210.94	143	IMAP
engine.dipa-sys.de	35.242.210.94	465	SMTP (encrypted)

engine.dipa-sys.de	35.242.210.94	465	SMTP (encrypted)
engine.dipa-sys.de	35.242.210.94	587	SMTP (encrypted, submission)

engine.dipa-sys.de	35.242.210.94	587	SMTP (encrypted, submission)
engine.dipa-sys.de	35.242.210.94	993	IMAP (encrypted)

engine.dipa-sys.de	35.242.210.94	993	IMAP (encrypted)
engine.dipa-sys.de	35.242.210.94	995	POP3 (encrypted)

engine.dipa-sys.de	35.242.210.94	995	POP3 (encrypted)
engine.dipa-sys.de	35.242.210.94	1433	MS SQL

engine.dipa-sys.de	35.242.210.94	1433	MS SQL
engine.dipa-sys.de	35.242.210.94	2082	cPanel (http)

engine.dipa-sys.de	35.242.210.94	2082	cPanel (http)
engine.dipa-sys.de	35.242.210.94	2083	cPanel (https)

engine.dipa-sys.de	35.242.210.94	2083	cPanel (https)
engine.dipa-sys.de	35.242.210.94	2086	WHM (http)

engine.dipa-sys.de	35.242.210.94	2086	WHM (http)
engine.dipa-sys.de	35.242.210.94	2087	WHM (https)

engine.dipa-sys.de	35.242.210.94	2087	WHM (https)
engine.dipa-sys.de	35.242.210.94	2089	cPanel Licensing

engine.dipa-sys.de	35.242.210.94	2089	cPanel Licensing
engine.dipa-sys.de	35.242.210.94	2095	cPanel Webmail (http)

engine.dipa-sys.de	35.242.210.94	2095	cPanel Webmail (http)
engine.dipa-sys.de	35.242.210.94	2096	cPanel Webmail (https)

engine.dipa-sys.de	35.242.210.94	2096	cPanel Webmail (https)
engine.dipa-sys.de	35.242.210.94	2222	DirectAdmin (http)

engine.dipa-sys.de	35.242.210.94	2222	DirectAdmin (http)
engine.dipa-sys.de	35.242.210.94	2222	DirectAdmin (https)

engine.dipa-sys.de	35.242.210.94	2222	DirectAdmin (https)
engine.dipa-sys.de	35.242.210.94	3306	mySql

engine.dipa-sys.de	35.242.210.94	3306	mySql
engine.dipa-sys.de	35.242.210.94	5224	Plesk Licensing

engine.dipa-sys.de	35.242.210.94	5224	Plesk Licensing
engine.dipa-sys.de	35.242.210.94	5432	PostgreSQL

engine.dipa-sys.de	35.242.210.94	5432	PostgreSQL
engine.dipa-sys.de	35.242.210.94	8080	Ookla Speedtest (http)

engine.dipa-sys.de	35.242.210.94	8080	Ookla Speedtest (http)
engine.dipa-sys.de	35.242.210.94	8080	Ookla Speedtest (https)

engine.dipa-sys.de	35.242.210.94	8080	Ookla Speedtest (https)
engine.dipa-sys.de	35.242.210.94	8083	VestaCP http

engine.dipa-sys.de	35.242.210.94	8083	VestaCP http
engine.dipa-sys.de	35.242.210.94	8083	VestaCP https

engine.dipa-sys.de	35.242.210.94	8083	VestaCP https
engine.dipa-sys.de	35.242.210.94	8443	Plesk Administration (https)

engine.dipa-sys.de	35.242.210.94	8443	Plesk Administration (https)
engine.dipa-sys.de	35.242.210.94	8447	Plesk Installer + Updates

engine.dipa-sys.de	35.242.210.94	8447	Plesk Installer + Updates
engine.dipa-sys.de	35.242.210.94	8880	Plesk Administration (http)

engine.dipa-sys.de	35.242.210.94	8880	Plesk Administration (http)
engine.dipa-sys.de	35.242.210.94	10000	Webmin (http)

engine.dipa-sys.de	35.242.210.94	10000	Webmin (http)
engine.dipa-sys.de	35.242.210.94	10000	Webmin (https)

engine.dipa-sys.de	35.242.210.94	10000	Webmin (https)

Permalink: https://check-your-website.server-daten.de/?i=917b0c81-d9d1-4e54-9927-120866ff5667

Last Result: https://check-your-website.server-daten.de/?q=engine.dipa-sys.de - 2023-09-18 14:42:14

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

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

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

QR-Code of this page - https://check-your-website.server-daten.de/?d=engine.dipa-sys.de