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




X

DNS-problem - authoritative Nameserver refused, not defined or timeout

Checked:
10.06.2024 17:23:32


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
ups-tracking.link
A
87.237.55.154
UEbach-Palenberg/North Rhine-Westphalia/Germany (DE) - aurologic GmbH
Hostname: khaki-rabbit-07036.zap.cloud
yes
1
0

AAAA

yes


www.ups-tracking.link


yes
2
2
www.ups-tracking.link
A
87.237.55.154
UEbach-Palenberg/North Rhine-Westphalia/Germany (DE) - aurologic GmbH
No Hostname found
no


*.ups-tracking.link
A
87.237.55.154
yes



AAAA

yes



CNAME

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 5613, 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: 01.07.2024, 00:00:00 +, Signature-Inception: 10.06.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: link
link
1 DS RR in the parent zone found



DS with Algorithm 13, KeyTag 16766, DigestType 2 and Digest QPEEUDXXukjSemZEKyxxyhWdIZdW061NNc8egEGSKLU=



1 RRSIG RR to validate DS RR found



RRSIG-Owner link., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 23.06.2024, 05:00:00 +, Signature-Inception: 10.06.2024, 04:00:00 +, KeyTag 5613, Signer-Name: (root)



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



2 DNSKEY RR found



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



Public Key with Algorithm 13, KeyTag 59568, Flags 256



2 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner link., Algorithm: 13, 1 Labels, original TTL: 900 sec, Signature-expiration: 10.07.2024, 14:22:11 +, Signature-Inception: 10.06.2024, 14:22:11 +, KeyTag 16766, Signer-Name: link



RRSIG-Owner link., Algorithm: 13, 1 Labels, original TTL: 900 sec, Signature-expiration: 10.07.2024, 14:22:11 +, Signature-Inception: 10.06.2024, 14:22:11 +, KeyTag 59568, Signer-Name: link



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



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



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

Zone: ups-tracking.link
ups-tracking.link
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 "121tb8v0kqeq0amic4t7f62vft32878g" between the hashed NSEC3-owner "1210ij1dgbj33uvunsohpm6025amo59r" and the hashed NextOwner "1256jdd0marb02qs58c0k2njs7fjo11v". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 1210ij1dgbj33uvunsohpm6025amo59r.link., Algorithm: 13, 2 Labels, original TTL: 300 sec, Signature-expiration: 10.07.2024, 14:22:11 +, Signature-Inception: 10.06.2024, 14:22:11 +, KeyTag 59568, Signer-Name: link



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "9nos90sudpc503ec1bd8pem2ocmvhduk" as Owner. That's the Hash of "link" with the NextHashedOwnerName "9nu518hoc58uuh0tdvfskaqogbaukqi4". So that domain name is the Closest Encloser of "ups-tracking.link". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 9nos90sudpc503ec1bd8pem2ocmvhduk.link., Algorithm: 13, 2 Labels, original TTL: 300 sec, Signature-expiration: 10.07.2024, 14:22:11 +, Signature-Inception: 10.06.2024, 14:22:11 +, KeyTag 59568, Signer-Name: link



0 DNSKEY RR found




Zone: www.ups-tracking.link
www.ups-tracking.link
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
ups-tracking.link
  ns1.zap-hosting.com
134.255.234.153
Frankfurt am Main/Hesse/Germany (DE) - aurologic GmbH


 
2a0c:3580::5
Frankfurt am Main/Hesse/Germany (DE) - aurologic GmbH


X  ns1.zap-hosting.com.ups-tracking.link


T  ns2.zap-hosting.com
134.255.252.32
Frankfurt am Main/Hesse/Germany (DE) - aurologic GmbH


 
2a0c:3580::6
Frankfurt am Main/Hesse/Germany (DE) - aurologic GmbH

link
  ns.trs-dns.com


  ns01.trs-dns.com / dns01.den1.tucowsregistry.net


  ns01.trs-dns.info / FRA2


  ns01.trs-dns.net / dns02.den1.tucowsregistry.net


  ns01.trs-dns.org / CDG1


4. SOA-Entries


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


Domain:link
Zone-Name:link
Primary:ns.trs-dns.com
Mail:trs-ops.tucows.com
Serial:1718032891
Refresh:1800
Retry:900
Expire:604800
TTL:300
num Entries:4


Domain:ups-tracking.link
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:2


Domain:ups-tracking.link
Zone-Name:ups-tracking.link
Primary:ns1.zap-hosting.com.ups-tracking.link
Mail:root.zap-hosting.com
Serial:1
Refresh:28800
Retry:7200
Expire:604800
TTL:86400
num Entries:3


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://www.ups-tracking.link/
87.237.55.154
302
http://www.ups-tracking.link/./app/track.php
0.240
D
Date: Mon, 10 Jun 2024 15:24:52 GMT
Server: Apache/2.4.41, (Ubuntu)
Location: ./app/track.php
Connection: close
Content-Length: 0
Content-Type: text/html; charset=UTF-8

• http://ups-tracking.link/
87.237.55.154
-16

0.027
W
UnknownError - An error occurred while sending the request. - Unable to read data from the transport connection (FF: PR_CONNECT_RESET_ERROR)

• http://www.ups-tracking.link/./app/track.php
GZip used - 4599 / 31465 - 85.38 %
200

Html is minified: 205.29 %
0.257
H
Date: Mon, 10 Jun 2024 15:24:54 GMT
Server: Apache/2.4.41, (Ubuntu)
Vary: Accept-Encoding
Connection: close
Content-Encoding: gzip
Content-Length: 4599
Content-Type: text/html; charset=UTF-8

• https://ups-tracking.link/
87.237.55.154
-16

0.030
P
UnknownError - The SSL connection could not be established, see inner exception. - Unable to read data from the transport connection (FF: PR_CONNECT_RESET_ERROR)

• https://www.ups-tracking.link/
87.237.55.154
-16

1.063
V
UnknownError - Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. [::ffff:87.237.55.154]:443 (87.237.55.154:443)

• http://ups-tracking.link/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
87.237.55.154
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
404

Html is minified: 100.00 %
0.037
A
Not Found
Visible Content:
Date: Mon, 10 Jun 2024 15:24:53 GMT
Server: Apache/2.4.41, (Ubuntu)
Connection: close
Content-Length: 279
Content-Type: text/html; charset=iso-8859-1

• http://www.ups-tracking.link/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
87.237.55.154
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
404

Html is minified: 100.00 %
0.060
A
Not Found
Visible Content:
Date: Mon, 10 Jun 2024 15:24:53 GMT
Server: Apache/2.4.41, (Ubuntu)
Connection: close
Content-Length: 283
Content-Type: text/html; charset=iso-8859-1

• https://87.237.55.154/
87.237.55.154
-16

1.060
V
UnknownError - Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. [::ffff:87.237.55.154]:443 (87.237.55.154:443)

7. Comments


1. General Results, most used to calculate the result

Aname "ups-tracking.link" is domain, public suffix is ".link", top-level-domain is ".link", top-level-domain-type is "generic", tld-manager is "Uniregistry, Corp.", num .link-domains preloaded: 226 (complete: 245733)
AGood: All ip addresses are public addresses
Warning: Only one ip address found: ups-tracking.link 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: ups-tracking.link has no ipv6 address.
AGood - only one version with Http-Status 200
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: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
Dhttp://www.ups-tracking.link/ 87.237.55.154
302
http://www.ups-tracking.link/./app/track.php
Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
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.
XFatal error: Nameserver doesn't support TCP connection: ns1.zap-hosting.com.ups-tracking.link: Fatal error (-14). Details: Unable to read data from the transport connection: Eine vorhandene Verbindung wurde vom Remotehost geschlossen.. - Eine vorhandene Verbindung wurde vom Remotehost geschlossen.
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 ups-tracking.link, 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.ups-tracking.link

2. Header-Checks (Cross-Origin-* headers are alpha - started 2024-06-05)

U

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

3. DNS- and NameServer - Checks

AInfo:: 7 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
AInfo:: 7 Queries complete, 7 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
Ok (4 - 8):: An average of 3.5 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 3 different Name Servers found: ns1.zap-hosting.com, ns1.zap-hosting.com.ups-tracking.link, ns2.zap-hosting.com, 2 Name Servers included in Delegation: ns1.zap-hosting.com, ns2.zap-hosting.com, 2 Name Servers included in 2 Zone definitions: ns1.zap-hosting.com, ns2.zap-hosting.com, 1 Name Servers listed in SOA.Primary: ns1.zap-hosting.com.ups-tracking.link.
AGood: Only one SOA.Primary Name Server found.: ns1.zap-hosting.com.ups-tracking.link.
Error: SOA.Primary Name Server not included in the delegation set.: ns1.zap-hosting.com.ups-tracking.link.
AGood: Consistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Ordered list of name servers: ns1.zap-hosting.com, ns2.zap-hosting.com
AGood: All Name Server Domain Names have a Public Suffix.
Error: Name Server Domain Names with Public Suffix and without ip address found.: 1 Name Servers without ipv4 and ipv6: 1

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
AGood: Name Servers with different domain names found.: 2 different Domains found
Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: DE
AInfo: Ipv4-Subnet-list: 2 Name Servers, 1 different subnets (first Byte): 134., 1 different subnets (first two Bytes): 134.255., 2 different subnets (first three Bytes): 134.255.234., 134.255.252.
AGood: Name Server IPv4-addresses from different subnet found:
AInfo: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2a0c:, 1 different subnets (first two blocks): 2a0c:3580:, 1 different subnets (first three blocks): 2a0c:3580:0000:, 1 different subnets (first four blocks): 2a0c:3580:0000:0000:
Fatal: All Name Server IPv6 addresses from the same subnet.
AInfo: Nameserver mit different domain names found. May be a problem with DNS-Updates
AGood: Nameserver supports Echo Capitalization: 5 good Nameserver
XNameserver Timeout checking EDNS512: ns2.zap-hosting.com / 134.255.252.32
Nameserver doesn't pass all EDNS-Checks: ns.trs-dns.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: ns1.zap-hosting.com / 134.255.234.153: OP100: fatal timeout. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout.
Nameserver doesn't pass all EDNS-Checks: ns1.zap-hosting.com.ups-tracking.link: OP100: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found, NO OPT100 expected, OPT100 echoed. FLAGS: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1: SOA NOT expected and NOT found, BADVER expected, NOERR found, Version 0 expected, Version greater 0 found. V1OP100: SOA NOT expected and NOT found, BADVER expected, NOERR found, Version 0 expected, Version greater 0 found, NO OPT100 expected, OPT100 echoed. V1FLAGS: SOA NOT expected and NOT found, BADVER expected, NOERR found, Version 0 expected, Version greater 0 found. DNSSEC: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. V1DNSSEC: SOA NOT expected and NOT found, BADVER expected, NOERR found, Version 0 expected, Version greater 0 found. NSID: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. COOKIE: SOA expected, but NOT found, NOERR expectend and NOERR found, Version 0 expectend and found. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns2.zap-hosting.com / 134.255.252.32: OP100: fatal timeout. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: fatal timeout. 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.
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: 569857 milliseconds, 569.857 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: ns1.zap-hosting.com, ns2.zap-hosting.com

QNr.DomainTypeNS used
1
com
NS
j.root-servers.net (2001:503:c27::2:30)

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

Answer: edna.ns.cloudflare.com, josh.ns.cloudflare.com

Answer: edna.ns.cloudflare.com
108.162.192.109, 172.64.32.109, 173.245.58.109, 2606:4700:50::adf5:3a6d, 2803:f800:50::6ca2:c06d, 2a06:98c1:50::ac40:206d

Answer: josh.ns.cloudflare.com
108.162.193.126, 172.64.33.126, 173.245.59.126, 2606:4700:58::adf5:3b7e, 2803:f800:50::6ca2:c17e, 2a06:98c1:50::ac40:217e
3
ns2.zap-hosting.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: edna.ns.cloudflare.com, josh.ns.cloudflare.com

Answer: edna.ns.cloudflare.com
108.162.192.109, 172.64.32.109, 173.245.58.109, 2606:4700:50::adf5:3a6d, 2803:f800:50::6ca2:c06d, 2a06:98c1:50::ac40:206d

Answer: josh.ns.cloudflare.com
108.162.193.126, 172.64.33.126, 173.245.59.126, 2606:4700:58::adf5:3b7e, 2803:f800:50::6ca2:c17e, 2a06:98c1:50::ac40:217e
4
ns1.zap-hosting.com: 134.255.234.153
A
edna.ns.cloudflare.com (2606:4700:50::adf5:3a6d)
5
ns1.zap-hosting.com: 2a0c:3580::5
AAAA
edna.ns.cloudflare.com (2606:4700:50::adf5:3a6d)
6
ns2.zap-hosting.com: 134.255.252.32
A
edna.ns.cloudflare.com (2606:4700:50::adf5:3a6d)
7
ns2.zap-hosting.com: 2a0c:3580::6
AAAA
edna.ns.cloudflare.com (2606:4700:50::adf5:3a6d)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
ups-tracking.link
0

no CAA entry found
1
0
link
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
ups-tracking.link

ok
2
1
_acme-challenge.ups-tracking.link

missing entry or wrong length
1
0
_acme-challenge.ups-tracking.link.ups-tracking.link


2
2


15. DomainService - Entries

TypeDomainPrefValueDNS-errornum AnswersStatusDescription
MX

ups-tracking.link
0
mail.ups-tracking.link
01ok

A


87.237.55.154
01ok

CNAME


00ok
_dmarc
TXT
_dmarc.ups-tracking.link

00ok



16. Cipher Suites

No results


17. Portchecks

DomainIPPortDescriptionResultAnswer
ups-tracking.link
87.237.55.154
21
FTP
open


ups-tracking.link
87.237.55.154
21
FTP
open


ups-tracking.link
87.237.55.154
22
SSH
open


ups-tracking.link
87.237.55.154
22
SSH
open


ups-tracking.link
87.237.55.154
25
SMTP
open


ups-tracking.link
87.237.55.154
25
SMTP
open


ups-tracking.link
87.237.55.154
53
DNS



ups-tracking.link
87.237.55.154
53
DNS



ups-tracking.link
87.237.55.154
110
POP3
open


ups-tracking.link
87.237.55.154
110
POP3
open

This port ist unencrypted and deprecated. Don't use it.
ups-tracking.link
87.237.55.154
143
IMAP
open


ups-tracking.link
87.237.55.154
143
IMAP
open

This port ist unencrypted and deprecated. Don't use it.
ups-tracking.link
87.237.55.154
465
SMTP (encrypted)
open


ups-tracking.link
87.237.55.154
465
SMTP (encrypted)
open


ups-tracking.link
87.237.55.154
587
SMTP (encrypted, submission)
open


ups-tracking.link
87.237.55.154
587
SMTP (encrypted, submission)
open


ups-tracking.link
87.237.55.154
993
IMAP (encrypted)
open


ups-tracking.link
87.237.55.154
993
IMAP (encrypted)
open


ups-tracking.link
87.237.55.154
995
POP3 (encrypted)
open


ups-tracking.link
87.237.55.154
995
POP3 (encrypted)
open


ups-tracking.link
87.237.55.154
1433
MS SQL
open


ups-tracking.link
87.237.55.154
1433
MS SQL
open


ups-tracking.link
87.237.55.154
2082
cPanel (http)
open
http://87.237.55.154:2082/
Http-Status: -14
Timeout - The operation has timed out.

ups-tracking.link
87.237.55.154
2082
cPanel (http)
open
http://87.237.55.154:2082/
Http-Status: -14
Timeout - The operation has timed out.

ups-tracking.link
87.237.55.154
2083
cPanel (https)
open
https://87.237.55.154:2083/
Http-Status: -14
Timeout - The operation has timed out.

ups-tracking.link
87.237.55.154
2083
cPanel (https)
open
https://87.237.55.154:2083/
Http-Status: -14
Timeout - The operation has timed out.

ups-tracking.link
87.237.55.154
2086
WHM (http)
open
http://87.237.55.154:2086/
Http-Status: -14
Timeout - The operation has timed out.

ups-tracking.link
87.237.55.154
2086
WHM (http)
open
http://87.237.55.154:2086/
Http-Status: -14
Timeout - The operation has timed out.

ups-tracking.link
87.237.55.154
2087
WHM (https)
open
https://87.237.55.154:2087/
Http-Status: -14
Timeout - The operation has timed out.

ups-tracking.link
87.237.55.154
2087
WHM (https)
open
https://87.237.55.154:2087/
Http-Status: -14
Timeout - The operation has timed out.

ups-tracking.link
87.237.55.154
2089
cPanel Licensing
open


ups-tracking.link
87.237.55.154
2089
cPanel Licensing
open


ups-tracking.link
87.237.55.154
2095
cPanel Webmail (http)
open
http://87.237.55.154:2095/
Http-Status: -14
Timeout - The operation has timed out.

ups-tracking.link
87.237.55.154
2095
cPanel Webmail (http)
open
http://87.237.55.154:2095/
Http-Status: -14
Timeout - The operation has timed out.

ups-tracking.link
87.237.55.154
2096
cPanel Webmail (https)
open
https://87.237.55.154:2096/
Http-Status: -14
Timeout - The operation has timed out.

ups-tracking.link
87.237.55.154
2096
cPanel Webmail (https)
open
https://87.237.55.154:2096/
Http-Status: -14
Timeout - The operation has timed out.

ups-tracking.link
87.237.55.154
2222
DirectAdmin (http)
open
http://87.237.55.154:2222/
Http-Status: -14
Timeout - The operation has timed out.

ups-tracking.link
87.237.55.154
2222
DirectAdmin (http)
open
http://87.237.55.154:2222/
Http-Status: -14
Timeout - The operation has timed out.

ups-tracking.link
87.237.55.154
2222
DirectAdmin (https)
open
https://87.237.55.154:2222/
Http-Status: -14
Timeout - The operation has timed out.

ups-tracking.link
87.237.55.154
2222
DirectAdmin (https)
open
https://87.237.55.154:2222/
Http-Status: -14
Timeout - The operation has timed out.

ups-tracking.link
87.237.55.154
3306
mySql
open


ups-tracking.link
87.237.55.154
3306
mySql
open


ups-tracking.link
87.237.55.154
5224
Plesk Licensing
open


ups-tracking.link
87.237.55.154
5224
Plesk Licensing
open


ups-tracking.link
87.237.55.154
5432
PostgreSQL
open


ups-tracking.link
87.237.55.154
5432
PostgreSQL
open


ups-tracking.link
87.237.55.154
8080
Ookla Speedtest (http)
open
http://87.237.55.154:8080/
Http-Status: -14
Timeout - The operation has timed out.

ups-tracking.link
87.237.55.154
8080
Ookla Speedtest (http)
open
http://87.237.55.154:8080/
Http-Status: -14
Timeout - The operation has timed out.

ups-tracking.link
87.237.55.154
8080
Ookla Speedtest (https)
open
https://87.237.55.154:8080/
Http-Status: -14
Timeout - The operation has timed out.

ups-tracking.link
87.237.55.154
8080
Ookla Speedtest (https)
open
https://87.237.55.154:8080/
Http-Status: -14
Timeout - The operation has timed out.

ups-tracking.link
87.237.55.154
8083
VestaCP http
open
http://87.237.55.154:8083/
Http-Status: -14
Timeout - The operation has timed out.

ups-tracking.link
87.237.55.154
8083
VestaCP http
open
http://87.237.55.154:8083/
Http-Status: -14
Timeout - The operation has timed out.

ups-tracking.link
87.237.55.154
8083
VestaCP https
open
https://87.237.55.154:8083/
Http-Status: -14
Timeout - The operation has timed out.

ups-tracking.link
87.237.55.154
8083
VestaCP https
open
https://87.237.55.154:8083/
Http-Status: -14
Timeout - The operation has timed out.

ups-tracking.link
87.237.55.154
8443
Plesk Administration (https)
open
https://87.237.55.154:8443/
Http-Status: -16
UnknownError - The SSL connection could not be established, see inner exception. - Unable to read data from the transport connection (FF: PR_CONNECT_RESET_ERROR)

ups-tracking.link
87.237.55.154
8443
Plesk Administration (https)
open
https://87.237.55.154:8443/
Http-Status: -16
UnknownError - The SSL connection could not be established, see inner exception. - Unable to read data from the transport connection (FF: PR_CONNECT_RESET_ERROR)

ups-tracking.link
87.237.55.154
8447
Plesk Installer + Updates
open


ups-tracking.link
87.237.55.154
8447
Plesk Installer + Updates
open


ups-tracking.link
87.237.55.154
8880
Plesk Administration (http)
open
http://87.237.55.154:8880/
Http-Status: -16
UnknownError - An error occurred while sending the request. - Unable to read data from the transport connection (FF: PR_CONNECT_RESET_ERROR)

ups-tracking.link
87.237.55.154
8880
Plesk Administration (http)
open
http://87.237.55.154:8880/
Http-Status: -16
UnknownError - An error occurred while sending the request. - Unable to read data from the transport connection (FF: PR_CONNECT_RESET_ERROR)

ups-tracking.link
87.237.55.154
10000
Webmin (http)
open
http://87.237.55.154:10000/
Http-Status: -16
UnknownError - An error occurred while sending the request. - Unable to read data from the transport connection (FF: PR_CONNECT_RESET_ERROR)

ups-tracking.link
87.237.55.154
10000
Webmin (http)
open
http://87.237.55.154:10000/
Http-Status: -16
UnknownError - An error occurred while sending the request. - Unable to read data from the transport connection (FF: PR_CONNECT_RESET_ERROR)

ups-tracking.link
87.237.55.154
10000
Webmin (https)
open
https://87.237.55.154:10000/
Http-Status: -14
Timeout - The operation has timed out.

ups-tracking.link
87.237.55.154
10000
Webmin (https)
open
https://87.237.55.154:10000/
Http-Status: -14
Timeout - The operation has timed out.



Permalink: https://check-your-website.server-daten.de/?i=4266cd5a-f015-4c01-9d15-2fa9afc2481d


Last Result: https://check-your-website.server-daten.de/?q=ups-tracking.link - 2024-06-10 17:23:32


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

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

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