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




V

Connect failure - perhaps firewall

Checked:
11.06.2024 14:25:37


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
odontoapp.com.co
A
44.198.51.181
Ashburn/Virginia/United States (US) - Amazon.com
Hostname: ec2-44-198-51-181.compute-1.amazonaws.com
yes
2
0

AAAA

yes


www.odontoapp.com.co
CNAME
odontoapp.com.co
yes
1
0

A
44.198.51.181
Ashburn/Virginia/United States (US) - Amazon.com
Hostname: ec2-44-198-51-181.compute-1.amazonaws.com
yes


*.odontoapp.com.co
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 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: co
co
1 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 62110, DigestType 2 and Digest SFfuGoXmYckhVq0JtAE52ufVvjfRF6EiMonw4gz51lQ=



1 RRSIG RR to validate DS RR found



RRSIG-Owner co., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 24.06.2024, 05:00:00 +, Signature-Inception: 11.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



3 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 19065, Flags 256



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



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



2 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner co., Algorithm: 8, 1 Labels, original TTL: 7200 sec, Signature-expiration: 10.07.2024, 05:08:31 +, Signature-Inception: 10.06.2024, 04:52:30 +, KeyTag 19065, Signer-Name: co



RRSIG-Owner co., Algorithm: 8, 1 Labels, original TTL: 7200 sec, Signature-expiration: 10.07.2024, 05:08:31 +, Signature-Inception: 10.06.2024, 04:52:30 +, KeyTag 62110, Signer-Name: co



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



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



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

Zone: com.co
com.co
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 "dn7griesdhut72a80dgfb9vvppvvi080" between the hashed NSEC3-owner "dn7griesdhut72a80dgfb9vvppvvi080" and the hashed NextOwner "dn7haqknbt064mpbhfbc37r5clegfqfi". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: No Bitmap? Validated: RRSIG-Owner dn7griesdhut72a80dgfb9vvppvvi080.co., Algorithm: 8, 2 Labels, original TTL: 900 sec, Signature-expiration: 10.07.2024, 10:10:02 +, Signature-Inception: 10.06.2024, 09:23:12 +, KeyTag 19065, Signer-Name: co



0 DNSKEY RR found




Zone: odontoapp.com.co
odontoapp.com.co
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 "uia5muvrqgi8hlfrbmnbo92bhbob1tli" between the hashed NSEC3-owner "uia0u80mfmfq12lohlhkli8ciervv1nk" and the hashed NextOwner "uia6a7419clnfmtvis3g67mtvejvtotc". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner uia0u80mfmfq12lohlhkli8ciervv1nk.co., Algorithm: 8, 2 Labels, original TTL: 900 sec, Signature-expiration: 07.07.2024, 08:59:21 +, Signature-Inception: 07.06.2024, 08:38:36 +, KeyTag 19065, Signer-Name: co



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "dn7griesdhut72a80dgfb9vvppvvi080" as Owner. That's the Hash of "com.co" with the NextHashedOwnerName "dn7haqknbt064mpbhfbc37r5clegfqfi". So that domain name is the Closest Encloser of "odontoapp.com.co". Opt-Out: True.
Bitmap: No Bitmap? Validated: RRSIG-Owner dn7griesdhut72a80dgfb9vvppvvi080.co., Algorithm: 8, 2 Labels, original TTL: 900 sec, Signature-expiration: 10.07.2024, 10:10:02 +, Signature-Inception: 10.06.2024, 09:23:12 +, KeyTag 19065, Signer-Name: co



0 DNSKEY RR found




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


3. Name Servers

DomainNameserverNS-IP
odontoapp.com.co
  ns1.dns-parking.com / 67m75
162.159.24.201
Toronto/Ontario/Canada (CA) - Cloudflare, Inc.


 
2400:cb00:2049:1::a29f:18c9
San Francisco/California/United States (US) - CLOUDFLARE


  ns2.dns-parking.com / 67m43
162.159.25.42
Toronto/Ontario/Canada (CA) - Cloudflare, Inc.


 
2400:cb00:2049:1::a29f:192a
San Francisco/California/United States (US) - CLOUDFLARE

com.co
  ns1.cctld.co / dns4.defra1
37.209.192.14
Melbourne/Victoria/Australia (AU) - NeuStar, Inc.


 
2001:dcd:1::14
Melbourne/Victoria/Australia (AU) - NeuStar, Inc.

co
  ns1.cctld.co / dns2.defra1


  ns2.cctld.co / dns4.defra1


  ns3.cctld.co / dns2.defra1


  ns4.cctld.co / TLD_Host2.Frankfurt_Node1


  ns5.cctld.co / TLD_Host2.Frankfurt_Node1


  ns6.cctld.co / TLD_Host1.Frankfurt_Node1


4. SOA-Entries


Domain:co
Zone-Name:co
Primary:ns1.cctld.co
Mail:admin.tldns.godaddy
Serial:1718108022
Refresh:1800
Retry:300
Expire:604800
TTL:1800
num Entries:6


Domain:com.co
Zone-Name:co
Primary:ns1.cctld.co
Mail:admin.tldns.godaddy
Serial:1718108022
Refresh:1800
Retry:300
Expire:604800
TTL:1800
num Entries:2


Domain:odontoapp.com.co
Zone-Name:odontoapp.com.co
Primary:ns1.dns-parking.com
Mail:dns.hostinger.com
Serial:2024061104
Refresh:10000
Retry:2400
Expire:604800
TTL:600
num Entries:4


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://odontoapp.com.co/
44.198.51.181 GZip used - 307 / 496 - 38.10 %
200

Html is minified: 111.71 %
0.234
H
Server: nginx/1.24.0, (Ubuntu)
Date: Tue, 11 Jun 2024 12:26:12 GMT
Transfer-Encoding: chunked
Connection: close
ETag: W/"637e47ba59ebf9d4e27fc9b913d9951c7c5ae20f"
Vary: Accept-Encoding
Content-Type: text/html; charset=utf-8
Content-Disposition: inline; filename="index.html"
Content-Encoding: gzip

• http://www.odontoapp.com.co/
44.198.51.181 GZip used - 307 / 496 - 38.10 %
200

Html is minified: 111.71 %
0.230
H
Server: nginx/1.24.0, (Ubuntu)
Date: Tue, 11 Jun 2024 12:26:12 GMT
Transfer-Encoding: chunked
Connection: close
ETag: W/"637e47ba59ebf9d4e27fc9b913d9951c7c5ae20f"
Vary: Accept-Encoding
Content-Type: text/html; charset=utf-8
Content-Disposition: inline; filename="index.html"
Content-Encoding: gzip

• https://odontoapp.com.co/
44.198.51.181
-16

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

• https://www.odontoapp.com.co/
44.198.51.181
-16

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

• http://odontoapp.com.co/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
44.198.51.181 GZip used - 123 / 162 - 24.07 %
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
404

Html is minified: 109.46 %
0.234
A
Not Found
Visible Content:
Server: nginx/1.24.0, (Ubuntu)
Date: Tue, 11 Jun 2024 12:26:15 GMT
Transfer-Encoding: chunked
Connection: close
Content-Type: text/html
Content-Encoding: gzip

• http://www.odontoapp.com.co/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
44.198.51.181 GZip used - 123 / 162 - 24.07 %
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
404

Html is minified: 109.46 %
0.223
A
Not Found
Visible Content:
Server: nginx/1.24.0, (Ubuntu)
Date: Tue, 11 Jun 2024 12:26:15 GMT
Transfer-Encoding: chunked
Connection: close
Content-Type: text/html
Content-Encoding: gzip

• https://44.198.51.181/
44.198.51.181
-16

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

7. Comments


1. General Results, most used to calculate the result

Aname "odontoapp.com.co" is domain, public suffix is ".com.co", top-level-domain is ".co", top-level-domain-type is "country-code", Country is Colombia, tld-manager is ".CO Internet S.A.S.", num .co-domains preloaded: 2090 (complete: 245733)
AGood: All ip addresses are public addresses
Warning: Only one ip address found: odontoapp.com.co has only one ip address.
Warning: Only one ip address found: www.odontoapp.com.co 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: odontoapp.com.co has no ipv6 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: www.odontoapp.com.co has no ipv6 address.
AGood: No asked Authoritative Name Server had a timeout
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: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):2 complete Content-Type - header (4 urls)
http://odontoapp.com.co/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 44.198.51.181


Url with incomplete Content-Type - header - missing charset
http://www.odontoapp.com.co/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 44.198.51.181


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.
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 odontoapp.com.co, 1 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.odontoapp.com.co, 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.odontoapp.com.co

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:: 2 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
AInfo:: 2 Queries complete, 2 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
AGood: Some ip addresses of name servers found with the minimum of two DNS Queries. One to find the TLD-Zone, one to ask the TLD-Zone.ns1.dns-parking.com (162.159.24.201, 2400:cb00:2049:1::a29f:18c9), ns2.dns-parking.com (162.159.25.42, 2400:cb00:2049:1::a29f:192a)
AGood (1 - 3.0):: An average of 1.0 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 2 different Name Servers found: ns1.dns-parking.com, ns2.dns-parking.com, 2 Name Servers included in Delegation: ns1.dns-parking.com, ns2.dns-parking.com, 2 Name Servers included in 1 Zone definitions: ns1.dns-parking.com, ns2.dns-parking.com, 1 Name Servers listed in SOA.Primary: ns1.dns-parking.com.
AGood: Only one SOA.Primary Name Server found.: ns1.dns-parking.com.
AGood: SOA.Primary Name Server included in the delegation set.: ns1.dns-parking.com.
AGood: Consistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Ordered list of name servers: ns1.dns-parking.com, ns2.dns-parking.com
AGood: All Name Server Domain Names have a Public Suffix.
AGood: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
AGood: All Name Server ip addresses are public.
AGood: Minimal 2 different name servers (public suffix and public ip address) found: 2 different Name Servers found
AGood: All name servers have ipv4- and ipv6-addresses.: 2 different Name Servers found
Warning: All Name Servers have the same Top Level Domain / Public Suffix. If there is a problem with that Top Level Domain, your domain may be affected. Better: Use Name Servers with different top level domains.: 2 Name Servers, 1 Top Level Domain: com
Warning: All Name Servers have the same domain name. If there is a problem with that domain name (or with the name servers of that domain name), your domain may be affected. Better: Use Name Servers with different domain names / different top level domains.: Only one domain name used: dns-parking.com
AGood: Name servers with different Country locations found: 2 Name Servers, 2 Countries: CA, US
AInfo: Ipv4-Subnet-list: 2 Name Servers, 1 different subnets (first Byte): 162., 1 different subnets (first two Bytes): 162.159., 2 different subnets (first three Bytes): 162.159.24., 162.159.25.
AGood: Name Server IPv4-addresses from different subnet found:
AInfo: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2400:, 1 different subnets (first two blocks): 2400:cb00:, 1 different subnets (first three blocks): 2400:cb00:2049:, 1 different subnets (first four blocks): 2400:cb00:2049:0001:
Fatal: All Name Server IPv6 addresses from the same subnet.
AGood: Nameserver supports TCP connections: 4 good Nameserver
AGood: Nameserver supports Echo Capitalization: 4 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 4 good Nameserver
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: ns1.dns-parking.com / 162.159.24.201: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok (67m75). COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns2.dns-parking.com / 162.159.25.42: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok (67m43). COOKIE: ok. CLIENTSUBNET: ok.
AGood: All SOA have the same Serial Number
AGood: CAA entries found, creating certificate is limited: comodoca.com is allowed to create certificates
AGood: CAA entries found, creating certificate is limited: digicert.com is allowed to create certificates
AGood: CAA entries found, creating certificate is limited: globalsign.com is allowed to create certificates
AGood: CAA entries found, creating certificate is limited: letsencrypt.org is allowed to create certificates
AGood: CAA entries found, creating certificate is limited: pki.goog is allowed to create certificates
AGood: CAA entries found, creating certificate is limited: comodoca.com is allowed to create wildcard-certificates
AGood: CAA entries found, creating certificate is limited: digicert.com is allowed to create wildcard-certificates
AGood: CAA entries found, creating certificate is limited: globalsign.com is allowed to create wildcard-certificates
AGood: CAA entries found, creating certificate is limited: letsencrypt.org is allowed to create wildcard-certificates
AGood: CAA entries found, creating certificate is limited: pki.goog is allowed to create wildcard-certificates

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: 76473 milliseconds, 76.473 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.dns-parking.com, ns2.dns-parking.com

QNr.DomainTypeNS used
1
com
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
2
ns1.dns-parking.com: 162.159.24.201, 2400:cb00:2049:1::a29f:18c9
NS
e.gtld-servers.net (2001:502:1ca1::30)

Answer: ns2.dns-parking.com
162.159.25.42, 2400:cb00:2049:1::a29f:192a


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.odontoapp.com.co
5
issue
comodoca.com
1
0

9
issuewild
comodoca.com
1
0

5
issue
digicert.com
1
0

9
issuewild
digicert.com
1
0

5
issue
globalsign.com
1
0

9
issuewild
globalsign.com
1
0

5
issue
letsencrypt.org
1
0

9
issuewild
letsencrypt.org
1
0

5
issue
pki.goog
1
0

9
issuewild
pki.goog
1
0
odontoapp.com.co
5
issue
comodoca.com
1
0

9
issuewild
comodoca.com
1
0

5
issue
digicert.com
1
0

9
issuewild
digicert.com
1
0

5
issue
globalsign.com
1
0

9
issuewild
globalsign.com
1
0

5
issue
letsencrypt.org
1
0

9
issuewild
letsencrypt.org
1
0

5
issue
pki.goog
1
0

9
issuewild
pki.goog
1
0
com.co
0

no CAA entry found
1
0
co
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
odontoapp.com.co

ok
1
0
www.odontoapp.com.co


1
0
_acme-challenge.odontoapp.com.co

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

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

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

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

Name Error - The domain name does not exist
1
0


15. DomainService - Entries

No DomainServiceEntries entries found



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=8b04e15c-af75-41c1-8143-2d8e04820c99


Last Result: https://check-your-website.server-daten.de/?q=odontoapp.com.co - 2024-06-11 14:25:37


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

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

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