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

...

skip EDNS-Check

skip Content-Check

check links

Tls-Protocol error

Checked:
29.01.2026 23:32:09

Older results

P - 18.01.2026 03:52:57

P - 24.11.2025 06:18:50

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
donaldtrump4president.com	A	3.33.251.168 Montreal/Quebec/Canada (CA) - Amazon.com, Inc. Hostname: aec037177372cc6cd.awsglobalaccelerator.com	yes	2	0
	A	15.197.225.128 Montreal/Quebec/Canada (CA) - Amazon.com, Inc. Hostname: aec037177372cc6cd.awsglobalaccelerator.com	yes	2	0
	AAAA		yes
www.donaldtrump4president.com	CNAME	donaldtrump4president.com	yes	1	0
	A	3.33.251.168 Montreal/Quebec/Canada (CA) - Amazon.com, Inc. Hostname: aec037177372cc6cd.awsglobalaccelerator.com	yes
	A	15.197.225.128 Montreal/Quebec/Canada (CA) - Amazon.com, Inc. Hostname: aec037177372cc6cd.awsglobalaccelerator.com	yes
*.donaldtrump4president.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


	3 DNSKEY RR found


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


	Public Key with Algorithm 8, KeyTag 21831, 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: 11.02.2026, 00:00:00 +, Signature-Inception: 21.01.2026, 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 13, KeyTag 19718, DigestType 2 and Digest isuwzSj0ElCoCkkTiUJNNBUi2Uaw2gwCkfLT13HXgFo=


	1 RRSIG RR to validate DS RR found


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


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


	2 DNSKEY RR found


	Public Key with Algorithm 13, KeyTag 19718, Flags 257 (SEP = Secure Entry Point)


	Public Key with Algorithm 13, KeyTag 35511, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner com., Algorithm: 13, 1 Labels, original TTL: 86400 sec, Signature-expiration: 11.02.2026, 15:02:35 +, Signature-Inception: 27.01.2026, 14:57:35 +, KeyTag 19718, Signer-Name: com


	• Status: Good - Algorithmus 13 and DNSKEY with KeyTag 19718 used to validate the DNSKEY RRSet


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

Zone: donaldtrump4president.com
donaldtrump4president.com	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 "6mpe56l0a5q34mmoscjqohc4400se49a" between the hashed NSEC3-owner "6mpe54tg8tmri95tltc2577gos0krf0u" and the hashed NextOwner "6mpe8j3h6i3erlu3rb16nkt35403vg93". So the parent zone confirmes the not-existence of a DS RR. Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 6mpe54tg8tmri95tltc2577gos0krf0u.com., Algorithm: 13, 2 Labels, original TTL: 900 sec, Signature-expiration: 03.02.2026, 00:39:08 +, Signature-Inception: 26.01.2026, 23:29:08 +, KeyTag 35511, Signer-Name: com


	DS-Query in the parent zone sends valid NSEC3 RR with the Hash "ck0pojmg874ljref7efn8430qvit8bsm" as Owner. That's the Hash of "com" with the NextHashedOwnerName "ck0q3udg8cekkae7rukpgct1dvssh8ll". So that domain name is the Closest Encloser of "donaldtrump4president.com". Opt-Out: True. Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner ck0pojmg874ljref7efn8430qvit8bsm.com., Algorithm: 13, 2 Labels, original TTL: 900 sec, Signature-expiration: 03.02.2026, 00:27:13 +, Signature-Inception: 26.01.2026, 23:17:13 +, KeyTag 35511, Signer-Name: com


	0 DNSKEY RR found




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

3. Name Servers

Domain	Nameserver	NS-IP
donaldtrump4president.com	• ns17.domaincontrol.com / hex:0D 70 30 37	97.74.108.9 Tempe/Arizona/United States (US) - Host Europe GmbH	•
	•	2603:5:21c0::9 New York/United States (US) - Host Europe GmbH	•
	• ns18.domaincontrol.com / hex:0D 70 30 34	173.201.76.9 Tempe/Arizona/United States (US) - Host Europe GmbH	•
	•	2603:5:22c0::9 New York/United States (US) - Host Europe GmbH	•
com	• a.gtld-servers.net / nnn1-par6		•
	• b.gtld-servers.net / nnn1-elwaw4		•
	• c.gtld-servers.net / nnn1-par6		•
	• d.gtld-servers.net / nnn1-par6		•
	• e.gtld-servers.net / nnn1-par6		•
	• f.gtld-servers.net / nnn1-defra-4		•
	• g.gtld-servers.net / nnn1-defra-4		•
	• h.gtld-servers.net / nnn1-defra-4		•
	• i.gtld-servers.net / nnn1-defra-4		•
	• j.gtld-servers.net / nnn1-ein2		•
	• k.gtld-servers.net / nnn1-ein1		•
	• l.gtld-servers.net / nnn1-frmrs-2		•
	• m.gtld-servers.net / nnn1-frmrs-2		•

4. SOA-Entries

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

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

Domain:	donaldtrump4president.com
Zone-Name:	donaldtrump4president.com
Primary:	ns17.domaincontrol.com
Mail:	dns.jomax.net
Serial:	2025062403
Refresh:	28800
Retry:	7200
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

show header:

Domainname	Http-Status	redirect	Sec.	G
• http://donaldtrump4president.com/ 3.33.251.168	302	https://www.thecreditreportwithbilllewis.com/ Html is minified: 103.08 %	0.047	E
Date: Thu, 29 Jan 2026 22:32:51 GMT
Connection: keep-alive
Location: https://www.thecreditreportwithbilllewis.com/
Server: ip-100-74-4-33.eu-west-2.compute.internal
Vary: Accept-Encoding
X-Request-ID: dbd115f2-268a-4526-b8cf-7b59a86c589b
Content-Type: text/html; charset=utf-8
Content-Length: 67

• http://donaldtrump4president.com/ 15.197.225.128	302	https://www.thecreditreportwithbilllewis.com/ Html is minified: 103.08 %	0.054	E
Date: Thu, 29 Jan 2026 22:32:51 GMT
Connection: keep-alive
Location: https://www.thecreditreportwithbilllewis.com/
Server: ip-100-74-4-101.eu-west-2.compute.internal
Vary: Accept-Encoding
X-Request-ID: ff44149f-359a-419a-a8ef-d0d39ddc08c3
Content-Type: text/html; charset=utf-8
Content-Length: 67

• http://www.donaldtrump4president.com/ 3.33.251.168	302	https://www.thecreditreportwithbilllewis.com/ Html is minified: 103.08 %	0.027	E
Date: Thu, 29 Jan 2026 22:32:51 GMT
Connection: keep-alive
Location: https://www.thecreditreportwithbilllewis.com/
Server: ip-100-74-5-111.eu-west-2.compute.internal
Vary: Accept-Encoding
X-Request-ID: 81d7c47e-1bd9-4b1b-94bc-7c0ce2ec0ba6
Content-Type: text/html; charset=utf-8
Content-Length: 67

• http://www.donaldtrump4president.com/ 15.197.225.128	302	https://www.thecreditreportwithbilllewis.com/ Html is minified: 103.08 %	0.030	E
Date: Thu, 29 Jan 2026 22:32:51 GMT
Connection: keep-alive
Location: https://www.thecreditreportwithbilllewis.com/
Server: ip-100-74-4-168.eu-west-2.compute.internal
Vary: Accept-Encoding
X-Request-ID: 9e9b9541-4ece-4f90-b65a-bfbce699cb68
Content-Type: text/html; charset=utf-8
Content-Length: 67

• https://donaldtrump4president.com/ 3.33.251.168	-103		0.063	P
SecureConnectionError (3, 0x80131501). The SSL connection could not be established, see inner exception. Authentication failed because the remote party sent a TLS alert: 'ProtocolVersion' Only Tls.1.3 allowed? That's bad, allow Tls.1.2.

• https://donaldtrump4president.com/ 15.197.225.128	-103		0.060	P
SecureConnectionError (3, 0x80131501). The SSL connection could not be established, see inner exception. Authentication failed because the remote party sent a TLS alert: 'ProtocolVersion' Only Tls.1.3 allowed? That's bad, allow Tls.1.2.

• https://www.donaldtrump4president.com/ 3.33.251.168	-103		0.056	P
SecureConnectionError (3, 0x80131501). The SSL connection could not be established, see inner exception. Authentication failed because the remote party sent a TLS alert: 'ProtocolVersion' Only Tls.1.3 allowed? That's bad, allow Tls.1.2.

• https://www.donaldtrump4president.com/ 15.197.225.128	-103		0.066	P
SecureConnectionError (3, 0x80131501). The SSL connection could not be established, see inner exception. Authentication failed because the remote party sent a TLS alert: 'ProtocolVersion' Only Tls.1.3 allowed? That's bad, allow Tls.1.2.

• https://www.thecreditreportwithbilllewis.com/	-103		0.120	P
SecureConnectionError (3, 0x80131501). The SSL connection could not be established, see inner exception. Authentication failed because the remote party sent a TLS alert: 'ProtocolVersion' Only Tls.1.3 allowed? That's bad, allow Tls.1.2.

• http://donaldtrump4president.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 3.33.251.168	403		0.023	M
Forbidden
Visible Content:
Server: awselb/2.0
Date: Thu, 29 Jan 2026 22:32:51 GMT
Connection: keep-alive
WAFRule: 4
Content-Length: 0

• http://donaldtrump4president.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 15.197.225.128	403		0.027	M
Forbidden
Visible Content:
Server: awselb/2.0
Date: Thu, 29 Jan 2026 22:32:51 GMT
Connection: keep-alive
WAFRule: 4
Content-Length: 0

• http://www.donaldtrump4president.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 3.33.251.168	403		0.026	M
Forbidden
Visible Content:
Server: awselb/2.0
Date: Thu, 29 Jan 2026 22:32:51 GMT
Connection: keep-alive
WAFRule: 4
Content-Length: 0

• http://www.donaldtrump4president.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 15.197.225.128	403		0.023	M
Forbidden
Visible Content:
Server: awselb/2.0
Date: Thu, 29 Jan 2026 22:32:51 GMT
Connection: keep-alive
WAFRule: 4
Content-Length: 0

• https://3.33.251.168/ 3.33.251.168	-103		0.056	P
SecureConnectionError (3, 0x80131501). The SSL connection could not be established, see inner exception. Authentication failed because the remote party sent a TLS alert: 'ProtocolVersion' Only Tls.1.3 allowed? That's bad, allow Tls.1.2.

• https://15.197.225.128/ 15.197.225.128	-103		0.063	P
SecureConnectionError (3, 0x80131501). The SSL connection could not be established, see inner exception. Authentication failed because the remote party sent a TLS alert: 'ProtocolVersion' Only Tls.1.3 allowed? That's bad, allow Tls.1.2.

7. Comments

	1. General Results, most used to calculate the result
A	name "donaldtrump4president.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: 108094 (complete: 276475)
A	Good: All ip addresses are public addresses
A	Good: Minimal 2 ip addresses per domain name found: donaldtrump4president.com has 2 different ip addresses (authoritative).
A	Good: Minimal 2 ip addresses per domain name found: www.donaldtrump4president.com has 2 different ip addresses (authoritative).
	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: donaldtrump4president.com 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.donaldtrump4president.com has no ipv6 address.
A	Good: No asked Authoritative Name Server had a timeout
A	Good: 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.
C	Error - no version with Http-Status 200
E	http://donaldtrump4president.com/ 3.33.251.168	302	https://www.thecreditreportwithbilllewis.com/	Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
E	http://donaldtrump4president.com/ 15.197.225.128	302	https://www.thecreditreportwithbilllewis.com/	Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
E	http://www.donaldtrump4president.com/ 3.33.251.168	302	https://www.thecreditreportwithbilllewis.com/	Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
E	http://www.donaldtrump4president.com/ 15.197.225.128	302	https://www.thecreditreportwithbilllewis.com/	Wrong redirect one domain http to other domain https. First redirect to https without new dns query, so the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. 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. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
H	Fatal error: No https - result with http-status 200, no encryption
A	Good: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain donaldtrump4president.com, 2 ip addresses.
A	Good: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain www.donaldtrump4president.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 donaldtrump4president.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.donaldtrump4president.com, 2 ip addresses.
B	No _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.donaldtrump4president.com
	2. Header-Checks
U				No https result with http status 2 or 4 (standard-check) found, no header checked.
	3. DNS- and NameServer - Checks
A	Info:: 26 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
A	Info:: 26 Queries complete, 26 with IPv6, 0 with IPv4.
A	Good: All DNS Queries done via IPv6.
	Bad (greater 8):: An average of 13.0 queries per domain name server required to find all ip addresses of all name servers.
A	Info:: 2 different Name Servers found: ns17.domaincontrol.com, ns18.domaincontrol.com, 2 Name Servers included in Delegation: ns17.domaincontrol.com, ns18.domaincontrol.com, 2 Name Servers included in 1 Zone definitions: ns17.domaincontrol.com, ns18.domaincontrol.com, 1 Name Servers listed in SOA.Primary: ns17.domaincontrol.com.
A	Good: Only one SOA.Primary Name Server found.: ns17.domaincontrol.com.
A	Good: SOA.Primary Name Server included in the delegation set.: ns17.domaincontrol.com.
A	Good: 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: ns17.domaincontrol.com, ns18.domaincontrol.com
A	Good: All Name Server Domain Names have a Public Suffix.
A	Good: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
A	Good: All Name Server ip addresses are public.
A	Good: Minimal 2 different name servers (public suffix and public ip address) found: 2 different Name Servers found
A	Good: 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: domaincontrol.com
	Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: US
A	Info: Ipv4-Subnet-list: 2 Name Servers, 2 different subnets (first Byte): 173., 97., 2 different subnets (first two Bytes): 173.201., 97.74., 2 different subnets (first three Bytes): 173.201.76., 97.74.108.
A	Excellent: Every Name Server IPv4-address starts with an unique Byte.
A	Info: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2603:, 1 different subnets (first two blocks): 2603:0005:, 2 different subnets (first three blocks): 2603:0005:21c0:, 2603:0005:22c0:, 2 different subnets (first four blocks): 2603:0005:21c0:0000:, 2603:0005:22c0:0000:
A	Good: Name Server IPv6 addresses from different subnets found.
A	Good: Nameserver supports TCP connections: 4 good Nameserver
A	Good: Nameserver supports Echo Capitalization: 4 good Nameserver
A	Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 4 good Nameserver
A	Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 4 good Nameserver
A	Good: 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://donaldtrump4president.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 3.33.251.168	403		Fatal: Check of /.well-known/acme-challenge/random-filename has a http status 401 / 403 Not Allowed / Forbidden. A http status 404 - Not Found - is expected. Creating a Letsencrypt certificate via http-01 challenge may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
	http://donaldtrump4president.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 15.197.225.128	403		Fatal: Check of /.well-known/acme-challenge/random-filename has a http status 401 / 403 Not Allowed / Forbidden. A http status 404 - Not Found - is expected. Creating a Letsencrypt certificate via http-01 challenge may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
	http://www.donaldtrump4president.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 3.33.251.168	403		Fatal: Check of /.well-known/acme-challenge/random-filename has a http status 401 / 403 Not Allowed / Forbidden. A http status 404 - Not Found - is expected. Creating a Letsencrypt certificate via http-01 challenge may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
	http://www.donaldtrump4president.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 15.197.225.128	403		Fatal: Check of /.well-known/acme-challenge/random-filename has a http status 401 / 403 Not Allowed / Forbidden. A http status 404 - Not Found - is expected. Creating a Letsencrypt certificate via http-01 challenge may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
A	Info: No img element found, no alt attribute checked
A	Good: 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
A	Info: Different Server-Headers found
A	Duration: 86343 milliseconds, 86.343 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)

Issuer				last 7 days	active	num Certs
//certs.godaddy.com/repository/, CN=Go Daddy Secure Certificate Authority - G2				0	2	2

CertSpotter-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
10880562579 leaf cert	//certs.godaddy.com/repository/, CN=Go Daddy Secure Certificate Authority - G2	2025-06-25 05:28:11	2026-06-25 05:28:11	www.donaldtrump4president.com - 1 entries
10879331789 leaf cert	//certs.godaddy.com/repository/, CN=Go Daddy Secure Certificate Authority - G2	2025-06-25 02:33:22	2026-06-25 02:33:21	donaldtrump4president.com - 1 entries

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. 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: ns17.domaincontrol.com, ns18.domaincontrol.com

QNr.	Domain	Type	NS used
1	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
2	ns17.domaincontrol.com	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: a1-245.akam.net, a11-64.akam.net, a20-65.akam.net, a6-66.akam.net, a8-67.akam.net, a9-67.akam.net, ans01.domaincontrol.com, ans02.domaincontrol.com
	Answer: ans01.domaincontrol.com 2603:5:2111::23, 97.74.97.35
	Answer: ans02.domaincontrol.com 173.201.65.35, 2603:5:2211::23
3	ns18.domaincontrol.com	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: a1-245.akam.net, a11-64.akam.net, a20-65.akam.net, a6-66.akam.net, a8-67.akam.net, a9-67.akam.net, ans01.domaincontrol.com, ans02.domaincontrol.com
	Answer: ans01.domaincontrol.com 2603:5:2111::23, 97.74.97.35
	Answer: ans02.domaincontrol.com 173.201.65.35, 2603:5:2211::23
4	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
5	a1-245.akam.net	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a4-67.akam.net, a6-67.akam.net
	Answer: a1-67.akam.net 193.108.91.67, 2600:1401:2::43
	Answer: a11-67.akam.net 2600:1480:1::43, 84.53.139.67
	Answer: a12-67.akam.net 184.26.160.67, 2600:1480:f000::43
	Answer: a18-67.akam.net 2600:1480:4800::43, 95.101.36.67
	Answer: a22-67.akam.net 23.211.61.67, 2600:1480:7800::43
	Answer: a28-67.akam.net 2600:1480:d800::43, 95.100.173.67
	Answer: a4-67.akam.net 2600:1480:9000::43, 72.246.46.67
	Answer: a6-67.akam.net 23.211.133.67, 2600:1401:1::43
6	a11-64.akam.net	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a4-67.akam.net, a6-67.akam.net
	Answer: a1-67.akam.net 193.108.91.67, 2600:1401:2::43
	Answer: a11-67.akam.net 2600:1480:1::43, 84.53.139.67
	Answer: a12-67.akam.net 184.26.160.67, 2600:1480:f000::43
	Answer: a18-67.akam.net 2600:1480:4800::43, 95.101.36.67
	Answer: a22-67.akam.net 23.211.61.67, 2600:1480:7800::43
	Answer: a28-67.akam.net 2600:1480:d800::43, 95.100.173.67
	Answer: a4-67.akam.net 2600:1480:9000::43, 72.246.46.67
	Answer: a6-67.akam.net 23.211.133.67, 2600:1401:1::43
7	a20-65.akam.net	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a4-67.akam.net, a6-67.akam.net
	Answer: a1-67.akam.net 193.108.91.67, 2600:1401:2::43
	Answer: a11-67.akam.net 2600:1480:1::43, 84.53.139.67
	Answer: a12-67.akam.net 184.26.160.67, 2600:1480:f000::43
	Answer: a18-67.akam.net 2600:1480:4800::43, 95.101.36.67
	Answer: a22-67.akam.net 23.211.61.67, 2600:1480:7800::43
	Answer: a28-67.akam.net 2600:1480:d800::43, 95.100.173.67
	Answer: a4-67.akam.net 2600:1480:9000::43, 72.246.46.67
	Answer: a6-67.akam.net 23.211.133.67, 2600:1401:1::43
8	a6-66.akam.net	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a4-67.akam.net, a6-67.akam.net
	Answer: a1-67.akam.net 193.108.91.67, 2600:1401:2::43
	Answer: a11-67.akam.net 2600:1480:1::43, 84.53.139.67
	Answer: a12-67.akam.net 184.26.160.67, 2600:1480:f000::43
	Answer: a18-67.akam.net 2600:1480:4800::43, 95.101.36.67
	Answer: a22-67.akam.net 23.211.61.67, 2600:1480:7800::43
	Answer: a28-67.akam.net 2600:1480:d800::43, 95.100.173.67
	Answer: a4-67.akam.net 2600:1480:9000::43, 72.246.46.67
	Answer: a6-67.akam.net 23.211.133.67, 2600:1401:1::43
9	a8-67.akam.net	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a4-67.akam.net, a6-67.akam.net
	Answer: a1-67.akam.net 193.108.91.67, 2600:1401:2::43
	Answer: a11-67.akam.net 2600:1480:1::43, 84.53.139.67
	Answer: a12-67.akam.net 184.26.160.67, 2600:1480:f000::43
	Answer: a18-67.akam.net 2600:1480:4800::43, 95.101.36.67
	Answer: a22-67.akam.net 23.211.61.67, 2600:1480:7800::43
	Answer: a28-67.akam.net 2600:1480:d800::43, 95.100.173.67
	Answer: a4-67.akam.net 2600:1480:9000::43, 72.246.46.67
	Answer: a6-67.akam.net 23.211.133.67, 2600:1401:1::43
10	a9-67.akam.net	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a4-67.akam.net, a6-67.akam.net
	Answer: a1-67.akam.net 193.108.91.67, 2600:1401:2::43
	Answer: a11-67.akam.net 2600:1480:1::43, 84.53.139.67
	Answer: a12-67.akam.net 184.26.160.67, 2600:1480:f000::43
	Answer: a18-67.akam.net 2600:1480:4800::43, 95.101.36.67
	Answer: a22-67.akam.net 23.211.61.67, 2600:1480:7800::43
	Answer: a28-67.akam.net 2600:1480:d800::43, 95.100.173.67
	Answer: a4-67.akam.net 2600:1480:9000::43, 72.246.46.67
	Answer: a6-67.akam.net 23.211.133.67, 2600:1401:1::43
11	a1-245.akam.net: 193.108.91.245	A	a1-67.akam.net (2600:1401:2::43)
12	a1-245.akam.net: 2600:1401:2::f5	AAAA	a1-67.akam.net (2600:1401:2::43)
13	a11-64.akam.net: 84.53.139.64	A	a1-67.akam.net (2600:1401:2::43)
14	a11-64.akam.net: 2600:1480:1::40	AAAA	a1-67.akam.net (2600:1401:2::43)
15	a20-65.akam.net: 95.100.175.65	A	a1-67.akam.net (2600:1401:2::43)
16	a20-65.akam.net: 2a02:26f0:67::41	AAAA	a1-67.akam.net (2600:1401:2::43)
17	a6-66.akam.net: 23.211.133.66	A	a1-67.akam.net (2600:1401:2::43)
18	a6-66.akam.net: 2600:1401:1::42	AAAA	a1-67.akam.net (2600:1401:2::43)
19	a8-67.akam.net: 2.16.40.67	A	a1-67.akam.net (2600:1401:2::43)
20	a8-67.akam.net: 2600:1403:a::43	AAAA	a1-67.akam.net (2600:1401:2::43)
21	a9-67.akam.net: 184.85.248.67	A	a1-67.akam.net (2600:1401:2::43)
22	a9-67.akam.net: 2a02:26f0:117::43	AAAA	a1-67.akam.net (2600:1401:2::43)
23	ns17.domaincontrol.com: 97.74.108.9	A	a1-245.akam.net (2600:1401:2::f5)
24	ns17.domaincontrol.com: 2603:5:21c0::9	AAAA	a1-245.akam.net (2600:1401:2::f5)
25	ns18.domaincontrol.com: 173.201.76.9	A	a1-245.akam.net (2600:1401:2::f5)
26	ns18.domaincontrol.com: 2603:5:22c0::9	AAAA	a1-245.akam.net (2600:1401:2::f5)

14. CAA - Entries

Domainname	flag	Value	∑ Queries
www.donaldtrump4president.com			1
donaldtrump4president.com	0	no CAA entry found	1
com	0	no CAA entry found	1

15. TXT - Entries

Domainname	Status	∑ Queries
donaldtrump4president.com	ok	1
www.donaldtrump4president.com		1
_acme-challenge.donaldtrump4president.com	Name Error - The domain name does not exist	1
_acme-challenge.www.donaldtrump4president.com	Name Error - The domain name does not exist	1
_acme-challenge.donaldtrump4president.com.donaldtrump4president.com	Name Error - The domain name does not exist	1
_acme-challenge.www.donaldtrump4president.com.donaldtrump4president.com	Name Error - The domain name does not exist	1
_acme-challenge.www.donaldtrump4president.com.www.donaldtrump4president.com	Name Error - The domain name does not exist	1

16. DomainService - Entries

No DomainServiceEntries entries found

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=d3316df4-447a-4920-8d25-9eb90d640d12

Last Result: https://check-your-website.server-daten.de/?q=donaldtrump4president.com - 2026-01-29 23:32:09

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

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

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