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




V

Connect failure - perhaps firewall

Checked:
24.01.2023 23:07:06


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
curaetech.com
A
18.135.245.110
London/England/United Kingdom (GB) - Amazon Technologies Inc.
Hostname: ec2-18-135-245-110.eu-west-2.compute.amazonaws.com
yes
1
0

AAAA
2a05:d01c:43e:8400:5263:37b9:fba0:8fec
London/England/United Kingdom (GB) - Amazon.com, Inc.

yes


www.curaetech.com
A
18.135.245.110
London/England/United Kingdom (GB) - Amazon Technologies Inc.
Hostname: ec2-18-135-245-110.eu-west-2.compute.amazonaws.com
yes
1
0

AAAA
2a05:d01c:43e:8400:5263:37b9:fba0:8fec
London/England/United Kingdom (GB) - Amazon.com, Inc.

yes


*.curaetech.com
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes



2. DNSSEC

Zone (*)DNSSEC - Informations

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



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



Status: Valid because published



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 951, Flags 256



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



1 RRSIG RR to validate DNSKEY RR found



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



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



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

Zone: com
com
1 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 30909, DigestType 2 and Digest 4tPJFvbe6scylOgmj7WIUESoM/xUWViPSpGEz8QaV2Y=



1 RRSIG RR to validate DS RR found



RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 06.02.2023, 17:00:00 +, Signature-Inception: 24.01.2023, 16:00:00 +, KeyTag 951, Signer-Name: (root)



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



2 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 36739, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 04.02.2023, 18:24:21 +, Signature-Inception: 20.01.2023, 18:19:21 +, KeyTag 30909, Signer-Name: com



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



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

Zone: curaetech.com
curaetech.com
1 DS RR in the parent zone found



DS with Algorithm 13, KeyTag 14232, DigestType 2 and Digest kZ4rpcYUOZysytdwaSZI4b/4LapVBzvl05oNvOh8rv8=



1 RRSIG RR to validate DS RR found



RRSIG-Owner curaetech.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 31.01.2023, 05:23:37 +, Signature-Inception: 24.01.2023, 04:13:37 +, KeyTag 36739, Signer-Name: com



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



0 DNSKEY RR found






Fatal error: Parent zone has a signed DS RR (Algorithm 13, KeyTag 14232, DigestType 2, Digest kZ4rpcYUOZysytdwaSZI4b/4LapVBzvl05oNvOh8rv8=), but the destination DNSKEY doesn't exist or doesn't validate the DNSKEY RR set. No chain of trust created.

Zone: www.curaetech.com
www.curaetech.com
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.curaetech.com
  ns-636.awsdns-15.net / 9b0e15bdc161ea053055e43a4acaca4a -

curaetech.com
  ns-1503.awsdns-59.org / 09ce1c1d88db6d4ed06ff56455dd7337 -
205.251.197.223
Dublin/Leinster/Ireland (IE) - Amazon.com


 
2600:9000:5305:df00::1
London/England/United Kingdom (GB) - Amazon.com


  ns-169.awsdns-21.com / 758989b8a91eaa6347c0e27feb0a1605 -
205.251.192.169
Dublin/Leinster/Ireland (IE) - Amazon.com


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


  ns-1753.awsdns-27.co.uk / 860e272172777caa66628af3b2e9568a -
205.251.198.217
Herndon/Virginia/United States (US) - Amazon.com


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


  ns-636.awsdns-15.net / 9b0e15bdc161ea053055e43a4acaca4a -
205.251.194.124
Sterling/Virginia/United States (US) - Amazon.com


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

com
  a.gtld-servers.net / nnn1-fra6


  b.gtld-servers.net / nnn1-elpar7


  c.gtld-servers.net / nnn1-fra6


  d.gtld-servers.net / nnn1-fra6


  e.gtld-servers.net / nnn1-fra6


  f.gtld-servers.net / nnn1-fra5


  g.gtld-servers.net / nnn1-fra5


  h.gtld-servers.net / nnn1-fra5


  i.gtld-servers.net / nnn1-fra5


  j.gtld-servers.net / nnn1-nlams-1c


  k.gtld-servers.net / nnn1-nlams-1a


  l.gtld-servers.net / nnn1-nlams-1d


  m.gtld-servers.net / nnn1-nlams-1c


4. SOA-Entries


Domain:com
Zone-Name:com
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1674597995
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:4


Domain:com
Zone-Name:com
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1674598010
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:9


Domain:curaetech.com
Zone-Name:curaetech.com
Primary:ns-636.awsdns-15.net
Mail:awsdns-hostmaster.amazon.com
Serial:1
Refresh:7200
Retry:900
Expire:1209600
TTL:86400
num Entries:8


Domain:www.curaetech.com
Zone-Name:curaetech.com
Primary:ns-636.awsdns-15.net
Mail:awsdns-hostmaster.amazon.com
Serial:1
Refresh:7200
Retry:900
Expire:1209600
TTL:86400
num Entries:1


5. Screenshots

No Screenshot listed, because no url-check with https + http status 200-299, 400-599 + not-ACME-check found.

6. Url-Checks

DomainnameHttp-StatusredirectSec.G
• http://curaetech.com/
18.135.245.110
-2

1.104
V
ConnectFailure - Unable to connect to the remote server

• http://curaetech.com/
2a05:d01c:43e:8400:5263:37b9:fba0:8fec
-2

1.107
V
ConnectFailure - Unable to connect to the remote server

• http://www.curaetech.com/
18.135.245.110
-2

1.103
V
ConnectFailure - Unable to connect to the remote server

• http://www.curaetech.com/
2a05:d01c:43e:8400:5263:37b9:fba0:8fec
-2

1.120
V
ConnectFailure - Unable to connect to the remote server

• https://curaetech.com/
18.135.245.110
-2

1.110
V
ConnectFailure - Unable to connect to the remote server

• https://curaetech.com/
2a05:d01c:43e:8400:5263:37b9:fba0:8fec
-2

1.080
V
ConnectFailure - Unable to connect to the remote server

• https://www.curaetech.com/
18.135.245.110
-2

1.100
V
ConnectFailure - Unable to connect to the remote server

• https://www.curaetech.com/
2a05:d01c:43e:8400:5263:37b9:fba0:8fec
-2

1.100
V
ConnectFailure - Unable to connect to the remote server

• http://curaetech.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
18.135.245.110
-2

1.103
V
ConnectFailure - Unable to connect to the remote server
Visible Content:

• http://curaetech.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
2a05:d01c:43e:8400:5263:37b9:fba0:8fec
-2

1.103
V
ConnectFailure - Unable to connect to the remote server
Visible Content:

• http://www.curaetech.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
18.135.245.110
-2

1.117
V
ConnectFailure - Unable to connect to the remote server
Visible Content:

• http://www.curaetech.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
2a05:d01c:43e:8400:5263:37b9:fba0:8fec
-2

1.100
V
ConnectFailure - Unable to connect to the remote server
Visible Content:

• https://18.135.245.110/
18.135.245.110
-2

1.083
V
ConnectFailure - Unable to connect to the remote server

• https://[2a05:d01c:043e:8400:5263:37b9:fba0:8fec]/
2a05:d01c:43e:8400:5263:37b9:fba0:8fec
-2

1.097
V
ConnectFailure - Unable to connect to the remote server

7. Comments


1. General Results, most used to calculate the result

Aname "curaetech.com" is domain, public suffix is ".com", top-level-domain is ".com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .com-domains preloaded: 83852 (complete: 216710)
AGood: All ip addresses are public addresses
AGood: Minimal 2 ip addresses per domain name found: curaetech.com has 2 different ip addresses (authoritative).
AGood: Minimal 2 ip addresses per domain name found: www.curaetech.com has 2 different ip addresses (authoritative).
AGood: Ipv4 and Ipv6 addresses per domain name found: curaetech.com has 1 ipv4, 1 ipv6 addresses
AGood: Ipv4 and Ipv6 addresses per domain name found: www.curaetech.com has 1 ipv4, 1 ipv6 addresses
AGood: No asked Authoritative Name Server had a timeout
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
Vhttp://curaetech.com/ 18.135.245.110
-2

Connect failure - perhaps firewall
Vhttp://curaetech.com/ 2a05:d01c:43e:8400:5263:37b9:fba0:8fec
-2

Connect failure - perhaps firewall
Vhttp://www.curaetech.com/ 18.135.245.110
-2

Connect failure - perhaps firewall
Vhttp://www.curaetech.com/ 2a05:d01c:43e:8400:5263:37b9:fba0:8fec
-2

Connect failure - perhaps firewall
Vhttps://curaetech.com/ 18.135.245.110
-2

Connect failure - perhaps firewall
Vhttps://curaetech.com/ 2a05:d01c:43e:8400:5263:37b9:fba0:8fec
-2

Connect failure - perhaps firewall
Vhttps://www.curaetech.com/ 18.135.245.110
-2

Connect failure - perhaps firewall
Vhttps://www.curaetech.com/ 2a05:d01c:43e:8400:5263:37b9:fba0:8fec
-2

Connect failure - perhaps firewall
Vhttp://curaetech.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 18.135.245.110
-2

Connect failure - perhaps firewall
Vhttp://curaetech.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a05:d01c:43e:8400:5263:37b9:fba0:8fec
-2

Connect failure - perhaps firewall
Vhttp://www.curaetech.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 18.135.245.110
-2

Connect failure - perhaps firewall
Vhttp://www.curaetech.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a05:d01c:43e:8400:5263:37b9:fba0:8fec
-2

Connect failure - perhaps firewall
Vhttps://18.135.245.110/ 18.135.245.110
-2

Connect failure - perhaps firewall
Vhttps://[2a05:d01c:043e:8400:5263:37b9:fba0:8fec]/ 2a05:d01c:43e:8400:5263:37b9:fba0:8fec
-2

Connect failure - perhaps firewall
AGood: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain curaetech.com, 2 ip addresses.
AGood: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain www.curaetech.com, 2 ip addresses.
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 curaetech.com, 2 ip addresses.
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 www.curaetech.com, 2 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.curaetech.com

2. Header-Checks (alpha, started 2022-10-23, may be buggy / incomplete)

U

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

3. DNS- and NameServer - Checks

AInfo:: 16 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers.
AInfo:: 16 Queries complete, 16 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
Ok (4 - 8):: An average of 4.0 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 4 different Name Servers found: ns-1503.awsdns-59.org, ns-169.awsdns-21.com, ns-1753.awsdns-27.co.uk, ns-636.awsdns-15.net, 4 Name Servers included in Delegation: ns-1503.awsdns-59.org, ns-169.awsdns-21.com, ns-1753.awsdns-27.co.uk, ns-636.awsdns-15.net, 4 Name Servers included in 1 Zone definitions: ns-1503.awsdns-59.org, ns-169.awsdns-21.com, ns-1753.awsdns-27.co.uk, ns-636.awsdns-15.net, 1 Name Servers listed in SOA.Primary: ns-636.awsdns-15.net.
AGood: Only one SOA.Primary Name Server found.: ns-636.awsdns-15.net.
AGood: SOA.Primary Name Server included in the delegation set.: ns-636.awsdns-15.net.
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: ns-1503.awsdns-59.org, ns-169.awsdns-21.com, ns-1753.awsdns-27.co.uk, ns-636.awsdns-15.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: 4 different Name Servers found
AGood: All name servers have ipv4- and ipv6-addresses.: 4 different Name Servers found
AGood: Name servers with different Top Level Domains / Public Suffix List entries found: 4 Name Servers, 4 Top Level Domains: org, net, com, co.uk
AGood: Name Servers with different domain names found.: 4 different Domains found
AGood: Name servers with different Country locations found: 4 Name Servers, 3 Countries: GB, IE, US
AInfo: Ipv4-Subnet-list: 4 Name Servers, 1 different subnets (first Byte): 205., 1 different subnets (first two Bytes): 205.251., 4 different subnets (first three Bytes): 205.251.192., 205.251.194., 205.251.197., 205.251.198.
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:5300:, 2600:9000:5302:, 2600:9000:5305:, 2600:9000:5306:, 4 different subnets (first four blocks): 2600:9000:5300:a900:, 2600:9000:5302:7c00:, 2600:9000:5305:df00:, 2600:9000:5306:d900:
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 8 good Nameserver
AGood: Nameserver supports Echo Capitalization: 8 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 8 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 8 good Nameserver
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

http://curaetech.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 18.135.245.110
-2

Fatal: Check of /.well-known/acme-challenge/random-filename is blocked, http connection error. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
http://curaetech.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a05:d01c:43e:8400:5263:37b9:fba0:8fec
-2

Fatal: Check of /.well-known/acme-challenge/random-filename is blocked, http connection error. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
http://www.curaetech.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 18.135.245.110
-2

Fatal: Check of /.well-known/acme-challenge/random-filename is blocked, http connection error. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
http://www.curaetech.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2a05:d01c:43e:8400:5263:37b9:fba0:8fec
-2

Fatal: Check of /.well-known/acme-challenge/random-filename is blocked, http connection error. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
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: 114247 milliseconds, 114.247 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)

Issuerlast 7 daysactivenum Certs
CN=Sectigo RSA Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, C=GB, ST=Greater Manchester
0
1
1
CN=R3, O=Let's Encrypt, C=US
0
1
1

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
4721077159
leaf cert
CN=Sectigo RSA Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, C=GB, ST=Greater Manchester
2023-01-23 00:00:00
2024-02-23 23:59:59
curaetech.com, www.curaetech.com - 2 entries


4515012261
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-12-06 10:48:51
2023-03-06 10:48:50
*.curaetech.com, curaetech.com - 2 entries



2. Source crt.sh - old and new certificates, sometimes very slow - only certificates with "not after" > of the last months are listed

Issuerlast 7 daysactivenum Certs
CN=R3, O=Let's Encrypt, C=US
0 /0 new
1
8
CN=Sectigo RSA Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, C=GB, ST=Greater Manchester
0
1
1

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
8478440343
leaf cert
CN=Sectigo RSA Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, C=GB, ST=Greater Manchester
2023-01-22 23:00:00
2024-02-23 22:59:59
curaetech.com, www.curaetech.com
2 entries


8155034845
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-12-06 09:48:51
2023-03-06 09:48:50
*.curaetech.com, curaetech.com
2 entries


7709328848
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-10-06 08:48:39
2023-01-04 09:48:38
*.curaetech.com, curaetech.com
2 entries


7281163457
precert
CN=R3, O=Let's Encrypt, C=US
2022-08-06 09:48:30
2022-11-04 10:48:29
*.curaetech.com, curaetech.com
2 entries


6880362677
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-06-06 09:48:18
2022-09-04 09:48:17
*.curaetech.com, curaetech.com
2 entries


6489068149
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-04-06 09:48:07
2022-07-05 09:48:06
*.curaetech.com, curaetech.com
2 entries


6121238151
leaf cert
CN=R3, O=Let's Encrypt, C=US
2022-02-04 10:47:55
2022-05-05 09:47:54
*.curaetech.com, curaetech.com
2 entries


5741251066
leaf cert
CN=R3, O=Let's Encrypt, C=US
2021-12-05 10:47:40
2022-03-05 10:47:39
*.curaetech.com, curaetech.com
2 entries


5359731970
leaf cert
CN=R3, O=Let's Encrypt, C=US
2021-10-05 09:47:27
2022-01-03 10:47:26
*.curaetech.com, curaetech.com
2 entries



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: ns-1503.awsdns-59.org, ns-169.awsdns-21.com, ns-1753.awsdns-27.co.uk, ns-636.awsdns-15.net

QNr.DomainTypeNS used
1
org
NS
a.root-servers.net (2001:503:ba3e::2:30)

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
2
ns-1503.awsdns-59.org
NS
a0.org.afilias-nst.info (2001:500:e::1)

Answer: g-ns-1086.awsdns-59.org, g-ns-1659.awsdns-59.org, g-ns-187.awsdns-59.org, g-ns-765.awsdns-59.org

Answer: g-ns-1086.awsdns-59.org
205.251.196.62, 2600:9000:5304:3e00::1

Answer: g-ns-1659.awsdns-59.org
205.251.198.123, 2600:9000:5306:7b00::1

Answer: g-ns-187.awsdns-59.org
205.251.192.187, 2600:9000:5300:bb00::1

Answer: g-ns-765.awsdns-59.org
205.251.194.253, 2600:9000:5302:fd00::1
3
com
NS
a.root-servers.net (2001:503:ba3e::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
4
ns-169.awsdns-21.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: g-ns-1173.awsdns-21.com, g-ns-1749.awsdns-21.com, g-ns-22.awsdns-21.com, g-ns-597.awsdns-21.com

Answer: g-ns-1173.awsdns-21.com
205.251.196.149, 2600:9000:5304:9500::1

Answer: g-ns-1749.awsdns-21.com
205.251.198.213, 2600:9000:5306:d500::1

Answer: g-ns-22.awsdns-21.com
205.251.192.22, 2600:9000:5300:1600::1

Answer: g-ns-597.awsdns-21.com
205.251.194.85, 2600:9000:5302:5500::1
5
uk
NS
m.root-servers.net (2001:dc3::35)

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-1753.awsdns-27.co.uk
NS
dns1.nic.uk (2a01:618:400::1)

Answer: g-ns-1502.awsdns-27.co.uk, g-ns-1823.awsdns-27.co.uk, g-ns-347.awsdns-27.co.uk, g-ns-923.awsdns-27.co.uk

Answer: g-ns-1502.awsdns-27.co.uk
205.251.197.222, 2600:9000:5305:de00::1

Answer: g-ns-1823.awsdns-27.co.uk
205.251.199.31, 2600:9000:5307:1f00::1

Answer: g-ns-347.awsdns-27.co.uk
205.251.193.91, 2600:9000:5301:5b00::1

Answer: g-ns-923.awsdns-27.co.uk
205.251.195.155, 2600:9000:5303:9b00::1
7
net
NS
k.root-servers.net (2001:7fd::1)

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

Answer: g-ns-1359.awsdns-15.net, g-ns-1935.awsdns-15.net, g-ns-464.awsdns-15.net, g-ns-785.awsdns-15.net

Answer: g-ns-1359.awsdns-15.net
205.251.197.79, 2600:9000:5305:4f00::1

Answer: g-ns-1935.awsdns-15.net
205.251.199.143, 2600:9000:5307:8f00::1

Answer: g-ns-464.awsdns-15.net
205.251.193.208, 2600:9000:5301:d000::1

Answer: g-ns-785.awsdns-15.net
205.251.195.17, 2600:9000:5303:1100::1
9
ns-1503.awsdns-59.org: 205.251.197.223
A
g-ns-1086.awsdns-59.org (2600:9000:5304:3e00::1)
10
ns-1503.awsdns-59.org: 2600:9000:5305:df00::1
AAAA
g-ns-1086.awsdns-59.org (2600:9000:5304:3e00::1)
11
ns-169.awsdns-21.com: 205.251.192.169
A
g-ns-1173.awsdns-21.com (2600:9000:5304:9500::1)
12
ns-169.awsdns-21.com: 2600:9000:5300:a900::1
AAAA
g-ns-1173.awsdns-21.com (2600:9000:5304:9500::1)
13
ns-1753.awsdns-27.co.uk: 205.251.198.217
A
g-ns-1502.awsdns-27.co.uk (2600:9000:5305:de00::1)
14
ns-1753.awsdns-27.co.uk: 2600:9000:5306:d900::1
AAAA
g-ns-1502.awsdns-27.co.uk (2600:9000:5305:de00::1)
15
ns-636.awsdns-15.net: 205.251.194.124
A
g-ns-1359.awsdns-15.net (2600:9000:5305:4f00::1)
16
ns-636.awsdns-15.net: 2600:9000:5302:7c00::1
AAAA
g-ns-1359.awsdns-15.net (2600:9000:5305:4f00::1)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.curaetech.com
0

no CAA entry found
1
0
curaetech.com
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
curaetech.com
MS=ms21844062
ok
1
0
curaetech.com
v=spf1 include:spf.protection.outlook.com -all
ok
1
0
www.curaetech.com

ok
1
0
_acme-challenge.curaetech.com

Name Error - The domain name does not exist
1
0
_acme-challenge.www.curaetech.com

Name Error - The domain name does not exist
1
0
_acme-challenge.curaetech.com.curaetech.com

Name Error - The domain name does not exist
1
0
_acme-challenge.www.curaetech.com.curaetech.com

Name Error - The domain name does not exist
1
0
_acme-challenge.www.curaetech.com.www.curaetech.com

Name Error - The domain name does not exist
1
0


15. DomainService - Entries (SSHFP Check is new - 2022-09-24, may be incomplete, alpha, some results are required)

TypeDomainPrefValueDNS-errornum AnswersStatusDescription
MX

curaetech.com
0
curaetech-com.mail.protection.outlook.com
0
1
ok


A


104.47.20.36
0
1
ok


CNAME



-4
0
ok



16. Cipher Suites

No results


17. Portchecks

No open Ports <> 80 / 443 found, so no additional Ports checked.



Permalink: https://check-your-website.server-daten.de/?i=53abad19-c0b0-4541-ba5e-75ecab5fcaf0


Last Result: https://check-your-website.server-daten.de/?q=curaetech.com - 2023-01-24 23:07:06


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

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

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