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


 

 

X

 

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

 

Checked:
12.02.2025 13:11:36

 

Older results

 

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
cdncf.site
A

yes
1
0

AAAA

yes


www.cdncf.site
A

yes
1
0

AAAA

yes


*.cdncf.site
A

yes



AAAA

yes



CNAME

yes


 

2. DNSSEC

Zone (*)DNSSEC - Informations


Zone: (root)

(root)
1 DS RR published






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






Status: Valid because published






3 DNSKEY RR found






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






Public Key with Algorithm 8, KeyTag 26470, Flags 256






Public Key with Algorithm 8, KeyTag 38696, 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: 03.03.2025, 00:00:00 +, Signature-Inception: 10.02.2025, 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: site

site
2 DS RR in the parent zone found






DS with Algorithm 8, KeyTag 51676, DigestType 2 and Digest iDF19vXGjqgVY7YtGyt5tqmX1g3G4gzHCv0M1rfoL2I=






DS with Algorithm 8, KeyTag 51974, DigestType 2 and Digest oG3EdFfMEYXPGzp89uzLhJeN6Sk53Rgr7tlSFQnQ2ns=






1 RRSIG RR to validate DS RR found






RRSIG-Owner site., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 25.02.2025, 05:00:00 +, Signature-Inception: 12.02.2025, 04:00:00 +, KeyTag 26470, Signer-Name: (root)






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






2 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 24654, Flags 256






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






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner site., Algorithm: 8, 1 Labels, original TTL: 3600 sec, Signature-expiration: 08.03.2025, 10:30:00 +, Signature-Inception: 06.02.2025, 09:00:00 +, KeyTag 51974, Signer-Name: site






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






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



Zone: cdncf.site

cdncf.site
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 "id6i9iuja1r8ho1n7h5lmle6e4hmjbu8" between the hashed NSEC3-owner "id4d0kvhrlr1hbe73ehs9o5rb1l5p7d6" and the hashed NextOwner "id6mon2ph6o2jp0jjb4kimdl85vh5maa". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner id4d0kvhrlr1hbe73ehs9o5rb1l5p7d6.site., Algorithm: 8, 2 Labels, original TTL: 900 sec, Signature-expiration: 08.03.2025, 10:30:00 +, Signature-Inception: 06.02.2025, 09:00:00 +, KeyTag 24654, Signer-Name: site






DS-Query in the parent zone sends valid NSEC3 RR with the Hash "kkkldpnn5k2662ei72hm1tvtee3uakea" as Owner. That's the Hash of "site" with the NextHashedOwnerName "kkletpllcs8l9v4016d5lhccgrim8hq6". So that domain name is the Closest Encloser of "cdncf.site". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner kkkldpnn5k2662ei72hm1tvtee3uakea.site., Algorithm: 8, 2 Labels, original TTL: 900 sec, Signature-expiration: 08.03.2025, 10:30:00 +, Signature-Inception: 06.02.2025, 09:00:00 +, KeyTag 24654, Signer-Name: site






0 DNSKEY RR found









Zone: www.cdncf.site

www.cdncf.site
0 DS RR in the parent zone found

 

3. Name Servers

DomainNameserverNS-IP
www.cdncf.site
  ns1.platformcraft.ru / 185e41a3f0ff

cdncf.site
  ns1.platformcraft.ru


  ns2.platformcraft.com
5.188.121.99
Moscow/Russia (RU) - EdgeCenter LLC

site
  a.nic.site / SFQY-BG7AF9-XTW0MS


  b.nic.site / PDUS-VJ5JVS-CTI2KM


  e.nic.site / SFQY-BG7AF9-XTW0MS


  f.nic.site / PDUS-VJ5JVS-CTI2KM


  ns0.centralnic.net

 

4. SOA-Entries


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


Domain:site
Zone-Name:site
Primary:ns0.centralnic.net
Mail:hostmaster.centralnic.net
Serial:395255
Refresh:900
Retry:1800
Expire:6048000
TTL:3600
num Entries:4


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


Domain:cdncf.site
Zone-Name:cdncf.site
Primary:ns1.platformcraft.ru
Mail:care@platformcraft.ru
Serial:1739361857
Refresh:7200
Retry:900
Expire:1209600
TTL:86400
num Entries:1


Domain:www.cdncf.site
Zone-Name:cdncf.site
Primary:ns1.platformcraft.ru
Mail:care@platformcraft.ru
Serial:1739361857
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








 

7. Comments


1. General Results, most used to calculate the result

Aname "cdncf.site" is domain, public suffix is ".site", top-level-domain is ".site", top-level-domain-type is "generic", tld-manager is "DotSite Inc.", num .site-domains preloaded: 332 (complete: 263653)
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.
AGood: _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Domainname: _mta-sts.cdncf.site
BBad: _mta-sts TXT found, but invalid

2. Header-Checks

U

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

3. DNS- and NameServer - Checks

AInfo:: 29 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 1 Name Servers.
AInfo:: 29 Queries complete, 29 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
Bad (greater 8):: An average of 29.0 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 2 different Name Servers found: ns1.platformcraft.ru, ns2.platformcraft.com, 2 Name Servers included in Delegation: ns1.platformcraft.ru, ns2.platformcraft.com, 2 Name Servers included in 2 Zone definitions: ns1.platformcraft.ru, ns2.platformcraft.com, 1 Name Servers listed in SOA.Primary: ns1.platformcraft.ru.
AGood: Only one SOA.Primary Name Server found.: ns1.platformcraft.ru.
AGood: SOA.Primary Name Server included in the delegation set.: ns1.platformcraft.ru.
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.platformcraft.ru, ns2.platformcraft.com
AGood: All Name Server Domain Names have a Public Suffix.
Error: Name Server Domain Names with Public Suffix and without ip address found.: 1 Name Servers without ipv4 and ipv6: 1

Warning: No Name Server IPv6 address found. IPv6 is the future, so your name servers should be visible via IPv6.: 1 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.: 1 Name Servers, 1 Top Level Domain: com
AGood: Name Servers with different domain names found.: 2 different Domains found
Warning: All Name Servers from the same Country / IP location.: 1 Name Servers, 1 Countries: RU
AInfo: Ipv4-Subnet-list: 1 Name Servers, 1 different subnets (first Byte): 5., 1 different subnets (first two Bytes): 5.188., 1 different subnets (first three Bytes): 5.188.121.
XFatal: All Name Server IPv4 addresses from the same subnet. Check https://www.iana.org/help/nameserver-requirements to learn some basics about name server configurations. If you manage these name servers, fix it. If it's your provider, change your provider.:
XFatal: Only one Name Server IPv4 address found. Check https://www.iana.org/help/nameserver-requirements to learn some basics about name server configurations. If you manage these name servers, fix it. If it's your provider, change your provider.
AGood: Nameserver supports TCP connections: 1 good Nameserver
AGood: Nameserver supports Echo Capitalization: 1 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 1 good Nameserver
Nameserver doesn't pass all EDNS-Checks: a.nic.site: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (SFQY-BG7AF9-XTW0MS). COOKIE: SOA expected, but NOT found, NOERR expected, BADVER found, Version 0 expectend and found. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: e.nic.site: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (SFQY-BG7AF9-XTW0MS). COOKIE: SOA expected, but NOT found, NOERR expected, BADVER found, Version 0 expectend and found. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns0.centralnic.net: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
Nameserver doesn't pass all EDNS-Checks: ns1.platformcraft.ru: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
Nameserver doesn't pass all EDNS-Checks: ns2.platformcraft.com / 5.188.121.99: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: fatal timeout. COOKIE: ok. CLIENTSUBNET: ok.
AGood: All SOA have the same Serial Number
Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries.

4. Content- and Performance-critical Checks

AGood: 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: 64423 milliseconds, 64.423 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=R11, O=Let's Encrypt, C=US
0
7
7
CN=R10, O=Let's Encrypt, C=US
0
4
4

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
9485468780
leaf cert
CN=R11, O=Let's Encrypt, C=US
2025-02-12 09:14:49
2025-05-13 09:14:48
cdncf.site - 1 entries


9419304176
leaf cert
CN=R10, O=Let's Encrypt, C=US
2025-02-05 16:32:04
2025-05-06 16:32:03
cdncf.site - 1 entries


9410839118
leaf cert
CN=R10, O=Let's Encrypt, C=US
2025-02-04 19:34:13
2025-05-05 19:34:12
cdncf.site - 1 entries


9410817709
leaf cert
CN=R11, O=Let's Encrypt, C=US
2025-02-04 19:29:49
2025-05-05 19:29:48
cdncf.site - 1 entries


9380048924
leaf cert
CN=R11, O=Let's Encrypt, C=US
2025-02-01 09:24:33
2025-05-02 09:24:32
cdncf.site - 1 entries


9380000841
leaf cert
CN=R10, O=Let's Encrypt, C=US
2025-02-01 09:20:06
2025-05-02 09:20:05
cdncf.site - 1 entries


9378806754
leaf cert
CN=R11, O=Let's Encrypt, C=US
2025-02-01 06:26:39
2025-05-02 06:26:38
cdncf.site - 1 entries


9370433428
leaf cert
CN=R10, O=Let's Encrypt, C=US
2025-01-31 07:50:05
2025-05-01 07:50:04
cdncf.site - 1 entries


9354643213
leaf cert
CN=R11, O=Let's Encrypt, C=US
2025-01-29 15:17:56
2025-04-29 15:17:55
cdncf.site - 1 entries


9354260440
leaf cert
CN=R11, O=Let's Encrypt, C=US
2025-01-29 14:17:41
2025-04-29 14:17:40
cdncf.site - 1 entries


9354129758
leaf cert
CN=R11, O=Let's Encrypt, C=US
2025-01-29 13:57:26
2025-04-29 13:57:25
cdncf.site - 1 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=R11, O=Let's Encrypt, C=US
0
2
2
CN=R10, O=Let's Encrypt, C=US
0
1
1

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
16489099840
leaf cert
CN=R10, O=Let's Encrypt, C=US
2025-02-01 08:20:06
2025-05-02 07:20:05
cdncf.site
1 entries


16457760103
leaf cert
CN=R11, O=Let's Encrypt, C=US
2025-01-29 14:17:56
2025-04-29 13:17:55
cdncf.site
1 entries


16456722813
precert
CN=R11, O=Let's Encrypt, C=US
2025-01-29 12:57:26
2025-04-29 11:57:25
cdncf.site
1 entries


 

11. Html-Content - Entries

No Html-Content entries found. Only checked if https + status 200/401/403/404

 

12. Html-Parsing via https://validator.w3.org/nu/


No https result http status 200 and Content-Type text/html or text/xml found, no Html-Parsing - Check

 

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: ns2.platformcraft.com

 

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

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
ns2.platformcraft.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns-1449.awsdns-53.org, ns-1549.awsdns-01.co.uk, ns-198.awsdns-24.com, ns-965.awsdns-56.net, ns4-cloud.nic.ru, ns4-l2.nic.ru, ns8-cloud.nic.ru, ns8-l2.nic.ru

Answer: ns-198.awsdns-24.com
205.251.192.198
3
org
NS
d.root-servers.net (2001:500:2d::d)

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-1449.awsdns-53.org
NS
a0.org.afilias-nst.info (2001:500:e::1)

Answer: g-ns-1080.awsdns-53.org, g-ns-1653.awsdns-53.org, g-ns-181.awsdns-53.org, g-ns-759.awsdns-53.org

Answer: g-ns-1080.awsdns-53.org
205.251.196.56, 2600:9000:5304:3800::1

Answer: g-ns-1653.awsdns-53.org
205.251.198.117, 2600:9000:5306:7500::1

Answer: g-ns-181.awsdns-53.org
205.251.192.181, 2600:9000:5300:b500::1

Answer: g-ns-759.awsdns-53.org
205.251.194.247, 2600:9000:5302:f700::1
5
uk
NS
h.root-servers.net (2001:500:1::53)

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

Answer: g-ns-1476.awsdns-01.co.uk, g-ns-1797.awsdns-01.co.uk, g-ns-321.awsdns-01.co.uk, g-ns-897.awsdns-01.co.uk

Answer: g-ns-1476.awsdns-01.co.uk
205.251.197.196, 2600:9000:5305:c400::1

Answer: g-ns-1797.awsdns-01.co.uk
205.251.199.5, 2600:9000:5307:500::1

Answer: g-ns-321.awsdns-01.co.uk
205.251.193.65, 2600:9000:5301:4100::1

Answer: g-ns-897.awsdns-01.co.uk
205.251.195.129, 2600:9000:5303:8100::1
7
net
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
8
ns-965.awsdns-56.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: g-ns-1400.awsdns-56.net, g-ns-1976.awsdns-56.net, g-ns-505.awsdns-56.net, g-ns-826.awsdns-56.net

Answer: g-ns-1400.awsdns-56.net
205.251.197.120, 2600:9000:5305:7800::1

Answer: g-ns-1976.awsdns-56.net
205.251.199.184, 2600:9000:5307:b800::1

Answer: g-ns-505.awsdns-56.net
205.251.193.249, 2600:9000:5301:f900::1

Answer: g-ns-826.awsdns-56.net
205.251.195.58, 2600:9000:5303:3a00::1
9
ru
NS
c.root-servers.net (2001:500:2::c)

Answer: a.dns.ripn.net, b.dns.ripn.net, d.dns.ripn.net, e.dns.ripn.net, f.dns.ripn.net
10
ns4-cloud.nic.ru
NS
a.dns.ripn.net (2001:678:17:0:193:232:128:6)

Answer: ns5.nic.RU, ns6.nic.RU, ns9.nic.RU

Answer: ns5.nic.RU
2a02:2090:e800:9000:31:177:67:100, 31.177.67.100

Answer: ns6.nic.RU
2a02:2090:ec00:9040:31:177:74:100, 31.177.74.100

Answer: ns9.nic.RU
2a02:2090:e400:7000:31:177:85:186, 31.177.85.186
11
ns4-l2.nic.ru
NS
a.dns.ripn.net (2001:678:17:0:193:232:128:6)

Answer: ns5.nic.RU, ns6.nic.RU, ns9.nic.RU

Answer: ns5.nic.RU
2a02:2090:e800:9000:31:177:67:100, 31.177.67.100

Answer: ns6.nic.RU
2a02:2090:ec00:9040:31:177:74:100, 31.177.74.100

Answer: ns9.nic.RU
2a02:2090:e400:7000:31:177:85:186, 31.177.85.186
12
ns8-cloud.nic.ru
NS
a.dns.ripn.net (2001:678:17:0:193:232:128:6)

Answer: ns5.nic.RU, ns6.nic.RU, ns9.nic.RU

Answer: ns5.nic.RU
2a02:2090:e800:9000:31:177:67:100, 31.177.67.100

Answer: ns6.nic.RU
2a02:2090:ec00:9040:31:177:74:100, 31.177.74.100

Answer: ns9.nic.RU
2a02:2090:e400:7000:31:177:85:186, 31.177.85.186
13
ns8-l2.nic.ru
NS
a.dns.ripn.net (2001:678:17:0:193:232:128:6)

Answer: ns5.nic.RU, ns6.nic.RU, ns9.nic.RU

Answer: ns5.nic.RU
2a02:2090:e800:9000:31:177:67:100, 31.177.67.100

Answer: ns6.nic.RU
2a02:2090:ec00:9040:31:177:74:100, 31.177.74.100

Answer: ns9.nic.RU
2a02:2090:e400:7000:31:177:85:186, 31.177.85.186
14
ns-1449.awsdns-53.org: 205.251.197.169
A
g-ns-1080.awsdns-53.org (2600:9000:5304:3800::1)
15
ns-1449.awsdns-53.org: 2600:9000:5305:a900::1
AAAA
g-ns-1080.awsdns-53.org (2600:9000:5304:3800::1)
16
ns-1549.awsdns-01.co.uk: 205.251.198.13
A
g-ns-1476.awsdns-01.co.uk (2600:9000:5305:c400::1)
17
ns-1549.awsdns-01.co.uk: 2600:9000:5306:d00::1
AAAA
g-ns-1476.awsdns-01.co.uk (2600:9000:5305:c400::1)
18
ns-965.awsdns-56.net: 205.251.195.197
A
g-ns-1400.awsdns-56.net (2600:9000:5305:7800::1)
19
ns-965.awsdns-56.net: 2600:9000:5303:c500::1
AAAA
g-ns-1400.awsdns-56.net (2600:9000:5305:7800::1)
20
ns4-cloud.nic.ru: 89.104.93.30, 89.104.93.33, 89.104.93.34, 89.104.95.30, 89.104.95.33, 89.104.95.34
A
ns5.nic.ru (2a02:2090:e800:9000:31:177:67:100)
21
ns4-cloud.nic.ru: No AAAA record found
AAAA
ns5.nic.ru (2a02:2090:e800:9000:31:177:67:100)
22
ns4-l2.nic.ru: 91.217.20.20
A
ns5.nic.ru (2a02:2090:e800:9000:31:177:67:100)
23
ns4-l2.nic.ru: No AAAA record found
AAAA
ns5.nic.ru (2a02:2090:e800:9000:31:177:67:100)
24
ns8-cloud.nic.ru: 89.104.93.31, 89.104.93.35, 89.104.93.36, 89.104.95.31, 89.104.95.35, 89.104.95.36
A
ns5.nic.ru (2a02:2090:e800:9000:31:177:67:100)
25
ns8-cloud.nic.ru: No AAAA record found
AAAA
ns5.nic.ru (2a02:2090:e800:9000:31:177:67:100)
26
ns8-l2.nic.ru: 91.217.21.20
A
ns5.nic.ru (2a02:2090:e800:9000:31:177:67:100)
27
ns8-l2.nic.ru: No AAAA record found
AAAA
ns5.nic.ru (2a02:2090:e800:9000:31:177:67:100)
28
ns2.platformcraft.com: 5.188.121.99
A
ns-1449.awsdns-53.org (2600:9000:5305:a900::1)
29
ns2.platformcraft.com: No AAAA record found
AAAA
ns-1449.awsdns-53.org (2600:9000:5305:a900::1)

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.cdncf.site
0

no CAA entry found
1
0
cdncf.site
0

no CAA entry found
1
0
site
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
cdncf.site
TXT record for cdncf.site
ok
1
0
www.cdncf.site
jGltjHl67f4Hkjr3fN7PnlaAgSfPjYE4CAXHKdkWmCk
looks good, but no _acme-challenge in domain name?
1
0
www.cdncf.site
YbkC6Zg5V1fENMS3-_Y1IcVC_TSfxs4ou9soZ_JU-ao
looks good, but no _acme-challenge in domain name?
1
0
_acme-challenge.cdncf.site
jGltjHl67f4Hkjr3fN7PnlaAgSfPjYE4CAXHKdkWmCk
looks good, correct length, correct characters
1
0
_acme-challenge.cdncf.site
YbkC6Zg5V1fENMS3-_Y1IcVC_TSfxs4ou9soZ_JU-ao
looks good, correct length, correct characters
1
0
_acme-challenge.www.cdncf.site
jGltjHl67f4Hkjr3fN7PnlaAgSfPjYE4CAXHKdkWmCk
looks good, correct length, correct characters
1
0
_acme-challenge.www.cdncf.site
YbkC6Zg5V1fENMS3-_Y1IcVC_TSfxs4ou9soZ_JU-ao
looks good, correct length, correct characters
1
0
_acme-challenge.cdncf.site.cdncf.site
jGltjHl67f4Hkjr3fN7PnlaAgSfPjYE4CAXHKdkWmCk
perhaps wrong
1
0
_acme-challenge.cdncf.site.cdncf.site
YbkC6Zg5V1fENMS3-_Y1IcVC_TSfxs4ou9soZ_JU-ao
perhaps wrong
1
0
_acme-challenge.www.cdncf.site.cdncf.site
jGltjHl67f4Hkjr3fN7PnlaAgSfPjYE4CAXHKdkWmCk
perhaps wrong
1
0
_acme-challenge.www.cdncf.site.cdncf.site
YbkC6Zg5V1fENMS3-_Y1IcVC_TSfxs4ou9soZ_JU-ao
perhaps wrong
1
0
_acme-challenge.www.cdncf.site.www.cdncf.site
jGltjHl67f4Hkjr3fN7PnlaAgSfPjYE4CAXHKdkWmCk
perhaps wrong
1
0
_acme-challenge.www.cdncf.site.www.cdncf.site
YbkC6Zg5V1fENMS3-_Y1IcVC_TSfxs4ou9soZ_JU-ao
perhaps wrong
1
0

 

16. DomainService - Entries

TypeDomainPrefValueDNS-errornum AnswersStatusDescription
_mta-sts
TXT
_mta-sts.cdncf.site

jGltjHl67f4Hkjr3fN7PnlaAgSfPjYE4CAXHKdkWmCk
2A MTA-STS TXT Entry (Mail Transfer Agent Strict Transport Security) must start with "'v=STSv1". Do you really want to create a MTA-STS? Or is it the effect of a wildcard * DNS?

 

 

17. Cipher Suites

No Ciphers found

 

18. Portchecks

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

 

 

Permalink: https://check-your-website.server-daten.de/?i=57eaa13c-0d0f-4031-9c94-8f3a7ce9f785

 

Last Result: https://check-your-website.server-daten.de/?q=cdncf.site - 2025-02-12 13:11:36

 

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

 

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

 

 

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

 

QR-Code of this page - https://check-your-website.server-daten.de/?d=cdncf.site