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


 

 

H

 

Http as Destination - no encryption

 

Checked:
09.07.2024 15:50:31

 

Older results

No older results found

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
secmail.inetwork.dk
A
83.89.248.163
Værløse/Capital Region/Denmark (DK) - TDC Holding A/S
Hostname: 0x5359f8a3.static.cust.fastspeed.dk
yes
1
0

AAAA

yes


www.secmail.inetwork.dk

Name Error
yes
1
0
*.inetwork.dk
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes


*.secmail.inetwork.dk
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes


 

2. DNSSEC

Zone (*)DNSSEC - Informations


Zone: (root)

(root)
1 DS RR published






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






Status: Valid because published






3 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 5613, Flags 256






Public Key with Algorithm 8, KeyTag 20038, Flags 256






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






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 22.07.2024, 00:00:00 +, Signature-Inception: 01.07.2024, 00:00:00 +, KeyTag 20326, Signer-Name: (root)






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






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



Zone: dk

dk
1 DS RR in the parent zone found






DS with Algorithm 13, KeyTag 2181, DigestType 2 and Digest nnB7jJqK5Ik/bd9UWVf5gJ/oukdHv3BSY2AUZqoQBR0=






1 RRSIG RR to validate DS RR found






RRSIG-Owner dk., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 22.07.2024, 05:00:00 +, Signature-Inception: 09.07.2024, 04:00:00 +, KeyTag 20038, Signer-Name: (root)






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






2 DNSKEY RR found






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






Public Key with Algorithm 13, KeyTag 55245, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner dk., Algorithm: 13, 1 Labels, original TTL: 86400 sec, Signature-expiration: 03.08.2024, 20:39:02 +, Signature-Inception: 06.07.2024, 19:09:02 +, KeyTag 2181, Signer-Name: dk






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






Status: Valid Chain of trust. Parent-DS with Algorithm 13, KeyTag 2181, DigestType 2 and Digest "nnB7jJqK5Ik/bd9UWVf5gJ/oukdHv3BSY2AUZqoQBR0=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone



Zone: inetwork.dk

inetwork.dk
1 DS RR in the parent zone found






DS with Algorithm 13, KeyTag 9988, DigestType 2 and Digest YXBL4+Lsj4VhlypEpwQK80YkWfI4lRF+Q5YZ14iLzVg=






1 RRSIG RR to validate DS RR found






RRSIG-Owner inetwork.dk., Algorithm: 13, 2 Labels, original TTL: 7200 sec, Signature-expiration: 02.08.2024, 20:38:39 +, Signature-Inception: 05.07.2024, 19:08:39 +, KeyTag 55245, Signer-Name: dk






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






2 DNSKEY RR found






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






Public Key with Algorithm 13, KeyTag 11527, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner inetwork.dk., Algorithm: 13, 2 Labels, original TTL: 900 sec, Signature-expiration: 18.07.2024, 00:00:00 +, Signature-Inception: 27.06.2024, 00:00:00 +, KeyTag 9988, Signer-Name: inetwork.dk






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






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



Zone: secmail.inetwork.dk

secmail.inetwork.dk
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 "k50uqd9orgehu5m5uh25cd6uourc4bu7" between the hashed NSEC3-owner "k50uqd9orgehu5m5uh25cd6uourc4bu7" and the hashed NextOwner "k50uqd9orgehu5m5uh25cd6uourc4bu8". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: A, RRSIG Validated: RRSIG-Owner k50uqd9orgehu5m5uh25cd6uourc4bu7.inetwork.dk., Algorithm: 13, 3 Labels, original TTL: 900 sec, Signature-expiration: 18.07.2024, 00:00:00 +, Signature-Inception: 27.06.2024, 00:00:00 +, KeyTag 11527, Signer-Name: inetwork.dk






0 DNSKEY RR found












RRSIG Type 1 validates the A - Result: 83.89.248.163
Validated: RRSIG-Owner secmail.inetwork.dk., Algorithm: 13, 3 Labels, original TTL: 3600 sec, Signature-expiration: 18.07.2024, 00:00:00 +, Signature-Inception: 27.06.2024, 00:00:00 +, KeyTag 11527, Signer-Name: inetwork.dk






CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "k50uqd9orgehu5m5uh25cd6uourc4bu7" equal the hashed NSEC3-owner "k50uqd9orgehu5m5uh25cd6uourc4bu7" and the hashed NextOwner "k50uqd9orgehu5m5uh25cd6uourc4bu8". 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, RRSIG Validated: RRSIG-Owner k50uqd9orgehu5m5uh25cd6uourc4bu7.inetwork.dk., Algorithm: 13, 3 Labels, original TTL: 900 sec, Signature-expiration: 18.07.2024, 00:00:00 +, Signature-Inception: 27.06.2024, 00:00:00 +, KeyTag 11527, Signer-Name: inetwork.dk






Status: Good. NoData-Proof required and found.






TXT-Query sends a valid NSEC3 RR as result with the hashed query name "k50uqd9orgehu5m5uh25cd6uourc4bu7" equal the hashed NSEC3-owner "k50uqd9orgehu5m5uh25cd6uourc4bu7" and the hashed NextOwner "k50uqd9orgehu5m5uh25cd6uourc4bu8". 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, RRSIG Validated: RRSIG-Owner k50uqd9orgehu5m5uh25cd6uourc4bu7.inetwork.dk., Algorithm: 13, 3 Labels, original TTL: 900 sec, Signature-expiration: 18.07.2024, 00:00:00 +, Signature-Inception: 27.06.2024, 00:00:00 +, KeyTag 11527, Signer-Name: inetwork.dk






Status: Good. NoData-Proof required and found.






AAAA-Query sends a valid NSEC3 RR as result with the hashed query name "k50uqd9orgehu5m5uh25cd6uourc4bu7" equal the hashed NSEC3-owner "k50uqd9orgehu5m5uh25cd6uourc4bu7" and the hashed NextOwner "k50uqd9orgehu5m5uh25cd6uourc4bu8". So the zone confirmes the not-existence of that AAAA RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: A, RRSIG Validated: RRSIG-Owner k50uqd9orgehu5m5uh25cd6uourc4bu7.inetwork.dk., Algorithm: 13, 3 Labels, original TTL: 900 sec, Signature-expiration: 18.07.2024, 00:00:00 +, Signature-Inception: 27.06.2024, 00:00:00 +, KeyTag 11527, Signer-Name: inetwork.dk






Status: Good. NoData-Proof required and found.






TLSA-Query (_443._tcp.secmail.inetwork.dk) sends a valid NSEC3 RR as result with the hashed owner name "k50uqd9orgehu5m5uh25cd6uourc4bu7" (unhashed: secmail.inetwork.dk). So that's the Closest Encloser of the query name.
Bitmap: A, RRSIG Validated: RRSIG-Owner k50uqd9orgehu5m5uh25cd6uourc4bu7.inetwork.dk., Algorithm: 13, 3 Labels, original TTL: 900 sec, Signature-expiration: 18.07.2024, 00:00:00 +, Signature-Inception: 27.06.2024, 00:00:00 +, KeyTag 11527, Signer-Name: inetwork.dk






Status: Good. NXDomain-Proof required and found.






TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "n97oece54f15jgb6gsv2lgm6vlh2kibb" (unhashed: _tcp.secmail.inetwork.dk) with the owner "n97oece54f15jgb6gsv2lgm6vlh2kiba" and the NextOwner "n97oece54f15jgb6gsv2lgm6vlh2kibc". So that NSEC3 confirms the not-existence of the Next Closer Name.
Bitmap: No Bitmap? Validated: RRSIG-Owner n97oece54f15jgb6gsv2lgm6vlh2kiba.inetwork.dk., Algorithm: 13, 3 Labels, original TTL: 900 sec, Signature-expiration: 18.07.2024, 00:00:00 +, Signature-Inception: 27.06.2024, 00:00:00 +, KeyTag 11527, Signer-Name: inetwork.dk






Status: Good. NXDomain-Proof required and found.






TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Wildcard expansion of the ClosestEncloser "mt1nkqtr814f0h9gn5nbrd5u5ton48fd" (unhashed: *.secmail.inetwork.dk) with the owner "mt1nkqtr814f0h9gn5nbrd5u5ton48fc" and the NextOwner "mt1nkqtr814f0h9gn5nbrd5u5ton48fe". So that NSEC3 confirms the not-existence of the Wildcard expansion.
Bitmap: No Bitmap? Validated: RRSIG-Owner mt1nkqtr814f0h9gn5nbrd5u5ton48fc.inetwork.dk., Algorithm: 13, 3 Labels, original TTL: 900 sec, Signature-expiration: 18.07.2024, 00:00:00 +, Signature-Inception: 27.06.2024, 00:00:00 +, KeyTag 11527, Signer-Name: inetwork.dk






Status: Good. NXDomain-Proof required and found.






CAA-Query sends a valid NSEC3 RR as result with the hashed query name "k50uqd9orgehu5m5uh25cd6uourc4bu7" equal the hashed NSEC3-owner "k50uqd9orgehu5m5uh25cd6uourc4bu7" and the hashed NextOwner "k50uqd9orgehu5m5uh25cd6uourc4bu8". 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, RRSIG Validated: RRSIG-Owner k50uqd9orgehu5m5uh25cd6uourc4bu7.inetwork.dk., Algorithm: 13, 3 Labels, original TTL: 900 sec, Signature-expiration: 18.07.2024, 00:00:00 +, Signature-Inception: 27.06.2024, 00:00:00 +, KeyTag 11527, Signer-Name: inetwork.dk






Status: Good. NoData-Proof required and found.



Zone: www.secmail.inetwork.dk

www.secmail.inetwork.dk
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 "0e1sroo9ibhv42uqidka4mg3bdfm3bpc" between the hashed NSEC3-owner "0e1sroo9ibhv42uqidka4mg3bdfm3bpb" and the hashed NextOwner "0e1sroo9ibhv42uqidka4mg3bdfm3bpd". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: No Bitmap? Validated: RRSIG-Owner 0e1sroo9ibhv42uqidka4mg3bdfm3bpb.inetwork.dk., Algorithm: 13, 3 Labels, original TTL: 900 sec, Signature-expiration: 18.07.2024, 00:00:00 +, Signature-Inception: 27.06.2024, 00:00:00 +, KeyTag 11527, Signer-Name: inetwork.dk






DS-Query in the parent zone sends valid NSEC3 RR with the Hash "k50uqd9orgehu5m5uh25cd6uourc4bu7" as Owner. That's the Hash of "secmail.inetwork.dk" with the NextHashedOwnerName "k50uqd9orgehu5m5uh25cd6uourc4bu8". So that domain name is the Closest Encloser of "www.secmail.inetwork.dk". Opt-Out: False.
Bitmap: A, RRSIG Validated: RRSIG-Owner k50uqd9orgehu5m5uh25cd6uourc4bu7.inetwork.dk., Algorithm: 13, 3 Labels, original TTL: 900 sec, Signature-expiration: 18.07.2024, 00:00:00 +, Signature-Inception: 27.06.2024, 00:00:00 +, KeyTag 11527, Signer-Name: inetwork.dk






The ClosestEncloser says, that "*.secmail.inetwork.dk" with the Hash "mt1nkqtr814f0h9gn5nbrd5u5ton48fd" is a possible Wildcard of the DS Query Name. But the DS-Query in the parent zone sends a valid NSEC3 RR With the owner "mt1nkqtr814f0h9gn5nbrd5u5ton48fc" and the Next Owner "mt1nkqtr814f0h9gn5nbrd5u5ton48fe", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: False.
Bitmap: No Bitmap? Validated: RRSIG-Owner mt1nkqtr814f0h9gn5nbrd5u5ton48fc.inetwork.dk., Algorithm: 13, 3 Labels, original TTL: 900 sec, Signature-expiration: 18.07.2024, 00:00:00 +, Signature-Inception: 27.06.2024, 00:00:00 +, KeyTag 11527, Signer-Name: inetwork.dk

 

3. Name Servers

DomainNameserverNS-IP
www.secmail.inetwork.dk
  ns01.one.com

secmail.inetwork.dk
  ns01.one.com / ns1.cst.dnspod1-fra1.g1i.one
195.206.121.10
Copenhagen/Capital Region/Denmark (DK) - One.com A/S


 
2001:67c:28cc::10
Copenhagen/Capital Region/Denmark (DK) - One.com A/S

inetwork.dk
  ns01.one.com / ns3.cst.dnspod1-fra1.g1i.one
195.206.121.10
Copenhagen/Capital Region/Denmark (DK) - One.com A/S


 
2001:67c:28cc::10
Copenhagen/Capital Region/Denmark (DK) - One.com A/S


  ns02.one.com
185.10.11.10
Copenhagen/Capital Region/Denmark (DK) - One.com A/S


 
2001:67c:3c0::10
Copenhagen/Capital Region/Denmark (DK) - One.com A/S

dk
  b.nic.dk


  c.nic.dk / FRA1


  h.nic.dk


  l.nic.dk / nic-l2.prod.dkhm.dk


  p.nic.dk / 3.ams.pch


  s.nic.dk / ops-nsext01-p.sidn.nl

 

4. SOA-Entries


Domain:dk
Zone-Name:dk
Primary:b.nic.dk
Mail:tech.dk-hostmaster.dk
Serial:1720532881
Refresh:600
Retry:300
Expire:1814400
TTL:300
num Entries:6


Domain:inetwork.dk
Zone-Name:inetwork.dk
Primary:ns01.one.com
Mail:hostmaster.one.com
Serial:2024070916
Refresh:14400
Retry:3600
Expire:1209600
TTL:900
num Entries:4


Domain:secmail.inetwork.dk
Zone-Name:inetwork.dk
Primary:ns01.one.com
Mail:hostmaster.one.com
Serial:2024070916
Refresh:14400
Retry:3600
Expire:1209600
TTL:900
num Entries:2


Domain:www.secmail.inetwork.dk
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


5. Screenshots

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

 

 

6. Url-Checks


:

:
DomainnameHttp-StatusredirectSec.G
• http://secmail.inetwork.dk/
83.89.248.163 No Compression used - 324 / 544 - 59.56 % possible
200

Html is minified: 236.52 %
0.077
H
Server: nginx
Date: Tue, 09 Jul 2024 13:51:31 GMT
Connection: close
ETag: "668d32ee-220"
Cache-Control: no-cache
Accept-Ranges: bytes
Content-Type: text/html
Content-Length: 544
Last-Modified: Tue, 09 Jul 2024 12:54:06 GMT

• https://secmail.inetwork.dk/
83.89.248.163
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
200


Other inline scripts (∑/total): 0/0
44.897
A

• http://secmail.inetwork.dk/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
83.89.248.163
Inline-JavaScript (∑/total): 1/2231 Inline-CSS (∑/total): 1/161
404

Html is minified: 125.83 %
Other inline scripts (∑/total): 1/2231
0.077
A
Not Found
Visible Content:
Server: nginx
Date: Tue, 09 Jul 2024 13:52:16 GMT
Transfer-Encoding: chunked
Connection: close
Vary: Accept-Encoding
ETag: W/"64c75739-2ea3"
Content-Type: text/html
Content-Encoding: gzip

• https://83.89.248.163/
83.89.248.163
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
200


Other inline scripts (∑/total): 0/0
44.483
A

 

7. Comments


1. General Results, most used to calculate the result

Aname "secmail.inetwork.dk" is subdomain, public suffix is ".dk", top-level-domain is ".dk", top-level-domain-type is "country-code", Country is Denmark, tld-manager is "Dansk Internet Forum", num .dk-domains preloaded: 892 (complete: 245733)
AGood: All ip addresses are public addresses
Warning: Only one ip address found: secmail.inetwork.dk 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: secmail.inetwork.dk 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: one preferred version: non-www is preferred
AGood: No cookie sent via http.
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
http://secmail.inetwork.dk/ 83.89.248.163


Url with incomplete Content-Type - header - missing charset
http://secmail.inetwork.dk/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 83.89.248.163


Url with incomplete Content-Type - header - missing charset
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.
Nsecmail.inetwork.dk:465


Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Nsecmail.inetwork.dk:587


Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
Nsecmail.inetwork.dk:993


Error - Certificate isn't trusted, RemoteCertificateNameMismatch, RemoteCertificateChainErrors
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 secmail.inetwork.dk, 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.secmail.inetwork.dk

2. Header-Checks

Fsecmail.inetwork.dk 83.89.248.163
Content-Security-Policy
Critical: Missing Header:
Fsecmail.inetwork.dk 83.89.248.163
X-Content-Type-Options
Critical: Missing Header:
Fsecmail.inetwork.dk 83.89.248.163
Referrer-Policy
Critical: Missing Header:
Fsecmail.inetwork.dk 83.89.248.163
Permissions-Policy
Critical: Missing Header:
Bsecmail.inetwork.dk 83.89.248.163
Cross-Origin-Embedder-Policy
Info: Missing Header
Bsecmail.inetwork.dk 83.89.248.163
Cross-Origin-Opener-Policy
Info: Missing Header
Bsecmail.inetwork.dk 83.89.248.163
Cross-Origin-Resource-Policy
Info: Missing Header

3. DNS- and NameServer - Checks

AInfo:: 9 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
AInfo:: 9 Queries complete, 9 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
Ok (4 - 8):: An average of 4.5 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 2 different Name Servers found: ns01.one.com, ns02.one.com, 2 Name Servers included in Delegation: ns01.one.com, ns02.one.com, 2 Name Servers included in 1 Zone definitions: ns01.one.com, ns02.one.com, 1 Name Servers listed in SOA.Primary: ns01.one.com.
AGood: Only one SOA.Primary Name Server found.: ns01.one.com.
AGood: SOA.Primary Name Server included in the delegation set.: ns01.one.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: ns01.one.com, ns02.one.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
AGood: All name servers have ipv4- and ipv6-addresses.: 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: one.com
Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: DK
AInfo: Ipv4-Subnet-list: 2 Name Servers, 2 different subnets (first Byte): 185., 195., 2 different subnets (first two Bytes): 185.10., 195.206., 2 different subnets (first three Bytes): 185.10.11., 195.206.121.
AExcellent: Every Name Server IPv4-address starts with an unique Byte.
AInfo: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2001:, 1 different subnets (first two blocks): 2001:067c:, 2 different subnets (first three blocks): 2001:067c:03c0:, 2001:067c:28cc:, 2 different subnets (first four blocks): 2001:067c:03c0:0000:, 2001:067c:28cc:0000:
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 2 good Nameserver
AGood: Nameserver supports Echo Capitalization: 2 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 2 good Nameserver
Nameserver doesn't pass all EDNS-Checks: ns01.one.com: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
Nameserver doesn't pass all EDNS-Checks: ns01.one.com / 195.206.121.10: OP100: ok. FLAGS: ok. V1: ok. V1OP100: fatal timeout. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (ns1.cst.dnspod1-fra1.g1i.one). COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns01.one.com / 195.206.121.10: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: fatal timeout. V1DNSSEC: ok. NSID: ok (ns3.cst.dnspod1-fra1.g1i.one). COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns01.one.com / 2001:67c:28cc::10: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: fatal timeout. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns01.one.com / 2001:67c:28cc::10: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (ns1.cst.dnspod1-fra1.g1i.one). COOKIE: fatal timeout. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns02.one.com / 185.10.11.10: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: fatal timeout. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns02.one.com / 2001:67c:3c0::10: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: fatal timeout. COOKIE: ok. CLIENTSUBNET: ok.
AGood: All SOA have the same Serial Number
Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries.

4. Content- and Performance-critical Checks

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

Warning: Https connections (Standard Port 443) found without support of the http/2 protocol via ALPN. Http/2 is the new Http-Version (old: http 1.1) with some important new features. Update your server software so http/2 is available. Only one TCP-connection per Server (that's a performance boost), Header-Compression and Server Pushs are available. Domain Sharding and Inline-CSS/Javascript shouldn't used with http/2.
https://83.89.248.163/ 83.89.248.163
200

Warning: Https connections (Standard Port 443) found without support of the http/2 protocol via ALPN. Http/2 is the new Http-Version (old: http 1.1) with some important new features. Update your server software so http/2 is available. Only one TCP-connection per Server (that's a performance boost), Header-Compression and Server Pushs are available. Domain Sharding and Inline-CSS/Javascript shouldn't used with http/2.
Warning: Images with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 1 image files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 0 with Cache-Control max-age too short (minimum 7 days), 0 with Cache-Control long enough, 1 complete.
AGood: All checked attribute values are enclosed in quotation marks (" or ').
Wrong: img-elements without alt-attribute or empty alt-attribute found. The alt-attribute ("alternative") is required and should describe the img. So Screenreader and search engines are able to use these informations.: 1 img-elements without alt-attribute, 0 img-elements with empty alt-attribute found.
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: 336250 milliseconds, 336.250 seconds

 

8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
secmail.inetwork.dk
83.89.248.163
443
ok
Tls12
ECDH Ephermal
256
Aes256
256
Sha384
not supported
ok
secmail.inetwork.dk
83.89.248.163
443
ok
Tls12

ECDH Ephermal
256
Aes256
256
Sha384
not supported
ok
no http/2 via ALPN 
SNI required
Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
no http/2 via ALPN
SNI required
Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
Chain - incomplete

1CN=tactive-he-bcdwdqdnmgc.dynamic-m.com, O=Cisco Systems Inc., L=San Jose, C=US, ST=California


2CN=HydrantID Server CA O1, OU=HydrantID Trusted Certificate Service, O=IdenTrust, C=US


83.89.248.163
83.89.248.163
443
ok
Tls12
ECDH Ephermal
256
Aes256
256
Sha384
not supported
ok

83.89.248.163
83.89.248.163
443
ok
Tls12

ECDH Ephermal
256
Aes256
256
Sha384
not supported
ok
no http/2 via ALPN 
Cert sent without SNI
Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
no http/2 via ALPN
Cert sent without SNI
Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
Chain - incomplete

1CN=tactive-he-bcdwdqdnmgc.dynamic-m.com, O=Cisco Systems Inc., L=San Jose, C=US, ST=California


2CN=HydrantID Server CA O1, OU=HydrantID Trusted Certificate Service, O=IdenTrust, C=US


secmail.inetwork.dk
83.89.248.163
465
Certificate/chain invalid and wrong name
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok

secmail.inetwork.dk
83.89.248.163
465
Certificate/chain invalid and wrong name
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
not supported
ok
 
Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2

Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
Self signed certificate

1CN=synology.com, OU=FTP Team, O=Synology Inc., L=Taipei, C=TW, emailAddress=product@synology.com


secmail.inetwork.dk
83.89.248.163
587
Certificate/chain invalid and wrong name
Tls12
ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok

secmail.inetwork.dk
83.89.248.163
587
Certificate/chain invalid and wrong name
Tls12

ECDH Ephermal
255
Aes256
256
Sha384
error checking OCSP stapling
ok
 
Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2

Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2


secmail.inetwork.dk
83.89.248.163
993
Certificate/chain invalid and wrong name
Tls12
ECDH Ephermal
255
Aes128
128
Sha256
not supported
ok

secmail.inetwork.dk
83.89.248.163
993
Certificate/chain invalid and wrong name
Tls12

ECDH Ephermal
255
Aes128
128
Sha256
not supported
ok
 
Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2

Tls.1.2
no Tls.1.1
no Tls.1.0
no Ssl3
no Ssl2
Self signed certificate

1CN=synology.com, OU=FTP Team, O=Synology Inc., L=Taipei, C=TW, emailAddress=product@synology.com

 

9. Certificates

1.
1.
E=product@synology.com, CN=synology.com, OU=FTP Team, O=Synology Inc., L=Taipei, S=Taiwan, C=TW
14.10.2013
01.07.2033
expires in 3060 days
product@synology.com - 1 entry
1.
1.
E=product@synology.com, CN=synology.com, OU=FTP Team, O=Synology Inc., L=Taipei, S=Taiwan, C=TW
14.10.2013

01.07.2033
expires in 3060 days


product@synology.com - 1 entry

KeyalgorithmRSA encryption ( bit)
Signatur:SHA-1 with RSA Encryption
Serial Number:1381743116055E
Thumbprint:980298AF6184B88B4904B4C64D40EE98F3DF6B83
SHA256 / Certificate:crGSw7I/2JkyGsoyoiqqUhAZujJCrinJw5hVEeI6bQ4=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):f470a3149f3ded3e85d86b15eec4663474318224709eaedcd0ea8349622ffc66
SHA256 hex / Subject Public Key Information (SPKI):f470a3149f3ded3e85d86b15eec4663474318224709eaedcd0ea8349622ffc66 (is buggy, ignore the result)
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:


RevocationStatusUnknown: The revocation function was unable to check revocation for the certificate.
OfflineRevocation: The revocation function was unable to check revocation because the revocation server was offline.


 

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. 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: ns01.one.com, ns02.one.com

 

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

Answer: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net
2
ns01.one.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: auth.g1-dns.com, auth.g1-dns.one

Answer: auth.g1-dns.com
195.206.121.11, 2001:67c:28cc::11
3
ns02.one.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: auth.g1-dns.com, auth.g1-dns.one

Answer: auth.g1-dns.com
195.206.121.11, 2001:67c:28cc::11
4
one
NS
d.root-servers.net (2001:500:2d::d)

Answer: a.nic.one, b.nic.one, c.nic.one, x.nic.one, y.nic.one, z.nic.one
5
auth.g1-dns.one: 185.10.11.11, 2001:67c:3c0::11
NS
a.nic.one (2001:dcd:1::9)
6
ns01.one.com: 195.206.121.10
A
auth.g1-dns.com (2001:67c:28cc::11)
7
ns01.one.com: 2001:67c:28cc::10
AAAA
auth.g1-dns.com (2001:67c:28cc::11)
8
ns02.one.com: 185.10.11.10
A
auth.g1-dns.com (2001:67c:28cc::11)
9
ns02.one.com: 2001:67c:3c0::10
AAAA
auth.g1-dns.com (2001:67c:28cc::11)

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
secmail.inetwork.dk
0

no CAA entry found
1
0
inetwork.dk
0

no CAA entry found
1
0
dk
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
inetwork.dk
v=spf1 include:_spf.centerasecurity.dk include:_custspf.one.com -all
ok
1
0
secmail.inetwork.dk

ok
1
0
_acme-challenge.secmail.inetwork.dk

Name Error - The domain name does not exist
1
0
_acme-challenge.secmail.inetwork.dk.inetwork.dk

Name Error - The domain name does not exist
1
0
_acme-challenge.secmail.inetwork.dk.secmail.inetwork.dk

Name Error - The domain name does not exist
1
0

 

16. DomainService - Entries

No DomainServiceEntries entries found

 

 

17. Cipher Suites

Summary
DomainIPPortnum CipherstimeStd.ProtocolForward Secrecy
secmail.inetwork.dk
83.89.248.163
443
2 Ciphers32.20 sec
0 without, 2 FS
100.00 %
secmail.inetwork.dk
83.89.248.163
465
2 Ciphers34.94 secSMTP (encrypted)
0 without, 2 FS
100.00 %
secmail.inetwork.dk
83.89.248.163
587
2 Ciphers56.54 secSMTP (encrypted, submission)
0 without, 2 FS
100.00 %
secmail.inetwork.dk
83.89.248.163
993
2 Ciphers32.11 secIMAP (encrypted)
0 without, 2 FS
100.00 %
Complete

4
8 Ciphers
2.00 Ciphers/Check
155.79 sec38.95 sec/Check
0 without, 8 FS
100.00 %

Details
DomainIPPortCipher (OpenSsl / IANA)
secmail.inetwork.dk
83.89.248.163
443
ECDHE-RSA-AES256-GCM-SHA384
(Secure)
TLSv1.2
0xC0,0x30
FS
2 Ciphers, 32.20 sec
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384

ECDH
RSA
AESGCM(256)
AEAD




ECDHE-RSA-AES128-GCM-SHA256
(Secure)
TLSv1.2
0xC0,0x2F
FS

TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256

ECDH
RSA
AESGCM(128)
AEAD



465
ECDHE-RSA-AES256-GCM-SHA384
(Secure)
TLSv1.2
0xC0,0x30
FS
2 Ciphers, 34.94 sec
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384

ECDH
RSA
AESGCM(256)
AEAD




ECDHE-RSA-AES128-GCM-SHA256
(Secure)
TLSv1.2
0xC0,0x2F
FS

TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256

ECDH
RSA
AESGCM(128)
AEAD



587
ECDHE-RSA-AES256-GCM-SHA384
(Secure)
TLSv1.2
0xC0,0x30
FS
2 Ciphers, 56.54 sec
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384

ECDH
RSA
AESGCM(256)
AEAD




ECDHE-RSA-AES128-GCM-SHA256
(Secure)
TLSv1.2
0xC0,0x2F
FS

TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256

ECDH
RSA
AESGCM(128)
AEAD



993
ECDHE-RSA-AES256-GCM-SHA384
(Secure)
TLSv1.2
0xC0,0x30
FS
2 Ciphers, 32.11 sec
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384

ECDH
RSA
AESGCM(256)
AEAD




ECDHE-RSA-AES128-GCM-SHA256
(Secure)
TLSv1.2
0xC0,0x2F
FS

TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256

ECDH
RSA
AESGCM(128)
AEAD

 

18. Portchecks

DomainIPPortDescriptionResultAnswer
secmail.inetwork.dk
83.89.248.163
21
FTP



secmail.inetwork.dk
83.89.248.163
21
FTP



secmail.inetwork.dk
83.89.248.163
22
SSH



secmail.inetwork.dk
83.89.248.163
22
SSH



secmail.inetwork.dk
83.89.248.163
25
SMTP



secmail.inetwork.dk
83.89.248.163
25
SMTP



secmail.inetwork.dk
83.89.248.163
53
DNS



secmail.inetwork.dk
83.89.248.163
53
DNS



secmail.inetwork.dk
83.89.248.163
110
POP3



secmail.inetwork.dk
83.89.248.163
110
POP3



secmail.inetwork.dk
83.89.248.163
143
IMAP



secmail.inetwork.dk
83.89.248.163
143
IMAP



secmail.inetwork.dk
83.89.248.163
465
SMTP (encrypted)
open
220 secmail.inetwork.dk ESMTP Postfix
Mail certificate is invalid
secmail.inetwork.dk
83.89.248.163
465
SMTP (encrypted)
open
220 secmail.inetwork.dk ESMTP Postfix
Mail certificate is invalid
secmail.inetwork.dk
83.89.248.163
587
SMTP (encrypted, submission)
open
220 secmail.inetwork.dk ESMTP Postfix

 

Answer EHLO: 250-secmail.inetwork.dk 250-PIPELINING 250-SIZE 10485760 250-ETRN 250-STARTTLS 250-ENHANCEDSTATUSCODES 250-8BITMIME 250-DSN 250-SMTPUTF8 250 CHUNKING

 

Answer AUTH LOGIN: (no AUTH option found)
Mail certificate is invalid
secmail.inetwork.dk
83.89.248.163
587
SMTP (encrypted, submission)
open
220 secmail.inetwork.dk ESMTP Postfix
Mail certificate is invalid

Answer EHLO: 250-secmail.inetwork.dk 250-PIPELINING 250-SIZE 10485760 250-ETRN 250-STARTTLS 250-ENHANCEDSTATUSCODES 250-8BITMIME 250-DSN 250-SMTPUTF8 250 CHUNKING Good: STARTTLS found


Excellent: No unencrypted login possible
secmail.inetwork.dk
83.89.248.163
993
IMAP (encrypted)
open
* OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE LITERAL+ UTF8=ACCEPT AUTH=PLAIN AUTH=LOGIN AUTH=SYNOAUTH] Dovecot ready.
Mail certificate is invalid
secmail.inetwork.dk
83.89.248.163
993
IMAP (encrypted)
open
* OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE LITERAL+ UTF8=ACCEPT AUTH=PLAIN AUTH=LOGIN AUTH=SYNOAUTH] Dovecot ready.
Mail certificate is invalid
secmail.inetwork.dk
83.89.248.163
995
POP3 (encrypted)



secmail.inetwork.dk
83.89.248.163
995
POP3 (encrypted)



secmail.inetwork.dk
83.89.248.163
1433
MS SQL



secmail.inetwork.dk
83.89.248.163
1433
MS SQL



secmail.inetwork.dk
83.89.248.163
2082
cPanel (http)



secmail.inetwork.dk
83.89.248.163
2082
cPanel (http)



secmail.inetwork.dk
83.89.248.163
2083
cPanel (https)



secmail.inetwork.dk
83.89.248.163
2083
cPanel (https)



secmail.inetwork.dk
83.89.248.163
2086
WHM (http)



secmail.inetwork.dk
83.89.248.163
2086
WHM (http)



secmail.inetwork.dk
83.89.248.163
2087
WHM (https)



secmail.inetwork.dk
83.89.248.163
2087
WHM (https)



secmail.inetwork.dk
83.89.248.163
2089
cPanel Licensing



secmail.inetwork.dk
83.89.248.163
2089
cPanel Licensing



secmail.inetwork.dk
83.89.248.163
2095
cPanel Webmail (http)



secmail.inetwork.dk
83.89.248.163
2095
cPanel Webmail (http)



secmail.inetwork.dk
83.89.248.163
2096
cPanel Webmail (https)



secmail.inetwork.dk
83.89.248.163
2096
cPanel Webmail (https)



secmail.inetwork.dk
83.89.248.163
2222
DirectAdmin (http)



secmail.inetwork.dk
83.89.248.163
2222
DirectAdmin (http)



secmail.inetwork.dk
83.89.248.163
2222
DirectAdmin (https)



secmail.inetwork.dk
83.89.248.163
2222
DirectAdmin (https)



secmail.inetwork.dk
83.89.248.163
3306
mySql



secmail.inetwork.dk
83.89.248.163
3306
mySql



secmail.inetwork.dk
83.89.248.163
5224
Plesk Licensing



secmail.inetwork.dk
83.89.248.163
5224
Plesk Licensing



secmail.inetwork.dk
83.89.248.163
5432
PostgreSQL



secmail.inetwork.dk
83.89.248.163
5432
PostgreSQL



secmail.inetwork.dk
83.89.248.163
8080
Ookla Speedtest (http)



secmail.inetwork.dk
83.89.248.163
8080
Ookla Speedtest (http)



secmail.inetwork.dk
83.89.248.163
8080
Ookla Speedtest (https)



secmail.inetwork.dk
83.89.248.163
8080
Ookla Speedtest (https)



secmail.inetwork.dk
83.89.248.163
8083
VestaCP http



secmail.inetwork.dk
83.89.248.163
8083
VestaCP http



secmail.inetwork.dk
83.89.248.163
8083
VestaCP https



secmail.inetwork.dk
83.89.248.163
8083
VestaCP https



secmail.inetwork.dk
83.89.248.163
8443
Plesk Administration (https)



secmail.inetwork.dk
83.89.248.163
8443
Plesk Administration (https)



secmail.inetwork.dk
83.89.248.163
8447
Plesk Installer + Updates



secmail.inetwork.dk
83.89.248.163
8447
Plesk Installer + Updates



secmail.inetwork.dk
83.89.248.163
8880
Plesk Administration (http)



secmail.inetwork.dk
83.89.248.163
8880
Plesk Administration (http)



secmail.inetwork.dk
83.89.248.163
10000
Webmin (http)



secmail.inetwork.dk
83.89.248.163
10000
Webmin (http)



secmail.inetwork.dk
83.89.248.163
10000
Webmin (https)



secmail.inetwork.dk
83.89.248.163
10000
Webmin (https)



 

 

Permalink: https://check-your-website.server-daten.de/?i=a8cc7310-009c-4c28-8cef-8baf82057c52

 

Last Result: https://check-your-website.server-daten.de/?q=secmail.inetwork.dk - 2024-07-09 15:50:31

 

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

 

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