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




V

Connect failure - perhaps firewall

Checked:
02.06.2020 05:33:57


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
admin.matchups.games
A
3.20.180.23
Dublin/Ohio/United States (US) - Amazon.com, Inc.
Hostname: ec2-3-20-180-23.us-east-2.compute.amazonaws.com
yes
1
0

AAAA

yes


www.admin.matchups.games

Name Error
yes
1
0
*.matchups.games
A
Name Error
yes



A
Name Error
yes



AAAA
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes



CNAME
Name Error
yes


*.admin.matchups.games
A
Name Error
yes



A
Name Error
yes



AAAA
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes



CNAME
Name Error
yes



2. DNSSEC

Zone (*)DNSSEC - Informations (some minor bugs wildcard + nsec/nsec3)

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



Status: Valid because published



2 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 48903, Flags 256



1 RRSIG RR to validate DNSKEY RR found



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



1 RRSIG RR to validate DS RR found



RRSIG-Owner games., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 14.06.2020, 17:00:00 +, Signature-Inception: 01.06.2020, 16:00:00 +, KeyTag 48903, Signer-Name: (root)



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



3 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 15366, Flags 256



Public Key with Algorithm 8, KeyTag 43374, Flags 256



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



3 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner games., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 27.06.2020, 23:16:33 +, Signature-Inception: 28.05.2020, 22:46:20 +, KeyTag 15366, Signer-Name: games



RRSIG-Owner games., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 27.06.2020, 23:16:33 +, Signature-Inception: 28.05.2020, 22:46:20 +, KeyTag 43374, Signer-Name: games



RRSIG-Owner games., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 27.06.2020, 23:16:33 +, Signature-Inception: 28.05.2020, 22:46:20 +, KeyTag 59386, Signer-Name: games



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



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



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



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



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

Zone: matchups.games
matchups.games
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 "8ojmma2ahle1bjhd839q8l10r1h92qur" between the hashed NSEC3-owner "8ohm43diotr9lguob1jr1gmdpffhn59r" and the hashed NextOwner "8oug1g9an42urcgsj7f8cb2jvd6jmlqa". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 8ohm43diotr9lguob1jr1gmdpffhn59r.games., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 01.07.2020, 04:55:49 +, Signature-Inception: 01.06.2020, 03:55:49 +, KeyTag 15366, Signer-Name: games



DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed query name "8ojmma2ahle1bjhd839q8l10r1h92qur" between the hashed NSEC3-owner "8ohm43diotr9lguob1jr1gmdpffhn59r" and the hashed NextOwner "8oug1g9an42urcgsj7f8cb2jvd6jmlqa". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 8ohm43diotr9lguob1jr1gmdpffhn59r.games., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 01.07.2020, 04:55:49 +, Signature-Inception: 01.06.2020, 03:55:49 +, KeyTag 43374, Signer-Name: games



0 DNSKEY RR found




Zone: admin.matchups.games
admin.matchups.games
0 DS RR in the parent zone found



0 DNSKEY RR found




Zone: www.admin.matchups.games
www.admin.matchups.games
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.admin.matchups.games
  ns-1430.awsdns-50.org

admin.matchups.games
  ns-1430.awsdns-50.org / 841fedd5093f028bd1a5f996bb53f427 -
205.251.197.150
Seattle/Washington/United States (US) - Amazon.com, Inc.


 
2600:9000:5305:9600::1
Seattle/Washington/United States (US) - Amazon.com

matchups.games
T  ec2-52-15-100-203.us-east-2.compute.amazonaws.com
52.15.100.203
Dublin/Ohio/United States (US) - Amazon.com, Inc.


  ns-1430.awsdns-50.org / 4b65f8097a21711bd312c3a7a90557c5 -
205.251.197.150
Seattle/Washington/United States (US) - Amazon.com, Inc.


 
2600:9000:5305:9600::1
Seattle/Washington/United States (US) - Amazon.com


  ns-1922.awsdns-48.co.uk / 4299825d66b7b6cedccbcacfe4d8362c -
205.251.199.130
Chicago/Illinois/United States (US) - Amazon.com, Inc.


 
2600:9000:5307:8200::1
Seattle/Washington/United States (US) - Amazon.com


  ns-305.awsdns-38.com / 758989b8a91eaa6347c0e27feb0a1605 -
205.251.193.49
Chicago/Illinois/United States (US) - Amazon.com, Inc.


 
2600:9000:5301:3100::1
Seattle/Washington/United States (US) - Amazon.com


  ns-740.awsdns-28.net / 069d9eacb1c39f187625f2ad12ef56da -
205.251.194.228
Seattle/Washington/United States (US) - Amazon.com, Inc.


 
2600:9000:5302:e400::1
Seattle/Washington/United States (US) - Amazon.com

games
  demand.alpha.aridns.net.au / dns1.frpar1


  demand.beta.aridns.net.au / dns1.defra1


  demand.delta.aridns.net.au / dns4.frpar1


  demand.gamma.aridns.net.au / dns4.defra1


4. SOA-Entries


Domain:games
Zone-Name:games
Primary:demand.alpha.aridns.net.au
Mail:hostmaster.donuts.co
Serial:1591068526
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:4


Domain:matchups.games
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


Domain:matchups.games
Zone-Name:matchups.games
Primary:ns-1430.awsdns-50.org
Mail:awsdns-hostmaster.amazon.com
Serial:1
Refresh:7200
Retry:900
Expire:1209600
TTL:86400
num Entries:8


Domain:admin.matchups.games
Zone-Name:matchups.games
Primary:ns-1430.awsdns-50.org
Mail:awsdns-hostmaster.amazon.com
Serial:1
Refresh:7200
Retry:900
Expire:1209600
TTL:86400
num Entries:2


Domain:www.admin.matchups.games
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


:

:
DomainnameHttp-StatusredirectSec.G
• http://admin.matchups.games/
3.20.180.23 GZip used - 384 / 612 - 37.25 %
200

Html is minified: 129.94 %
0.243
H
small visible content (num chars: 273)
Welcome to nginx! If you see this page, the nginx web server is successfully installed and working. Further configuration is required. For online documentation and support please refer to nginx.org . Commercial support is available at nginx.com . Thank you for using nginx.
Server: nginx/1.14.0 (Ubuntu)
Date: Tue, 02 Jun 2020 03:35:56 GMT
Content-Type: text/html
Last-Modified: Mon, 01 Jun 2020 17:56:36 GMT
Transfer-Encoding: chunked
Connection: close
ETag: W/"5ed54154-264"
Content-Encoding: gzip

• https://admin.matchups.games/
3.20.180.23
-2

1.364
V
ConnectFailure - Unable to connect to the remote server

• http://admin.matchups.games/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
3.20.180.23 GZip used - 141 / 178 - 20.79 %
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
404

Html is minified: 108.54 %
0.247
A
Not Found
Visible Content: 404 Not Found nginx/1.14.0 (Ubuntu)
Server: nginx/1.14.0 (Ubuntu)
Date: Tue, 02 Jun 2020 03:35:57 GMT
Content-Type: text/html
Transfer-Encoding: chunked
Connection: close
Content-Encoding: gzip

• https://3.20.180.23/
3.20.180.23
-2

1.360
V
ConnectFailure - Unable to connect to the remote server

7. Comments


1. General Results, most used to calculate the result

Aname "admin.matchups.games" is subdomain, public suffix is "games", top-level-domain-type is "generic", tld-manager is "United TLD Holdco Ltd."
Agood: All ip addresses are public addresses
Warning: Only one ip address found: admin.matchups.games 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: admin.matchups.games 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 - only one version with Http-Status 200
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
AGood: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):0 complete Content-Type - header (2 urls)
http://admin.matchups.games/ 3.20.180.23


Url with incomplete Content-Type - header - missing charset
http://admin.matchups.games/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 3.20.180.23


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

connect failure - perhaps firewall
Vhttps://3.20.180.23/ 3.20.180.23
-2

connect failure - perhaps firewall
XFatal error: Nameserver doesn't support TCP connection: ec2-52-15-100-203.us-east-2.compute.amazonaws.com / 52.15.100.203: Timeout
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 admin.matchups.games, 1 ip addresses.

2. DNS- and NameServer - Checks

AInfo:: 109 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 0 Name Servers.
AInfo:: 109 Queries complete, 109 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
AInfo:: 5 different Name Servers found: ec2-52-15-100-203.us-east-2.compute.amazonaws.com, ns-1430.awsdns-50.org, ns-1922.awsdns-48.co.uk, ns-305.awsdns-38.com, ns-740.awsdns-28.net, 4 Name Servers included in Delegation: ns-1430.awsdns-50.org, ns-1922.awsdns-48.co.uk, ns-305.awsdns-38.com, ns-740.awsdns-28.net, 5 Name Servers included in 2 Zone definitions: ec2-52-15-100-203.us-east-2.compute.amazonaws.com, ns-1430.awsdns-50.org, ns-1922.awsdns-48.co.uk, ns-305.awsdns-38.com, ns-740.awsdns-28.net, 1 Name Servers listed in SOA.Primary: ns-1430.awsdns-50.org.
AGood: Only one SOA.Primary Name Server found.: ns-1430.awsdns-50.org.
AGood: SOA.Primary Name Server included in the delegation set.: ns-1430.awsdns-50.org.
XFatal: Inconsistency 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.: ns-1430.awsdns-50.org (205.251.197.150): Delegation: ns-1430.awsdns-50.org, ns-1922.awsdns-48.co.uk, ns-305.awsdns-38.com, ns-740.awsdns-28.net, Zone: ec2-52-15-100-203.us-east-2.compute.amazonaws.com, ns-1430.awsdns-50.org, ns-1922.awsdns-48.co.uk, ns-305.awsdns-38.com, ns-740.awsdns-28.net
XFatal: Inconsistency 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.: ns-1430.awsdns-50.org (2600:9000:5305:9600::1): Delegation: ns-1430.awsdns-50.org, ns-1922.awsdns-48.co.uk, ns-305.awsdns-38.com, ns-740.awsdns-28.net, Zone: ec2-52-15-100-203.us-east-2.compute.amazonaws.com, ns-1430.awsdns-50.org, ns-1922.awsdns-48.co.uk, ns-305.awsdns-38.com, ns-740.awsdns-28.net
XFatal: Inconsistency 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.: ns-1922.awsdns-48.co.uk (205.251.199.130): Delegation: ns-1430.awsdns-50.org, ns-1922.awsdns-48.co.uk, ns-305.awsdns-38.com, ns-740.awsdns-28.net, Zone: ec2-52-15-100-203.us-east-2.compute.amazonaws.com, ns-1430.awsdns-50.org, ns-1922.awsdns-48.co.uk, ns-305.awsdns-38.com, ns-740.awsdns-28.net
XFatal: Inconsistency 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.: ns-1922.awsdns-48.co.uk (2600:9000:5307:8200::1): Delegation: ns-1430.awsdns-50.org, ns-1922.awsdns-48.co.uk, ns-305.awsdns-38.com, ns-740.awsdns-28.net, Zone: ec2-52-15-100-203.us-east-2.compute.amazonaws.com, ns-1430.awsdns-50.org, ns-1922.awsdns-48.co.uk, ns-305.awsdns-38.com, ns-740.awsdns-28.net
XFatal: Inconsistency 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.: ns-305.awsdns-38.com (205.251.193.49): Delegation: ns-1430.awsdns-50.org, ns-1922.awsdns-48.co.uk, ns-305.awsdns-38.com, ns-740.awsdns-28.net, Zone: ec2-52-15-100-203.us-east-2.compute.amazonaws.com, ns-1430.awsdns-50.org, ns-1922.awsdns-48.co.uk, ns-305.awsdns-38.com, ns-740.awsdns-28.net
XFatal: Inconsistency 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.: ns-305.awsdns-38.com (2600:9000:5301:3100::1): Delegation: ns-1430.awsdns-50.org, ns-1922.awsdns-48.co.uk, ns-305.awsdns-38.com, ns-740.awsdns-28.net, Zone: ec2-52-15-100-203.us-east-2.compute.amazonaws.com, ns-1430.awsdns-50.org, ns-1922.awsdns-48.co.uk, ns-305.awsdns-38.com, ns-740.awsdns-28.net
XFatal: Inconsistency 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.: ns-740.awsdns-28.net (205.251.194.228): Delegation: ns-1430.awsdns-50.org, ns-1922.awsdns-48.co.uk, ns-305.awsdns-38.com, ns-740.awsdns-28.net, Zone: ec2-52-15-100-203.us-east-2.compute.amazonaws.com, ns-1430.awsdns-50.org, ns-1922.awsdns-48.co.uk, ns-305.awsdns-38.com, ns-740.awsdns-28.net
XFatal: Inconsistency 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.: ns-740.awsdns-28.net (2600:9000:5302:e400::1): Delegation: ns-1430.awsdns-50.org, ns-1922.awsdns-48.co.uk, ns-305.awsdns-38.com, ns-740.awsdns-28.net, Zone: ec2-52-15-100-203.us-east-2.compute.amazonaws.com, ns-1430.awsdns-50.org, ns-1922.awsdns-48.co.uk, ns-305.awsdns-38.com, ns-740.awsdns-28.net
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: 5 different Name Servers found
AGood: Some Name Servers have IPv6 addresses: 4 Name Servers with IPv6 found (1 Name Servers without IPv6)
AGood: Name servers with different Top Level Domains / Public Suffix List entries found: 5 Name Servers, 5 Top Level Domains: org, net, com, co.uk, *.compute.amazonaws.com
AGood: Name Servers with different domain names found.: 5 different Domains found
Warning: All Name Servers from the same Country / IP location.: 5 Name Servers, 1 Countries: US
AInfo: Ipv4-Subnet-list: 5 Name Servers, 2 different subnets (first Byte): 205., 52., 2 different subnets (first two Bytes): 205.251., 52.15., 5 different subnets (first three Bytes): 205.251.193., 205.251.194., 205.251.197., 205.251.199., 52.15.100.
AGood: Name Server IPv4-addresses from different subnet found:
AInfo: IPv6-Subnet-list: 4 Name Servers with IPv6, 1 different subnets (first block): 2600:, 1 different subnets (first two blocks): 2600:9000:, 4 different subnets (first three blocks): 2600:9000:5301:, 2600:9000:5302:, 2600:9000:5305:, 2600:9000:5307:, 4 different subnets (first four blocks): 2600:9000:5301:3100:, 2600:9000:5302:e400:, 2600:9000:5305:9600:, 2600:9000:5307:8200:
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
XNameserver Timeout checking Echo Capitalization: ec2-52-15-100-203.us-east-2.compute.amazonaws.com / 52.15.100.203
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 2 good Nameserver
XNameserver Timeout checking EDNS512: ec2-52-15-100-203.us-east-2.compute.amazonaws.com / 52.15.100.203
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 2 good Nameserver
Nameserver doesn't pass all EDNS-Checks: ec2-52-15-100-203.us-east-2.compute.amazonaws.com / 52.15.100.203: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout.
Nameserver doesn't pass all EDNS-Checks: ns-1430.awsdns-50.org: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
AGood: All SOA have the same Serial Number
Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries.

3. 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: 136030 milliseconds, 136.030 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" > 2019 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: ec2-52-15-100-203.us-east-2.compute.amazonaws.com, ns-1430.awsdns-50.org, ns-1922.awsdns-48.co.uk, ns-305.awsdns-38.com, ns-740.awsdns-28.net

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

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
ec2-52-15-100-203.us-east-2.compute.amazonaws.com
NS
b.gtld-servers.net (2001:503:231d::2:30)

Answer: r1.amazonaws.com, r2.amazonaws.com, u1.amazonaws.com, u2.amazonaws.com

Answer: r1.amazonaws.com
205.251.192.27, 2600:9000:5300:1b00::1

Answer: r2.amazonaws.com
205.251.195.199, 2600:9000:5303:c700::1

Answer: u1.amazonaws.com
156.154.64.10, 2001:502:f3ff::10

Answer: u2.amazonaws.com
156.154.65.10, 2610:a1:1014::10
3
org
NS
c.root-servers.net (2001:500:2::c)

Answer: a0.org.afilias-nst.info, a2.org.afilias-nst.info, b0.org.afilias-nst.org, b2.org.afilias-nst.org, c0.org.afilias-nst.info, d0.org.afilias-nst.org
4
ns-1430.awsdns-50.org
NS
a0.org.afilias-nst.info (2001:500:e::1)

Answer: g-ns-1077.awsdns-50.org, g-ns-1650.awsdns-50.org, g-ns-178.awsdns-50.org, g-ns-756.awsdns-50.org

Answer: g-ns-1077.awsdns-50.org
205.251.196.53, 2600:9000:5304:3500::1

Answer: g-ns-1650.awsdns-50.org
205.251.198.114, 2600:9000:5306:7200::1

Answer: g-ns-178.awsdns-50.org
205.251.192.178, 2600:9000:5300:b200::1

Answer: g-ns-756.awsdns-50.org
205.251.194.244, 2600:9000:5302:f400::1
5
uk
NS
l.root-servers.net (2001:500:9f::42)

Answer: dns1.nic.uk, dns2.nic.uk, dns3.nic.uk, dns4.nic.uk, nsa.nic.uk, nsb.nic.uk, nsc.nic.uk, nsd.nic.uk
6
ns-1922.awsdns-48.co.uk
NS
dns1.nic.uk (2a01:618:400::1)

Answer: g-ns-1523.awsdns-48.co.uk, g-ns-1844.awsdns-48.co.uk, g-ns-368.awsdns-48.co.uk, g-ns-944.awsdns-48.co.uk

Answer: g-ns-1523.awsdns-48.co.uk
205.251.197.243, 2600:9000:5305:f300::1

Answer: g-ns-1844.awsdns-48.co.uk
205.251.199.52, 2600:9000:5307:3400::1

Answer: g-ns-368.awsdns-48.co.uk
205.251.193.112, 2600:9000:5301:7000::1

Answer: g-ns-944.awsdns-48.co.uk
205.251.195.176, 2600:9000:5303:b000::1
7
ns-305.awsdns-38.com
NS
b.gtld-servers.net (2001:503:231d::2:30)

Answer: g-ns-1190.awsdns-38.com, g-ns-1766.awsdns-38.com, g-ns-39.awsdns-38.com, g-ns-614.awsdns-38.com

Answer: g-ns-1190.awsdns-38.com
205.251.196.166, 2600:9000:5304:a600::1

Answer: g-ns-1766.awsdns-38.com
205.251.198.230, 2600:9000:5306:e600::1

Answer: g-ns-39.awsdns-38.com
205.251.192.39, 2600:9000:5300:2700::1

Answer: g-ns-614.awsdns-38.com
205.251.194.102, 2600:9000:5302:6600::1
8
net
NS
g.root-servers.net (2001:500:12::d0d)

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
9
ns-740.awsdns-28.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: g-ns-1372.awsdns-28.net, g-ns-1948.awsdns-28.net, g-ns-477.awsdns-28.net, g-ns-798.awsdns-28.net

Answer: g-ns-1372.awsdns-28.net
205.251.197.92, 2600:9000:5305:5c00::1

Answer: g-ns-1948.awsdns-28.net
205.251.199.156, 2600:9000:5307:9c00::1

Answer: g-ns-477.awsdns-28.net
205.251.193.221, 2600:9000:5301:dd00::1

Answer: g-ns-798.awsdns-28.net
205.251.195.30, 2600:9000:5303:1e00::1
10
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No A record found
A
r1.amazonaws.com (2600:9000:5300:1b00::1)
11
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No AAAA record found
AAAA
r1.amazonaws.com (2600:9000:5300:1b00::1)
12
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No A record found
A
r1.amazonaws.com (2600:9000:5300:1b00::1)
13
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No AAAA record found
AAAA
r1.amazonaws.com (2600:9000:5300:1b00::1)
14
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No A record found
A
r1.amazonaws.com (2600:9000:5300:1b00::1)
15
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No AAAA record found
AAAA
r1.amazonaws.com (2600:9000:5300:1b00::1)
16
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No A record found
A
r1.amazonaws.com (2600:9000:5300:1b00::1)
17
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No AAAA record found
AAAA
r1.amazonaws.com (2600:9000:5300:1b00::1)
18
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No A record found
A
r1.amazonaws.com (2600:9000:5300:1b00::1)
19
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No AAAA record found
AAAA
r1.amazonaws.com (2600:9000:5300:1b00::1)
20
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No A record found
A
r1.amazonaws.com (2600:9000:5300:1b00::1)
21
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No AAAA record found
AAAA
r1.amazonaws.com (2600:9000:5300:1b00::1)
22
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No A record found
A
r1.amazonaws.com (2600:9000:5300:1b00::1)
23
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No AAAA record found
AAAA
r1.amazonaws.com (2600:9000:5300:1b00::1)
24
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No A record found
A
r1.amazonaws.com (2600:9000:5300:1b00::1)
25
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No AAAA record found
AAAA
r1.amazonaws.com (2600:9000:5300:1b00::1)
26
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No A record found
A
r1.amazonaws.com (2600:9000:5300:1b00::1)
27
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No AAAA record found
AAAA
r1.amazonaws.com (2600:9000:5300:1b00::1)
28
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No A record found
A
r1.amazonaws.com (2600:9000:5300:1b00::1)
29
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No AAAA record found
AAAA
r1.amazonaws.com (2600:9000:5300:1b00::1)
30
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No A record found
A
r1.amazonaws.com (2600:9000:5300:1b00::1)
31
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No AAAA record found
AAAA
r1.amazonaws.com (2600:9000:5300:1b00::1)
32
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No A record found
A
r1.amazonaws.com (2600:9000:5300:1b00::1)
33
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No AAAA record found
AAAA
r1.amazonaws.com (2600:9000:5300:1b00::1)
34
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No A record found
A
r1.amazonaws.com (2600:9000:5300:1b00::1)
35
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No AAAA record found
AAAA
r1.amazonaws.com (2600:9000:5300:1b00::1)
36
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No A record found
A
r1.amazonaws.com (2600:9000:5300:1b00::1)
37
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No AAAA record found
AAAA
r1.amazonaws.com (2600:9000:5300:1b00::1)
38
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No A record found
A
r1.amazonaws.com (2600:9000:5300:1b00::1)
39
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No AAAA record found
AAAA
r1.amazonaws.com (2600:9000:5300:1b00::1)
40
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No A record found
A
r1.amazonaws.com (2600:9000:5300:1b00::1)
41
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No AAAA record found
AAAA
r1.amazonaws.com (2600:9000:5300:1b00::1)
42
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No A record found
A
r1.amazonaws.com (2600:9000:5300:1b00::1)
43
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No AAAA record found
AAAA
r1.amazonaws.com (2600:9000:5300:1b00::1)
44
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No A record found
A
r1.amazonaws.com (2600:9000:5300:1b00::1)
45
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No AAAA record found
AAAA
r1.amazonaws.com (2600:9000:5300:1b00::1)
46
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No A record found
A
r1.amazonaws.com (2600:9000:5300:1b00::1)
47
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No AAAA record found
AAAA
r1.amazonaws.com (2600:9000:5300:1b00::1)
48
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No A record found
A
r1.amazonaws.com (2600:9000:5300:1b00::1)
49
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No AAAA record found
AAAA
r1.amazonaws.com (2600:9000:5300:1b00::1)
50
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No A record found
A
r1.amazonaws.com (2600:9000:5300:1b00::1)
51
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No AAAA record found
AAAA
r1.amazonaws.com (2600:9000:5300:1b00::1)
52
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No A record found
A
r1.amazonaws.com (2600:9000:5300:1b00::1)
53
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No AAAA record found
AAAA
r1.amazonaws.com (2600:9000:5300:1b00::1)
54
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No A record found
A
r1.amazonaws.com (2600:9000:5300:1b00::1)
55
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No AAAA record found
AAAA
r1.amazonaws.com (2600:9000:5300:1b00::1)
56
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No A record found
A
r1.amazonaws.com (2600:9000:5300:1b00::1)
57
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No AAAA record found
AAAA
r1.amazonaws.com (2600:9000:5300:1b00::1)
58
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No A record found
A
r1.amazonaws.com (2600:9000:5300:1b00::1)
59
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No AAAA record found
AAAA
r1.amazonaws.com (2600:9000:5300:1b00::1)
60
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No A record found
A
r1.amazonaws.com (2600:9000:5300:1b00::1)
61
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No AAAA record found
AAAA
r1.amazonaws.com (2600:9000:5300:1b00::1)
62
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No A record found
A
r1.amazonaws.com (2600:9000:5300:1b00::1)
63
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No AAAA record found
AAAA
r1.amazonaws.com (2600:9000:5300:1b00::1)
64
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No A record found
A
r1.amazonaws.com (2600:9000:5300:1b00::1)
65
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No AAAA record found
AAAA
r1.amazonaws.com (2600:9000:5300:1b00::1)
66
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No A record found
A
r1.amazonaws.com (2600:9000:5300:1b00::1)
67
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No AAAA record found
AAAA
r1.amazonaws.com (2600:9000:5300:1b00::1)
68
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No A record found
A
r1.amazonaws.com (2600:9000:5300:1b00::1)
69
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No AAAA record found
AAAA
r1.amazonaws.com (2600:9000:5300:1b00::1)
70
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No A record found
A
r1.amazonaws.com (2600:9000:5300:1b00::1)
71
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No AAAA record found
AAAA
r1.amazonaws.com (2600:9000:5300:1b00::1)
72
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No A record found
A
r1.amazonaws.com (2600:9000:5300:1b00::1)
73
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No AAAA record found
AAAA
r1.amazonaws.com (2600:9000:5300:1b00::1)
74
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No A record found
A
r1.amazonaws.com (2600:9000:5300:1b00::1)
75
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No AAAA record found
AAAA
r1.amazonaws.com (2600:9000:5300:1b00::1)
76
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No A record found
A
r1.amazonaws.com (2600:9000:5300:1b00::1)
77
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No AAAA record found
AAAA
r1.amazonaws.com (2600:9000:5300:1b00::1)
78
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No A record found
A
r1.amazonaws.com (2600:9000:5300:1b00::1)
79
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No AAAA record found
AAAA
r1.amazonaws.com (2600:9000:5300:1b00::1)
80
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No A record found
A
r1.amazonaws.com (2600:9000:5300:1b00::1)
81
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No AAAA record found
AAAA
r1.amazonaws.com (2600:9000:5300:1b00::1)
82
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No A record found
A
r1.amazonaws.com (2600:9000:5300:1b00::1)
83
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No AAAA record found
AAAA
r1.amazonaws.com (2600:9000:5300:1b00::1)
84
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No A record found
A
r1.amazonaws.com (2600:9000:5300:1b00::1)
85
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No AAAA record found
AAAA
r1.amazonaws.com (2600:9000:5300:1b00::1)
86
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No A record found
A
r1.amazonaws.com (2600:9000:5300:1b00::1)
87
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No AAAA record found
AAAA
r1.amazonaws.com (2600:9000:5300:1b00::1)
88
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No A record found
A
r1.amazonaws.com (2600:9000:5300:1b00::1)
89
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No AAAA record found
AAAA
r1.amazonaws.com (2600:9000:5300:1b00::1)
90
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No A record found
A
r1.amazonaws.com (2600:9000:5300:1b00::1)
91
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No AAAA record found
AAAA
r1.amazonaws.com (2600:9000:5300:1b00::1)
92
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No A record found
A
r1.amazonaws.com (2600:9000:5300:1b00::1)
93
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No AAAA record found
AAAA
r1.amazonaws.com (2600:9000:5300:1b00::1)
94
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No A record found
A
r1.amazonaws.com (2600:9000:5300:1b00::1)
95
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No AAAA record found
AAAA
r1.amazonaws.com (2600:9000:5300:1b00::1)
96
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No A record found
A
r1.amazonaws.com (2600:9000:5300:1b00::1)
97
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No AAAA record found
AAAA
r1.amazonaws.com (2600:9000:5300:1b00::1)
98
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No A record found
A
r1.amazonaws.com (2600:9000:5300:1b00::1)
99
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No AAAA record found
AAAA
r1.amazonaws.com (2600:9000:5300:1b00::1)
100
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No A record found
A
r1.amazonaws.com (2600:9000:5300:1b00::1)
101
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No AAAA record found
AAAA
r1.amazonaws.com (2600:9000:5300:1b00::1)
102
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No A record found
A
r1.amazonaws.com (2600:9000:5300:1b00::1)
103
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No AAAA record found
AAAA
r1.amazonaws.com (2600:9000:5300:1b00::1)
104
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No A record found
A
r1.amazonaws.com (2600:9000:5300:1b00::1)
105
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No AAAA record found
AAAA
r1.amazonaws.com (2600:9000:5300:1b00::1)
106
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No A record found
A
r1.amazonaws.com (2600:9000:5300:1b00::1)
107
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No AAAA record found
AAAA
r1.amazonaws.com (2600:9000:5300:1b00::1)
108
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No A record found
A
r1.amazonaws.com (2600:9000:5300:1b00::1)
109
ec2-52-15-100-203.us-east-2.compute.amazonaws.com: No AAAA record found
AAAA
r1.amazonaws.com (2600:9000:5300:1b00::1)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
admin.matchups.games
0

no CAA entry found
1
0
matchups.games
0

no CAA entry found
1
0
games
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
matchups.games

ok
1
0
admin.matchups.games

ok
1
0
_acme-challenge.admin.matchups.games

Name Error - The domain name does not exist
1
0
_acme-challenge.admin.matchups.games.matchups.games

Name Error - The domain name does not exist
1
0
_acme-challenge.admin.matchups.games.admin.matchups.games

Name Error - The domain name does not exist
1
0


15. Portchecks

Domain or IPPortDescriptionResultAnswer
admin.matchups.games
21
FTP



admin.matchups.games
21
FTP



admin.matchups.games
22
SSH
open
SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3

admin.matchups.games
22
SSH
open
SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3

admin.matchups.games
25
SMTP



admin.matchups.games
25
SMTP



admin.matchups.games
53
DNS



admin.matchups.games
53
DNS



admin.matchups.games
110
POP3



admin.matchups.games
110
POP3



admin.matchups.games
143
IMAP



admin.matchups.games
143
IMAP



admin.matchups.games
465
SMTP (encrypted)



admin.matchups.games
465
SMTP (encrypted)



admin.matchups.games
587
SMTP (encrypted, submission)



admin.matchups.games
587
SMTP (encrypted, submission)



admin.matchups.games
993
IMAP (encrypted)



admin.matchups.games
993
IMAP (encrypted)



admin.matchups.games
995
POP3 (encrypted)



admin.matchups.games
995
POP3 (encrypted)



admin.matchups.games
1433
MS SQL



admin.matchups.games
1433
MS SQL



admin.matchups.games
2082
cPanel (http)



admin.matchups.games
2082
cPanel (http)



admin.matchups.games
2083
cPanel (https)



admin.matchups.games
2083
cPanel (https)



admin.matchups.games
2086
WHM (http)



admin.matchups.games
2086
WHM (http)



admin.matchups.games
2087
WHM (https)



admin.matchups.games
2087
WHM (https)



admin.matchups.games
2089
cPanel Licensing



admin.matchups.games
2089
cPanel Licensing



admin.matchups.games
2095
cPanel Webmail (http)



admin.matchups.games
2095
cPanel Webmail (http)



admin.matchups.games
2096
cPanel Webmail (https)



admin.matchups.games
2096
cPanel Webmail (https)



admin.matchups.games
2222
DirectAdmin (http)



admin.matchups.games
2222
DirectAdmin (http)



admin.matchups.games
2222
DirectAdmin (https)



admin.matchups.games
2222
DirectAdmin (https)



admin.matchups.games
3306
mySql



admin.matchups.games
3306
mySql



admin.matchups.games
5224
Plesk Licensing



admin.matchups.games
5224
Plesk Licensing



admin.matchups.games
5432
PostgreSQL



admin.matchups.games
5432
PostgreSQL



admin.matchups.games
8080
Ookla Speedtest (http)



admin.matchups.games
8080
Ookla Speedtest (http)



admin.matchups.games
8080
Ookla Speedtest (https)



admin.matchups.games
8080
Ookla Speedtest (https)



admin.matchups.games
8083
VestaCP http



admin.matchups.games
8083
VestaCP http



admin.matchups.games
8083
VestaCP https



admin.matchups.games
8083
VestaCP https



admin.matchups.games
8443
Plesk Administration (https)



admin.matchups.games
8443
Plesk Administration (https)



admin.matchups.games
8447
Plesk Installer + Updates



admin.matchups.games
8447
Plesk Installer + Updates



admin.matchups.games
8880
Plesk Administration (http)



admin.matchups.games
8880
Plesk Administration (http)



admin.matchups.games
10000
Webmin (http)



admin.matchups.games
10000
Webmin (http)



admin.matchups.games
10000
Webmin (https)



admin.matchups.games
10000
Webmin (https)



3.20.180.23
21
FTP



3.20.180.23
21
FTP



3.20.180.23
22
SSH
open
SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3

3.20.180.23
22
SSH
open
SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3

3.20.180.23
25
SMTP



3.20.180.23
25
SMTP



3.20.180.23
53
DNS



3.20.180.23
53
DNS



3.20.180.23
110
POP3



3.20.180.23
110
POP3



3.20.180.23
143
IMAP



3.20.180.23
143
IMAP



3.20.180.23
465
SMTP (encrypted)



3.20.180.23
465
SMTP (encrypted)



3.20.180.23
587
SMTP (encrypted, submission)



3.20.180.23
587
SMTP (encrypted, submission)



3.20.180.23
993
IMAP (encrypted)



3.20.180.23
993
IMAP (encrypted)



3.20.180.23
995
POP3 (encrypted)



3.20.180.23
995
POP3 (encrypted)



3.20.180.23
1433
MS SQL



3.20.180.23
1433
MS SQL



3.20.180.23
2082
cPanel (http)



3.20.180.23
2082
cPanel (http)



3.20.180.23
2083
cPanel (https)



3.20.180.23
2083
cPanel (https)



3.20.180.23
2086
WHM (http)



3.20.180.23
2086
WHM (http)



3.20.180.23
2087
WHM (https)



3.20.180.23
2087
WHM (https)



3.20.180.23
2089
cPanel Licensing



3.20.180.23
2089
cPanel Licensing



3.20.180.23
2095
cPanel Webmail (http)



3.20.180.23
2095
cPanel Webmail (http)



3.20.180.23
2096
cPanel Webmail (https)



3.20.180.23
2096
cPanel Webmail (https)



3.20.180.23
2222
DirectAdmin (http)



3.20.180.23
2222
DirectAdmin (http)



3.20.180.23
2222
DirectAdmin (https)



3.20.180.23
2222
DirectAdmin (https)



3.20.180.23
3306
mySql



3.20.180.23
3306
mySql



3.20.180.23
5224
Plesk Licensing



3.20.180.23
5224
Plesk Licensing



3.20.180.23
5432
PostgreSQL



3.20.180.23
5432
PostgreSQL



3.20.180.23
8080
Ookla Speedtest (http)



3.20.180.23
8080
Ookla Speedtest (http)



3.20.180.23
8080
Ookla Speedtest (https)



3.20.180.23
8080
Ookla Speedtest (https)



3.20.180.23
8083
VestaCP http



3.20.180.23
8083
VestaCP http



3.20.180.23
8083
VestaCP https



3.20.180.23
8083
VestaCP https



3.20.180.23
8443
Plesk Administration (https)



3.20.180.23
8443
Plesk Administration (https)



3.20.180.23
8447
Plesk Installer + Updates



3.20.180.23
8447
Plesk Installer + Updates



3.20.180.23
8880
Plesk Administration (http)



3.20.180.23
8880
Plesk Administration (http)



3.20.180.23
10000
Webmin (http)



3.20.180.23
10000
Webmin (http)



3.20.180.23
10000
Webmin (https)



3.20.180.23
10000
Webmin (https)





Permalink: https://check-your-website.server-daten.de/?i=9b680104-bcb6-4c6a-9f5a-f5a5b0c65199


Last Result: https://check-your-website.server-daten.de/?q=admin.matchups.games - 2020-06-02 05:33:57


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

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