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


 

 

P

 

Tls-Protocol error

 

Checked:
31.10.2024 00:47:54

 

Older results

 

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
_acme-challenge.magic5114.xyz
CNAME
magic5114.xyz
yes
1
0

A
109.152.245.58
Blackburn/England/United Kingdom (GB) - BT Public Internet Service
Hostname: host109-152-245-58.range109-152.btcentralplus.com
yes


www._acme-challenge.magic5114.xyz

Name Error
yes
1
0
*.magic5114.xyz
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes


*._acme-challenge.magic5114.xyz
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 20326, Flags 257 (SEP = Secure Entry Point)






Public Key with Algorithm 8, KeyTag 61050, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 11.11.2024, 00:00:00 +, Signature-Inception: 21.10.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: xyz

xyz
2 DS RR in the parent zone found






DS with Algorithm 8, KeyTag 3599, DigestType 2 and Digest uXM4abyEyGu1nRArpdprJ7IIhVIzKjnc1UvE6NZrBJk=






DS with Algorithm 8, KeyTag 18130, DigestType 2 and Digest WqWWEmZZTM6sUJSamSGf4ATxMOGGSkJxQ+n/LmQcrG8=






1 RRSIG RR to validate DS RR found






RRSIG-Owner xyz., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 12.11.2024, 20:00:00 +, Signature-Inception: 30.10.2024, 19:00:00 +, KeyTag 61050, Signer-Name: (root)






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






2 DNSKEY RR found






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






Public Key with Algorithm 8, KeyTag 65206, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner xyz., Algorithm: 8, 1 Labels, original TTL: 3600 sec, Signature-expiration: 12.11.2024, 14:35:57 +, Signature-Inception: 13.10.2024, 13:05:57 +, KeyTag 18130, Signer-Name: xyz






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






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



Zone: magic5114.xyz

magic5114.xyz
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 "fr2phqt5rk10augv2nr8sgphklm30fqs" between the hashed NSEC3-owner "fr2h9spf06flt9c7ofeej3rk63dq22ck" and the hashed NextOwner "fr3rb0k0nh7tuv3ik24u23jgfb3lkau3". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner fr2h9spf06flt9c7ofeej3rk63dq22ck.xyz., Algorithm: 8, 2 Labels, original TTL: 900 sec, Signature-expiration: 12.11.2024, 16:25:59 +, Signature-Inception: 13.10.2024, 14:55:59 +, KeyTag 65206, Signer-Name: xyz






DS-Query in the parent zone sends valid NSEC3 RR with the Hash "2tjms8vm0h8n7j9e748d19gpnujm0emj" as Owner. That's the Hash of "xyz" with the NextHashedOwnerName "2tk402ni9id6k9m9fq8phvqjhvtfq9o6". So that domain name is the Closest Encloser of "magic5114.xyz". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 2tjms8vm0h8n7j9e748d19gpnujm0emj.xyz., Algorithm: 8, 2 Labels, original TTL: 900 sec, Signature-expiration: 12.11.2024, 14:35:57 +, Signature-Inception: 13.10.2024, 13:05:57 +, KeyTag 65206, Signer-Name: xyz






0 DNSKEY RR found









Zone: _acme-challenge.magic5114.xyz

_acme-challenge.magic5114.xyz
0 DS RR in the parent zone found



Zone: www._acme-challenge.magic5114.xyz

www._acme-challenge.magic5114.xyz
0 DS RR in the parent zone found

 

3. Name Servers

DomainNameserverNS-IP
www._acme-challenge.magic5114.xyz
  logan.ns.cloudflare.com

magic5114.xyz
  logan.ns.cloudflare.com / 67m87
108.162.193.198
Toronto/Ontario/Canada (CA) - Cloudflare, Inc.


 
172.64.33.198
Toronto/Ontario/Canada (CA) - Cloudflare, Inc.


 
173.245.59.198
Toronto/Ontario/Canada (CA) - Cloudflare, Inc.


 
2606:4700:58::adf5:3bc6
Montreal/Quebec/Canada (CA) - Cloudflare, Inc.


 
2803:f800:50::6ca2:c1c6
San José/Provincia de San José/Costa Rica (CR) - Cloudflare, Inc.


 
2a06:98c1:50::ac40:21c6
London/England/United Kingdom (GB) - Cloudflare, Inc.


  princess.ns.cloudflare.com / 67m99
108.162.194.17
Toronto/Ontario/Canada (CA) - Cloudflare, Inc.


 
162.159.38.17
Los Angeles/California/United States (US) - Cloudflare, Inc.


 
172.64.34.17
Toronto/Ontario/Canada (CA) - Cloudflare, Inc.


 
2606:4700:50::a29f:2611
Montreal/Quebec/Canada (CA) - Cloudflare, Inc.


 
2803:f800:50::6ca2:c211
San José/Provincia de San José/Costa Rica (CR) - Cloudflare, Inc.


 
2a06:98c1:50::ac40:2211
London/England/United Kingdom (GB) - Cloudflare, Inc.

xyz
  generationxyz.nic.xyz / PDUS-VJ5JVS-CTI2KM


  ns0.centralnic.net


  x.nic.xyz / SFQY-BG7AF9-XTW0MS


  y.nic.xyz / PDUS-VJ5JVS-CTI2KM


  z.nic.xyz / SFQY-BG7AF9-XTW0MS

 

4. SOA-Entries


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


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


Domain:magic5114.xyz
Zone-Name:magic5114.xyz
Primary:logan.ns.cloudflare.com
Mail:dns.cloudflare.com
Serial:2355817293
Refresh:10000
Retry:2400
Expire:604800
TTL:1800
num Entries:12


Domain:www._acme-challenge.magic5114.xyz
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://_acme-challenge.magic5114.xyz/
109.152.245.58
200


0.073
H
Server: Caddy
Date: Wed, 30 Oct 2024 23:48:39 GMT
Content-Length: 0

• https://_acme-challenge.magic5114.xyz/
109.152.245.58
-103


0.067
P
SecureConnectionError (3, 0x80131501). The SSL connection could not be established, see inner exception. Authentication failed because the remote party sent a TLS alert: 'InternalError' (FF: SSL_ERROR_INTERNAL_ERROR_ALERT)

• http://_acme-challenge.magic5114.xyz/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
109.152.245.58
200


0.036

Visible Content:
Server: Caddy
Date: Wed, 30 Oct 2024 23:48:39 GMT
Content-Length: 0

• https://109.152.245.58/
109.152.245.58
-103


0.073
P
SecureConnectionError (3, 0x80131501). The SSL connection could not be established, see inner exception. Authentication failed because the remote party sent a TLS alert: 'InternalError' (FF: SSL_ERROR_INTERNAL_ERROR_ALERT)

 

7. Comments


1. General Results, most used to calculate the result

Aname "_acme-challenge.magic5114.xyz" is subdomain, public suffix is ".xyz", top-level-domain is ".xyz", top-level-domain-type is "generic", tld-manager is "XYZ.COM LLC", num .xyz-domains preloaded: 1891 (complete: 251685)
AGood: All ip addresses are public addresses
Warning: Only one ip address found: _acme-challenge.magic5114.xyz 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: _acme-challenge.magic5114.xyz 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
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.
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 _acme-challenge.magic5114.xyz, 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._acme-challenge.magic5114.xyz

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:: 7 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
AInfo:: 7 Queries complete, 7 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
Ok (4 - 8):: An average of 3.5 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 2 different Name Servers found: logan.ns.cloudflare.com, princess.ns.cloudflare.com, 2 Name Servers included in Delegation: logan.ns.cloudflare.com, princess.ns.cloudflare.com, 2 Name Servers included in 1 Zone definitions: logan.ns.cloudflare.com, princess.ns.cloudflare.com, 1 Name Servers listed in SOA.Primary: logan.ns.cloudflare.com.
AGood: Only one SOA.Primary Name Server found.: logan.ns.cloudflare.com.
AGood: SOA.Primary Name Server included in the delegation set.: logan.ns.cloudflare.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.
AInfo: Ipv4-Subnet-list: 6 Name Servers, 4 different subnets (first Byte): 108., 162., 172., 173., 4 different subnets (first two Bytes): 108.162., 162.159., 172.64., 173.245., 6 different subnets (first three Bytes): 108.162.193., 108.162.194., 162.159.38., 172.64.33., 172.64.34., 173.245.59.
AGood: Name Server IPv4-addresses from different subnet found:
AInfo: IPv6-Subnet-list: 6 Name Servers with IPv6, 3 different subnets (first block): 2606:, 2803:, 2a06:, 3 different subnets (first two blocks): 2606:4700:, 2803:f800:, 2a06:98c1:, 4 different subnets (first three blocks): 2606:4700:0050:, 2606:4700:0058:, 2803:f800:0050:, 2a06:98c1:0050:, 4 different subnets (first four blocks): 2606:4700:0050:0000:, 2606:4700:0058:0000:, 2803:f800:0050:0000:, 2a06:98c1:0050:0000:
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 12 good Nameserver
AGood: Nameserver supports Echo Capitalization: 12 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 12 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 12 good Nameserver
Nameserver doesn't pass all EDNS-Checks: logan.ns.cloudflare.com: 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: 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: x.nic.xyz: 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: z.nic.xyz: 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.
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://_acme-challenge.magic5114.xyz/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 109.152.245.58
200

Warning: Not existing ACME-file, but Server sends 200, not 404 or redirect. May be a problem creating a Letsencrypt certificate. Checking /.well-known/acme-challenge/random-filename - a http status 404 - Not Found - is expected. If your server sends content and a http status 200, the validation file (87 bytes, token, dot and the hash of the public part of the account key) may be invisible, so Letsencrypt can't validate your domain. If it is an application that sends this content, perhaps create an exception, so /.well-known/acme-challenge sends raw files. Or create a redirect to another domain and / or port 443, but your Letsencrypt client must support such a solution. Certbot: Use webroot as authenticator - https://certbot.eff.org/docs/using.html 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: 62203 milliseconds, 62.203 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 ECC Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, C=GB, ST=Greater Manchester
0
1
1
CN=WE1, O=Google Trust Services, C=US
0
1
1

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
8517916508
precert
CN=WE1, O=Google Trust Services, C=US
2024-10-28 13:48:03
2025-01-26 13:48:02
*.magic5114.xyz, magic5114.xyz - 2 entries


8516875344
leaf cert
CN=Sectigo ECC Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, C=GB, ST=Greater Manchester
2024-10-28 00:00:00
2025-10-28 23:59:59
*.magic5114.xyz, magic5114.xyz - 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=Sectigo ECC Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, C=GB, ST=Greater Manchester
0
1
1
CN=WE1, O=Google Trust Services, C=US
0
1
1

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
15120251709
precert
CN=WE1, O=Google Trust Services, C=US
2024-10-28 12:48:03
2025-01-26 12:48:02
*.magic5114.xyz, magic5114.xyz
2 entries


15111627349
leaf cert
CN=Sectigo ECC Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, C=GB, ST=Greater Manchester
2024-10-27 23:00:00
2025-10-28 22:59:59
*.magic5114.xyz, magic5114.xyz
2 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.nu/ / https://validator.w3.org/nu/ (started 2024-09-28, 09:00, alpha)

  Unfortunately, there are differences between the first used validator.nu and validator.w3.org/nu/ - switched to validator.w3.org/nu/. Looks like some error messages (link - fetchpriority attribute) of validator.nu are obsolete, not seen in the w3.org-version and not found in the current specification: link may have a fetchpriority attribute.

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: logan.ns.cloudflare.com, princess.ns.cloudflare.com

 

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

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

Answer: ns3.cloudflare.com, ns4.cloudflare.com, ns5.cloudflare.com, ns6.cloudflare.com, ns7.cloudflare.com

Answer: ns3.cloudflare.com
162.159.0.33, 162.159.7.226, 2400:cb00:2049:1::a29f:21, 2400:cb00:2049:1::a29f:7e2

Answer: ns4.cloudflare.com
162.159.1.33, 162.159.8.55, 2400:cb00:2049:1::a29f:121, 2400:cb00:2049:1::a29f:837

Answer: ns5.cloudflare.com
162.159.2.9, 162.159.9.55, 2400:cb00:2049:1::a29f:209, 2400:cb00:2049:1::a29f:937

Answer: ns6.cloudflare.com
162.159.3.11, 162.159.5.6, 2400:cb00:2049:1::a29f:30b, 2400:cb00:2049:1::a29f:506

Answer: ns7.cloudflare.com
162.159.4.8, 162.159.6.6, 2400:cb00:2049:1::a29f:408, 2400:cb00:2049:1::a29f:606
3
princess.ns.cloudflare.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns3.cloudflare.com, ns4.cloudflare.com, ns5.cloudflare.com, ns6.cloudflare.com, ns7.cloudflare.com

Answer: ns3.cloudflare.com
162.159.0.33, 162.159.7.226, 2400:cb00:2049:1::a29f:21, 2400:cb00:2049:1::a29f:7e2

Answer: ns4.cloudflare.com
162.159.1.33, 162.159.8.55, 2400:cb00:2049:1::a29f:121, 2400:cb00:2049:1::a29f:837

Answer: ns5.cloudflare.com
162.159.2.9, 162.159.9.55, 2400:cb00:2049:1::a29f:209, 2400:cb00:2049:1::a29f:937

Answer: ns6.cloudflare.com
162.159.3.11, 162.159.5.6, 2400:cb00:2049:1::a29f:30b, 2400:cb00:2049:1::a29f:506

Answer: ns7.cloudflare.com
162.159.4.8, 162.159.6.6, 2400:cb00:2049:1::a29f:408, 2400:cb00:2049:1::a29f:606
4
logan.ns.cloudflare.com: 108.162.193.198, 172.64.33.198, 173.245.59.198
A
ns3.cloudflare.com (2400:cb00:2049:1::a29f:21)
5
logan.ns.cloudflare.com: 2606:4700:58::adf5:3bc6, 2803:f800:50::6ca2:c1c6, 2a06:98c1:50::ac40:21c6
AAAA
ns3.cloudflare.com (2400:cb00:2049:1::a29f:21)
6
princess.ns.cloudflare.com: 108.162.194.17, 162.159.38.17, 172.64.34.17
A
ns3.cloudflare.com (2400:cb00:2049:1::a29f:21)
7
princess.ns.cloudflare.com: 2606:4700:50::a29f:2611, 2803:f800:50::6ca2:c211, 2a06:98c1:50::ac40:2211
AAAA
ns3.cloudflare.com (2400:cb00:2049:1::a29f:21)

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
_acme-challenge.magic5114.xyz
0

no CAA entry found
1
0
magic5114.xyz
0

no CAA entry found
1
0
xyz
0

no CAA entry found
1
0

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
magic5114.xyz

ok
1
0
_acme-challenge.magic5114.xyz

missing entry or wrong length
1
0
_acme-challenge._acme-challenge.magic5114.xyz

Name Error - The domain name does not exist
1
0
_acme-challenge._acme-challenge.magic5114.xyz.magic5114.xyz

Name Error - The domain name does not exist
1
0
_acme-challenge._acme-challenge.magic5114.xyz._acme-challenge.magic5114.xyz

Name Error - The domain name does not exist
1
0

 

16. DomainService - Entries

TypeDomainPrefValueDNS-errornum AnswersStatusDescription
SPF
TXT
_acme-challenge.magic5114.xyz

32768TXT expected, but CNAME found. CNAME not allowed, only TXT queries are allowed. See RFC 7208, 4.4.

 

 

17. Cipher Suites

No results

 

18. Portchecks

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

 

 

Permalink: https://check-your-website.server-daten.de/?i=f54b4415-4a52-4326-b3c4-b0fdc73e58a3

 

Last Result: https://check-your-website.server-daten.de/?q=_acme-challenge.magic5114.xyz - 2024-10-31 00:47:54

 

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

 

<a href="https://check-your-website.server-daten.de/?q=_acme-challenge.magic5114.xyz" target="_blank">Check this Site: _acme-challenge.magic5114.xyz</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=_acme-challenge.magic5114.xyz