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

...

skip EDNS-Check

skip Content-Check

check links

Timeout

Checked:
18.09.2023 23:51:19

Older results

No older results found

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
2ez4.me	A	85.170.248.61 Rennes/Brittany/France (FR) - Societe Francaise Du Radiotelephone - SFR SA Hostname: 85-170-248-61.rev.numericable.fr	yes	1	0
	AAAA		yes
www.2ez4.me	A	85.170.248.61 Rennes/Brittany/France (FR) - Societe Francaise Du Radiotelephone - SFR SA Hostname: 85-170-248-61.rev.numericable.fr	yes	1	0
	AAAA		yes
*.2ez4.me	A		yes
	AAAA		yes
	CNAME	pixie.porkbun.com	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 11019, 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: 30.09.2023, 00:00:00 +, Signature-Inception: 09.09.2023, 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: me
me	1 DS RR in the parent zone found


	DS with Algorithm 8, KeyTag 45352, DigestType 2 and Digest dwjIptXXK2MhS7/1DLVFU/fgeh+l6QdL2NY8QxAthVk=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner me., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 01.10.2023, 21:00:00 +, Signature-Inception: 18.09.2023, 20:00:00 +, KeyTag 11019, Signer-Name: (root)


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


	3 DNSKEY RR found


	Public Key with Algorithm 8, KeyTag 7938, Flags 256


	Public Key with Algorithm 8, KeyTag 9681, Flags 256


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


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner me., Algorithm: 8, 1 Labels, original TTL: 3600 sec, Signature-expiration: 08.10.2023, 15:42:56 +, Signature-Inception: 17.09.2023, 14:42:56 +, KeyTag 45352, Signer-Name: me


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


	• Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 45352, DigestType 2 and Digest "dwjIptXXK2MhS7/1DLVFU/fgeh+l6QdL2NY8QxAthVk=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: 2ez4.me
2ez4.me	1 DS RR in the parent zone found


	DS with Algorithm 13, KeyTag 2371, DigestType 2 and Digest PzBcNrZl7Bsl7QW4PrpdY7stS4fkO+LaICetzcXFlXk=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner 2ez4.me., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 08.10.2023, 17:44:30 +, Signature-Inception: 17.09.2023, 16:44:30 +, KeyTag 7938, Signer-Name: me


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


	2 DNSKEY RR found


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


	Public Key with Algorithm 13, KeyTag 34505, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner 2ez4.me., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 16.11.2023, 17:30:00 +, Signature-Inception: 16.09.2023, 17:30:00 +, KeyTag 2371, Signer-Name: 2ez4.me


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


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


	RRSIG Type 1 validates the A - Result: 85.170.248.61 Validated: RRSIG-Owner 2ez4.me., Algorithm: 13, 2 Labels, original TTL: 600 sec, Signature-expiration: 19.09.2023, 22:51:49 +, Signature-Inception: 17.09.2023, 20:51:49 +, KeyTag 34505, Signer-Name: 2ez4.me


	RRSIG Type 16 validates the TXT - Result: v=spf1 mx include:_spf.porkbun.com ~all Validated: RRSIG-Owner 2ez4.me., Algorithm: 13, 2 Labels, original TTL: 300 sec, Signature-expiration: 19.09.2023, 22:51:49 +, Signature-Inception: 17.09.2023, 20:51:49 +, KeyTag 34505, Signer-Name: 2ez4.me


	CNAME-Query sends a valid NSEC RR as result with the query name "2ez4.me" equal the NSEC-owner "2ez4.me" and the NextOwner "\000.2ez4.me". So the zone confirmes the not-existence of that CNAME RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, NS, SOA, 13, MX, TXT, AAAA, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, DNSKEY, TLSA, 53, HIP, CDS, CDNSKEY, 61, 64, 65, URI, CAA Validated: RRSIG-Owner 2ez4.me., Algorithm: 13, 2 Labels, original TTL: 1800 sec, Signature-expiration: 19.09.2023, 22:51:49 +, Signature-Inception: 17.09.2023, 20:51:49 +, KeyTag 34505, Signer-Name: 2ez4.me


	Status: Good. NoData-Proof required and found.


	AAAA-Query sends a valid NSEC RR as result with the query name "2ez4.me" equal the NSEC-owner "2ez4.me" and the NextOwner "\000.2ez4.me". So the zone confirmes the not-existence of that AAAA RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, NS, SOA, 13, MX, TXT, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, DNSKEY, TLSA, 53, HIP, CDS, CDNSKEY, 61, 64, 65, URI, CAA Validated: RRSIG-Owner 2ez4.me., Algorithm: 13, 2 Labels, original TTL: 1800 sec, Signature-expiration: 19.09.2023, 22:51:49 +, Signature-Inception: 17.09.2023, 20:51:49 +, KeyTag 34505, Signer-Name: 2ez4.me


	Status: Good. NoData-Proof required and found.


	CAA-Query sends a valid NSEC RR as result with the query name "2ez4.me" equal the NSEC-owner "2ez4.me" and the NextOwner "\000.2ez4.me". So the zone confirmes the not-existence of that CAA RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, NS, SOA, 13, MX, TXT, AAAA, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, DNSKEY, TLSA, 53, HIP, CDS, CDNSKEY, 61, 64, 65, URI Validated: RRSIG-Owner 2ez4.me., Algorithm: 13, 2 Labels, original TTL: 1800 sec, Signature-expiration: 19.09.2023, 22:51:49 +, Signature-Inception: 17.09.2023, 20:51:49 +, KeyTag 34505, Signer-Name: 2ez4.me


	Status: Good. NoData-Proof required and found.

Zone: www.2ez4.me
www.2ez4.me	0 DS RR in the parent zone found


	DS-Query in the parent zone has a valid NSEC RR as result with the domain name between the NSEC-Owner "www.2ez4.me" and the NextOwner "\000.www.2ez4.me". So the parent zone confirmes the non-existence of a DS RR. Bitmap: A, 13, MX, TXT, AAAA, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, TLSA, 53, HIP, 61, 64, 65, URI, CAA


	RRSIG Type 1 validates the A - Result: 85.170.248.61 Validated: RRSIG-Owner www.2ez4.me., Algorithm: 13, 3 Labels, original TTL: 600 sec, Signature-expiration: 19.09.2023, 22:51:50 +, Signature-Inception: 17.09.2023, 20:51:50 +, KeyTag 34505, Signer-Name: 2ez4.me


	CNAME-Query sends a valid NSEC RR as result with the query name "www.2ez4.me" equal the NSEC-owner "www.2ez4.me" and the NextOwner "\000.www.2ez4.me". So the zone confirmes the not-existence of that CNAME RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, 13, MX, TXT, AAAA, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, TLSA, 53, HIP, 61, 64, 65, URI, CAA Validated: RRSIG-Owner www.2ez4.me., Algorithm: 13, 3 Labels, original TTL: 1800 sec, Signature-expiration: 19.09.2023, 22:51:50 +, Signature-Inception: 17.09.2023, 20:51:50 +, KeyTag 34505, Signer-Name: 2ez4.me


	Status: Good. NoData-Proof required and found.


	TXT-Query sends a valid NSEC RR as result with the query name "www.2ez4.me" equal the NSEC-owner "www.2ez4.me" and the NextOwner "\000.www.2ez4.me". So the zone confirmes the not-existence of that TXT RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, 13, MX, AAAA, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, TLSA, 53, HIP, 61, 64, 65, URI, CAA Validated: RRSIG-Owner www.2ez4.me., Algorithm: 13, 3 Labels, original TTL: 1800 sec, Signature-expiration: 19.09.2023, 22:51:51 +, Signature-Inception: 17.09.2023, 20:51:51 +, KeyTag 34505, Signer-Name: 2ez4.me


	Status: Good. NoData-Proof required and found.


	AAAA-Query sends a valid NSEC RR as result with the query name "www.2ez4.me" equal the NSEC-owner "www.2ez4.me" and the NextOwner "\000.www.2ez4.me". So the zone confirmes the not-existence of that AAAA RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, 13, MX, TXT, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, TLSA, 53, HIP, 61, 64, 65, URI, CAA Validated: RRSIG-Owner www.2ez4.me., Algorithm: 13, 3 Labels, original TTL: 1800 sec, Signature-expiration: 19.09.2023, 22:51:50 +, Signature-Inception: 17.09.2023, 20:51:50 +, KeyTag 34505, Signer-Name: 2ez4.me


	Status: Good. NoData-Proof required and found.


	TLSA-Query (_443._tcp.www.2ez4.me) sends a valid NSEC RR as result with the query name "_443._tcp.www.2ez4.me" equal the NSEC-owner "_443._tcp.www.2ez4.me" and the NextOwner "\000._443._tcp.www.2ez4.me". So the zone confirmes the not-existence of that TLSA RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: RRSIG, NSEC Validated: RRSIG-Owner _443._tcp.www.2ez4.me., Algorithm: 13, 5 Labels, original TTL: 1800 sec, Signature-expiration: 19.09.2023, 22:51:51 +, Signature-Inception: 17.09.2023, 20:51:51 +, KeyTag 34505, Signer-Name: 2ez4.me


	Status: Good. NoData-Proof required and found.


	CAA-Query sends a valid NSEC RR as result with the query name "www.2ez4.me" equal the NSEC-owner "www.2ez4.me" and the NextOwner "\000.www.2ez4.me". So the zone confirmes the not-existence of that CAA RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, 13, MX, TXT, AAAA, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, TLSA, 53, HIP, 61, 64, 65, URI Validated: RRSIG-Owner www.2ez4.me., Algorithm: 13, 3 Labels, original TTL: 1800 sec, Signature-expiration: 19.09.2023, 22:51:51 +, Signature-Inception: 17.09.2023, 20:51:51 +, KeyTag 34505, Signer-Name: 2ez4.me


	Status: Good. NoData-Proof required and found.

3. Name Servers

Domain	Nameserver	NS-IP
www.2ez4.me	• curitiba.ns.porkbun.com / 67m60		•
2ez4.me	• curitiba.ns.porkbun.com / 67m60	173.245.58.37 Toronto/Ontario/Canada (CA) - Cloudflare, Inc.	•
	•	2400:cb00:2049:1::adf5:3a25 San Francisco/California/United States (US) - CLOUDFLARE	•
	• fortaleza.ns.porkbun.com / 67m52	162.159.8.140 Toronto/Ontario/Canada (CA) - Cloudflare, Inc.	•
	•	2400:cb00:2049:1::a29f:88c San Francisco/California/United States (US) - CLOUDFLARE	•
	• maceio.ns.porkbun.com / 67m63	162.159.11.180 Toronto/Ontario/Canada (CA) - Cloudflare, Inc.	•
	•	2400:cb00:2049:1::a29f:bb4 San Francisco/California/United States (US) - CLOUDFLARE	•
	• salvador.ns.porkbun.com / 67m39	162.159.10.150 Toronto/Ontario/Canada (CA) - Cloudflare, Inc.	•
	•	2400:cb00:2049:1::a29f:a96 San Francisco/California/United States (US) - CLOUDFLARE	•
me	• a0.nic.me / app28.nrt1.hosts.meta.redstone.afilias-nst.info-1615580861		•
	• a2.nic.me / FRA4		•
	• b0.nic.me / app21.ams2.hosts.meta.redstone.afilias-nst.info-1615580861		•
	• b2.nic.me / FRA3		•
	• c0.nic.me / app29.nrt1.hosts.meta.redstone.afilias-nst.info-1615580861		•

4. SOA-Entries

Domain:	me
Zone-Name:	me
Primary:	a0.nic.me
Mail:	hostmaster.donuts.email
Serial:	1695073068
Refresh:	7200
Retry:	900
Expire:	1209600
TTL:	3600
num Entries:	5

Domain:	2ez4.me
Zone-Name:	2ez4.me
Primary:	curitiba.ns.porkbun.com
Mail:	dns.cloudflare.com
Serial:	2320483385
Refresh:	10000
Retry:	2400
Expire:	604800
TTL:	1800
num Entries:	8

Domain:	www.2ez4.me
Zone-Name:	2ez4.me
Primary:	curitiba.ns.porkbun.com
Mail:	dns.cloudflare.com
Serial:	2320483385
Refresh:	10000
Retry:	2400
Expire:	604800
TTL:	1800
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

Domainname	Http-Status	Sec.	G
• http://2ez4.me/ 85.170.248.61	-14	10.047	T
Timeout - The operation has timed out

• http://www.2ez4.me/ 85.170.248.61	-14	10.033	T
Timeout - The operation has timed out

• https://2ez4.me/ 85.170.248.61	-14	10.027	T
Timeout - The operation has timed out

• https://www.2ez4.me/ 85.170.248.61	-14	10.026	T
Timeout - The operation has timed out

• http://2ez4.me/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 85.170.248.61	-14	10.030	T
Timeout - The operation has timed out
Visible Content:

• http://www.2ez4.me/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 85.170.248.61	-14	10.030	T
Timeout - The operation has timed out
Visible Content:

• https://85.170.248.61/ 85.170.248.61	-14	10.030	T
Timeout - The operation has timed out

7. Comments

	1. General Results, most used to calculate the result
A	name "2ez4.me" is domain, public suffix is ".me", top-level-domain is ".me", top-level-domain-type is "country-code", Country is Montenegro, tld-manager is "Government of Montenegro", num .me-domains preloaded: 2017 (complete: 231048)
A	Good: All ip addresses are public addresses
	Warning: Only one ip address found: 2ez4.me has only one ip address.
	Warning: Only one ip address found: www.2ez4.me 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: 2ez4.me 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.2ez4.me has no ipv6 address.
A	Good: 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.
	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 2ez4.me, 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.2ez4.me, 1 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.2ez4.me
	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:: 25 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 0 Name Servers.
A	Info:: 25 Queries complete, 25 with IPv6, 0 with IPv4.
A	Good: All DNS Queries done via IPv6.
A	Info:: 4 different Name Servers found: curitiba.ns.porkbun.com, fortaleza.ns.porkbun.com, maceio.ns.porkbun.com, salvador.ns.porkbun.com, 4 Name Servers included in Delegation: curitiba.ns.porkbun.com, fortaleza.ns.porkbun.com, maceio.ns.porkbun.com, salvador.ns.porkbun.com, 4 Name Servers included in 1 Zone definitions: curitiba.ns.porkbun.com, fortaleza.ns.porkbun.com, maceio.ns.porkbun.com, salvador.ns.porkbun.com, 1 Name Servers listed in SOA.Primary: curitiba.ns.porkbun.com.
A	Good: Only one SOA.Primary Name Server found.: curitiba.ns.porkbun.com.
A	Good: SOA.Primary Name Server included in the delegation set.: curitiba.ns.porkbun.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: curitiba.ns.porkbun.com, fortaleza.ns.porkbun.com, maceio.ns.porkbun.com, salvador.ns.porkbun.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: 4 different Name Servers found
A	Good: All name servers have ipv4- and ipv6-addresses.: 4 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.: 4 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: porkbun.com
A	Good: Name servers with different Country locations found: 4 Name Servers, 2 Countries: CA, US
A	Info: Ipv4-Subnet-list: 4 Name Servers, 2 different subnets (first Byte): 162., 173., 2 different subnets (first two Bytes): 162.159., 173.245., 4 different subnets (first three Bytes): 162.159.10., 162.159.11., 162.159.8., 173.245.58.
A	Good: Name Server IPv4-addresses from different subnet found:
A	Info: IPv6-Subnet-list: 4 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.
A	Good: Nameserver supports TCP connections: 8 good Nameserver
A	Good: Nameserver supports Echo Capitalization: 8 good Nameserver
A	Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 8 good Nameserver
A	Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 8 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://2ez4.me/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 85.170.248.61	-14	Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
	http://www.2ez4.me/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 85.170.248.61	-14	Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. 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	Duration: 149193 milliseconds, 149.193 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
CN=Sectigo ECC Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, C=GB, ST=Greater Manchester				0	1	1
CN=R3, O=Let's Encrypt, C=US				0	1	1
CN=GTS CA 1P5, O=Google Trust Services LLC, C=US				0	1	1

CertSpotter-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
5864811743 leaf cert	CN=R3, O=Let's Encrypt, C=US	2023-09-17 16:30:09	2023-12-16 16:30:08	*.2ez4.me, 2ez4.me - 2 entries
5654802910 precert	CN=GTS CA 1P5, O=Google Trust Services LLC, C=US	2023-08-08 20:21:16	2023-11-06 20:21:15	*.2ez4.me, 2ez4.me - 2 entries
4844751106 leaf cert	CN=Sectigo ECC Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, C=GB, ST=Greater Manchester	2023-02-19 00:00:00	2024-02-19 23:59:59	*.2ez4.me, 2ez4.me - 2 entries

2. Source crt.sh - old and new certificates, sometimes very slow - only certificates with "not after" > of the last months are listed

Issuer				last 7 days	active	num Certs
CN=GTS CA 1P5, O=Google Trust Services LLC, C=US				0	1	3
CN=Sectigo ECC Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, C=GB, ST=Greater Manchester				0	1	1

CRT-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
10100028500 precert	CN=GTS CA 1P5, O=Google Trust Services LLC, C=US	2023-08-08 18:21:16	2023-11-06 19:21:15	*.2ez4.me, 2ez4.me 2 entries
9620726039 precert	CN=GTS CA 1P5, O=Google Trust Services LLC, C=US	2023-06-10 16:27:10	2023-09-08 16:27:09	*.2ez4.me, 2ez4.me 2 entries
9134181500 precert	CN=GTS CA 1P5, O=Google Trust Services LLC, C=US	2023-04-12 13:09:59	2023-07-11 13:09:58	*.2ez4.me, 2ez4.me 2 entries
8693478389 leaf cert	CN=Sectigo ECC Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, C=GB, ST=Greater Manchester	2023-02-18 23:00:00	2024-02-19 22:59:59	*.2ez4.me, 2ez4.me 2 entries

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: curitiba.ns.porkbun.com, fortaleza.ns.porkbun.com, maceio.ns.porkbun.com, salvador.ns.porkbun.com

QNr.	Domain	Type	NS used
1	com	NS	g.root-servers.net (2001:500:12::d0d)
	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	curitiba.ns.porkbun.com	NS	l.gtld-servers.net (2001:500:d937::30)
	Answer: ns-1328.awsdns-38.org, ns-1982.awsdns-55.co.uk, ns-199.awsdns-24.com, ns-586.awsdns-09.net
	Answer: ns-199.awsdns-24.com 205.251.192.199
3	fortaleza.ns.porkbun.com	NS	l.gtld-servers.net (2001:500:d937::30)
	Answer: ns-1328.awsdns-38.org, ns-1982.awsdns-55.co.uk, ns-199.awsdns-24.com, ns-586.awsdns-09.net
	Answer: ns-199.awsdns-24.com 205.251.192.199
4	maceio.ns.porkbun.com	NS	l.gtld-servers.net (2001:500:d937::30)
	Answer: ns-1328.awsdns-38.org, ns-1982.awsdns-55.co.uk, ns-199.awsdns-24.com, ns-586.awsdns-09.net
	Answer: ns-199.awsdns-24.com 205.251.192.199
5	salvador.ns.porkbun.com	NS	l.gtld-servers.net (2001:500:d937::30)
	Answer: ns-1328.awsdns-38.org, ns-1982.awsdns-55.co.uk, ns-199.awsdns-24.com, ns-586.awsdns-09.net
	Answer: ns-199.awsdns-24.com 205.251.192.199
6	org	NS	k.root-servers.net (2001:7fd::1)
	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
7	ns-1328.awsdns-38.org	NS	a0.org.afilias-nst.info (2001:500:e::1)
	Answer: g-ns-1065.awsdns-38.org, g-ns-1638.awsdns-38.org, g-ns-166.awsdns-38.org, g-ns-744.awsdns-38.org
	Answer: g-ns-1065.awsdns-38.org 205.251.196.41, 2600:9000:5304:2900::1
	Answer: g-ns-1638.awsdns-38.org 205.251.198.102, 2600:9000:5306:6600::1
	Answer: g-ns-166.awsdns-38.org 205.251.192.166, 2600:9000:5300:a600::1
	Answer: g-ns-744.awsdns-38.org 205.251.194.232, 2600:9000:5302:e800::1
8	uk	NS	k.root-servers.net (2001:7fd::1)
	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
9	ns-1982.awsdns-55.co.uk	NS	dns1.nic.uk (2a01:618:400::1)
	Answer: g-ns-1530.awsdns-55.co.uk, g-ns-1851.awsdns-55.co.uk, g-ns-375.awsdns-55.co.uk, g-ns-951.awsdns-55.co.uk
	Answer: g-ns-1530.awsdns-55.co.uk 205.251.197.250, 2600:9000:5305:fa00::1
	Answer: g-ns-1851.awsdns-55.co.uk 205.251.199.59, 2600:9000:5307:3b00::1
	Answer: g-ns-375.awsdns-55.co.uk 205.251.193.119, 2600:9000:5301:7700::1
	Answer: g-ns-951.awsdns-55.co.uk 205.251.195.183, 2600:9000:5303:b700::1
10	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
11	ns-586.awsdns-09.net	NS	b.gtld-servers.net (2001:503:231d::2:30)
	Answer: g-ns-1353.awsdns-09.net, g-ns-1929.awsdns-09.net, g-ns-458.awsdns-09.net, g-ns-779.awsdns-09.net
	Answer: g-ns-1353.awsdns-09.net 205.251.197.73, 2600:9000:5305:4900::1
	Answer: g-ns-1929.awsdns-09.net 205.251.199.137, 2600:9000:5307:8900::1
	Answer: g-ns-458.awsdns-09.net 205.251.193.202, 2600:9000:5301:ca00::1
	Answer: g-ns-779.awsdns-09.net 205.251.195.11, 2600:9000:5303:b00::1
12	ns-1328.awsdns-38.org: 205.251.197.48	A	g-ns-1065.awsdns-38.org (2600:9000:5304:2900::1)
13	ns-1328.awsdns-38.org: 2600:9000:5305:3000::1	AAAA	g-ns-1065.awsdns-38.org (2600:9000:5304:2900::1)
14	ns-1982.awsdns-55.co.uk: 205.251.199.190	A	g-ns-1530.awsdns-55.co.uk (2600:9000:5305:fa00::1)
15	ns-1982.awsdns-55.co.uk: 2600:9000:5307:be00::1	AAAA	g-ns-1530.awsdns-55.co.uk (2600:9000:5305:fa00::1)
16	ns-586.awsdns-09.net: 205.251.194.74	A	g-ns-1353.awsdns-09.net (2600:9000:5305:4900::1)
17	ns-586.awsdns-09.net: 2600:9000:5302:4a00::1	AAAA	g-ns-1353.awsdns-09.net (2600:9000:5305:4900::1)
18	curitiba.ns.porkbun.com: No A record found	A	ns-1328.awsdns-38.org (2600:9000:5305:3000::1)
19	curitiba.ns.porkbun.com: No AAAA record found	AAAA	ns-1328.awsdns-38.org (2600:9000:5305:3000::1)
20	fortaleza.ns.porkbun.com: No A record found	A	ns-1328.awsdns-38.org (2600:9000:5305:3000::1)
21	fortaleza.ns.porkbun.com: No AAAA record found	AAAA	ns-1328.awsdns-38.org (2600:9000:5305:3000::1)
22	maceio.ns.porkbun.com: No A record found	A	ns-1328.awsdns-38.org (2600:9000:5305:3000::1)
23	maceio.ns.porkbun.com: No AAAA record found	AAAA	ns-1328.awsdns-38.org (2600:9000:5305:3000::1)
24	salvador.ns.porkbun.com: No A record found	A	ns-1328.awsdns-38.org (2600:9000:5305:3000::1)
25	salvador.ns.porkbun.com: No AAAA record found	AAAA	ns-1328.awsdns-38.org (2600:9000:5305:3000::1)

13. CAA - Entries

Domainname	Value	∑ Queries
www.2ez4.me	no CAA entry found	1
2ez4.me	no CAA entry found	1
me	no CAA entry found	1

14. TXT - Entries

Domainname	TXT Entry	Status	∑ Queries
2ez4.me	v=spf1 mx include:_spf.porkbun.com ~all	ok	1
www.2ez4.me		ok	1
_acme-challenge.2ez4.me	7Gllv44dQ5d_tTrZpMf_51x5fCvE-hIHxgkmlm1y3TI	looks good, correct length, correct characters	1
_acme-challenge.2ez4.me	u69baSArPcRAw_DTVVM6Px6qVDzqYRw11YKnueEtjlo	looks good, correct length, correct characters	1
_acme-challenge.www.2ez4.me		Name Error - The domain name does not exist	1
_acme-challenge.2ez4.me.2ez4.me			1
_acme-challenge.www.2ez4.me.2ez4.me			1
_acme-challenge.www.2ez4.me.www.2ez4.me		Name Error - The domain name does not exist	1

15. DomainService - Entries

Type		Domain	Pref	Value	num Answers	Status
MX		2ez4.me	1	fwd1.porkbun.com	2	ok
	A			44.226.226.6	1	ok
	CNAME				0	ok
MX		2ez4.me	1	fwd2.porkbun.com	2	ok
	A			52.10.201.111	1	ok
	CNAME				0	ok

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=5f5922f7-05f7-4c4b-8ebf-c47e5a91e9a2

Last Result: https://check-your-website.server-daten.de/?q=2ez4.me - 2023-09-18 23:51:19

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

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

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