4 replies

Understanding custom hostnames API

I'm using cloudflare for SaaS custom hostnames API. Customs will connect their own domain to my website builder using API. However for some domains ( I tried 3 different domains ) from Namecheap SSL does not seem to work for me.

A crime scene

https://www.nslookup.io/domains/www.aidiscounts.site/dns-records/

 curl -v https://www.aidiscounts.site                                                                                                                    
...
< HTTP/1.1 200 Connection established
<
* Proxy replied 200 to CONNECT request
* CONNECT phase completed
* ALPN: offers h2
* ALPN: offers http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS alert, handshake failure (552):
* error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure
* Closing connection 0
curl: (35) error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure

 curl -v https://www.aidiscounts.site                                                                                                                    
...
< HTTP/1.1 200 Connection established
<
* Proxy replied 200 to CONNECT request
* CONNECT phase completed
* ALPN: offers h2
* ALPN: offers http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS alert, handshake failure (552):
* error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure
* Closing connection 0
curl: (35) error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure

The API ( https://developers.cloudflare.com/api/resources/custom_hostnames/methods/get/ ) response

{
    "id": "...",
    "hostname": "www.aidiscounts.site",
    "ssl": {
        "id": "80734efa-9634-...",
        "type": "dv",
        "method": "txt",
        "status": "pending_validation"
    },
    "status": "active",
    "created_at": "..."
}

{
    "id": "...",
    "hostname": "www.aidiscounts.site",
    "ssl": {
        "id": "80734efa-9634-...",
        "type": "dv",
        "method": "txt",
        "status": "pending_validation"
    },
    "status": "active",
    "created_at": "..."
}

My questions

1. I found "_cf-custom-hostname" in API result.data.ownership_verification https://developers.cloudflare.com/api/resources/custom_hostnames/methods/get/ . According to https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/realtime-validation/ this is optional if I don't care about down time. Am I correct?
2. I found

DCV Delegation for Custom Hostnames

DCV Delegation for Custom Hostnames

in my custom hostnames dashboard for

unproxied or wildcard hostnames

unproxied or wildcard hostnames

. Does this mean I should force my customers to set this record, if

unproxied

unproxied

means domains not bought on cloudflare or proxied on cloudflare?

Cloudflare API | Custom Hostnames › Custom Hostname Details

Interact with Cloudflare's products and services via the Cloudflare API

Cloudflare Docs

Real-time validation

When you use a real-time validation method, Cloudflare verifies your customer's hostname when your customers adds their DNS routing record to their authoritative DNS.

Cloudflare Developers•5mo ago•

4 replies

mrbirddev

Understanding custom hostnames API

A crime scene

https://www.nslookup.io/domains/www.aidiscounts.site/dns-records/

 curl -v https://www.aidiscounts.site                                                                                                                    
...
< HTTP/1.1 200 Connection established
<
* Proxy replied 200 to CONNECT request
* CONNECT phase completed
* ALPN: offers h2
* ALPN: offers http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS alert, handshake failure (552):
* error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure
* Closing connection 0
curl: (35) error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure

 curl -v https://www.aidiscounts.site                                                                                                                    
...
< HTTP/1.1 200 Connection established
<
* Proxy replied 200 to CONNECT request
* CONNECT phase completed
* ALPN: offers h2
* ALPN: offers http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS alert, handshake failure (552):
* error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure
* Closing connection 0
curl: (35) error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure

The API ( https://developers.cloudflare.com/api/resources/custom_hostnames/methods/get/ ) response

{
    "id": "...",
    "hostname": "www.aidiscounts.site",
    "ssl": {
        "id": "80734efa-9634-...",
        "type": "dv",
        "method": "txt",
        "status": "pending_validation"
    },
    "status": "active",
    "created_at": "..."
}

{
    "id": "...",
    "hostname": "www.aidiscounts.site",
    "ssl": {
        "id": "80734efa-9634-...",
        "type": "dv",
        "method": "txt",
        "status": "pending_validation"
    },
    "status": "active",
    "created_at": "..."
}

My questions

DCV Delegation for Custom Hostnames

DCV Delegation for Custom Hostnames

in my custom hostnames dashboard for

unproxied or wildcard hostnames

unproxied or wildcard hostnames

. Does this mean I should force my customers to set this record, if

unproxied

unproxied

means domains not bought on cloudflare or proxied on cloudflare?

Cloudflare API | Custom Hostnames › Custom Hostname Details

Interact with Cloudflare's products and services via the Cloudflare API

Cloudflare Docs

Real-time validation

When you use a real-time validation method, Cloudflare verifies your customer's hostname when your customers adds their DNS routing record to their authoritative DNS.

Understanding custom hostnames API

A crime scene

My questions

Understanding custom hostnames API

A crime scene

My questions

Similar Threads

Similar Threads

Similar Threads