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

...

skip EDNS-Check

skip Content-Check

check links

Private IP-Address found

Checked:
01.10.2024 10:59:23

Older results

No older results found

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
trjnhthang0912.click	A	192.168.47.111 No Hostname found	yes	1	0
	AAAA		yes
www.trjnhthang0912.click	A	192.168.47.111 No Hostname found	yes	1	0
	AAAA		yes
*.trjnhthang0912.click	A	172.67.221.31	yes
	A	104.21.53.248	yes
	AAAA	2606:4700:3034::ac43:dd1f	yes
	AAAA	2606:4700:3034::6815:35f8	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 20038, Flags 256


	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: 10.10.2024, 00:00:00 +, Signature-Inception: 19.09.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: click
click	1 DS RR in the parent zone found


	DS with Algorithm 13, KeyTag 65517, DigestType 2 and Digest 0JosFMQ4JjTtzPljT7MukVEeHmQvPDhGi6JAfx0brSQ=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner click., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 13.10.2024, 20:00:00 +, Signature-Inception: 30.09.2024, 19:00:00 +, KeyTag 20038, Signer-Name: (root)


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


	2 DNSKEY RR found


	Public Key with Algorithm 13, KeyTag 29054, Flags 256


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


	2 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner click., Algorithm: 13, 1 Labels, original TTL: 900 sec, Signature-expiration: 31.10.2024, 07:55:28 +, Signature-Inception: 01.10.2024, 07:55:28 +, KeyTag 29054, Signer-Name: click


	RRSIG-Owner click., Algorithm: 13, 1 Labels, original TTL: 900 sec, Signature-expiration: 31.10.2024, 07:55:28 +, Signature-Inception: 01.10.2024, 07:55:28 +, KeyTag 65517, Signer-Name: click


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


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


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

Zone: trjnhthang0912.click
trjnhthang0912.click	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 "nb6rq5b1u64a16f5gmeri2jm684kd3ph" between the hashed NSEC3-owner "nb1grtkupbqm5d2nsmesed8hccm36td0" and the hashed NextOwner "nbgagaj3ea5hi02a6e3esegibml9e77h". So the parent zone confirmes the not-existence of a DS RR. Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner nb1grtkupbqm5d2nsmesed8hccm36td0.click., Algorithm: 13, 2 Labels, original TTL: 300 sec, Signature-expiration: 31.10.2024, 07:55:28 +, Signature-Inception: 01.10.2024, 07:55:28 +, KeyTag 29054, Signer-Name: click


	DS-Query in the parent zone sends valid NSEC3 RR with the Hash "rd7lbu3l25g55gfaiobi8keaoloe7ibj" as Owner. That's the Hash of "click" with the NextHashedOwnerName "rdqiv33q7umhulqko3sser1gsm5kpjet". So that domain name is the Closest Encloser of "trjnhthang0912.click". Opt-Out: True. Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner rd7lbu3l25g55gfaiobi8keaoloe7ibj.click., Algorithm: 13, 2 Labels, original TTL: 300 sec, Signature-expiration: 31.10.2024, 07:55:28 +, Signature-Inception: 01.10.2024, 07:55:28 +, KeyTag 29054, Signer-Name: click


	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 trjnhthang0912.click., Algorithm: 13, 2 Labels, original TTL: 3600 sec, Signature-expiration: 06.11.2024, 12:25:17 +, Signature-Inception: 06.09.2024, 12:25:17 +, KeyTag 2371, Signer-Name: trjnhthang0912.click


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


	Error: DNSKEY 2371 signs DNSKEY RRset, but no confirming DS RR in the parent zone found. No chain of trust created.


	RRSIG Type 1 validates the A - Result: 192.168.47.111 Validated: RRSIG-Owner trjnhthang0912.click., Algorithm: 13, 2 Labels, original TTL: 300 sec, Signature-expiration: 02.10.2024, 09:59:32 +, Signature-Inception: 30.09.2024, 07:59:32 +, KeyTag 34505, Signer-Name: trjnhthang0912.click


	CNAME-Query sends a valid NSEC RR as result with the query name "trjnhthang0912.click" equal the NSEC-owner "trjnhthang0912.click" and the NextOwner "\000.trjnhthang0912.click". 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 trjnhthang0912.click., Algorithm: 13, 2 Labels, original TTL: 1800 sec, Signature-expiration: 02.10.2024, 09:59:32 +, Signature-Inception: 30.09.2024, 07:59:32 +, KeyTag 34505, Signer-Name: trjnhthang0912.click


	Status: Good. NoData-Proof required and found.


	TXT-Query sends a valid NSEC RR as result with the query name "trjnhthang0912.click" equal the NSEC-owner "trjnhthang0912.click" and the NextOwner "\000.trjnhthang0912.click". 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, NS, SOA, 13, MX, AAAA, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, DNSKEY, TLSA, 53, HIP, CDS, CDNSKEY, 61, 64, 65, URI, CAA Validated: RRSIG-Owner trjnhthang0912.click., Algorithm: 13, 2 Labels, original TTL: 1800 sec, Signature-expiration: 02.10.2024, 09:59:32 +, Signature-Inception: 30.09.2024, 07:59:32 +, KeyTag 34505, Signer-Name: trjnhthang0912.click


	Status: Good. NoData-Proof required and found.


	AAAA-Query sends a valid NSEC RR as result with the query name "trjnhthang0912.click" equal the NSEC-owner "trjnhthang0912.click" and the NextOwner "\000.trjnhthang0912.click". 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 trjnhthang0912.click., Algorithm: 13, 2 Labels, original TTL: 1800 sec, Signature-expiration: 02.10.2024, 09:59:32 +, Signature-Inception: 30.09.2024, 07:59:32 +, KeyTag 34505, Signer-Name: trjnhthang0912.click


	Status: Good. NoData-Proof required and found.


	TLSA-Query (_443._tcp.trjnhthang0912.click) sends a valid NSEC RR as result with the query name "_443._tcp.trjnhthang0912.click" equal the NSEC-owner "_443._tcp.trjnhthang0912.click" and the NextOwner "\000._443._tcp.trjnhthang0912.click". 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: A, 13, MX, TXT, AAAA, LOC, SRV, NAPTR, CERT, SSHFP, RRSIG, NSEC, 53, HIP, 61, 64, 65, URI, CAA Validated: RRSIG-Owner _443._tcp.trjnhthang0912.click., Algorithm: 13, 4 Labels, original TTL: 1800 sec, Signature-expiration: 02.10.2024, 09:59:32 +, Signature-Inception: 30.09.2024, 07:59:32 +, KeyTag 34505, Signer-Name: trjnhthang0912.click


	Status: Good. NoData-Proof required and found.


	CAA-Query sends a valid NSEC RR as result with the query name "trjnhthang0912.click" equal the NSEC-owner "trjnhthang0912.click" and the NextOwner "\000.trjnhthang0912.click". 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 trjnhthang0912.click., Algorithm: 13, 2 Labels, original TTL: 1800 sec, Signature-expiration: 02.10.2024, 09:59:32 +, Signature-Inception: 30.09.2024, 07:59:32 +, KeyTag 34505, Signer-Name: trjnhthang0912.click


	Status: Good. NoData-Proof required and found.

Zone: www.trjnhthang0912.click
www.trjnhthang0912.click	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.trjnhthang0912.click" and the NextOwner "\000.www.trjnhthang0912.click". 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: 192.168.47.111 Validated: RRSIG-Owner www.trjnhthang0912.click., Algorithm: 13, 3 Labels, original TTL: 300 sec, Signature-expiration: 02.10.2024, 09:59:33 +, Signature-Inception: 30.09.2024, 07:59:33 +, KeyTag 34505, Signer-Name: trjnhthang0912.click


	CNAME-Query sends a valid NSEC RR as result with the query name "www.trjnhthang0912.click" equal the NSEC-owner "www.trjnhthang0912.click" and the NextOwner "\000.www.trjnhthang0912.click". 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.trjnhthang0912.click., Algorithm: 13, 3 Labels, original TTL: 1800 sec, Signature-expiration: 02.10.2024, 09:59:33 +, Signature-Inception: 30.09.2024, 07:59:33 +, KeyTag 34505, Signer-Name: trjnhthang0912.click


	Status: Good. NoData-Proof required and found.


	TXT-Query sends a valid NSEC RR as result with the query name "www.trjnhthang0912.click" equal the NSEC-owner "www.trjnhthang0912.click" and the NextOwner "\000.www.trjnhthang0912.click". 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.trjnhthang0912.click., Algorithm: 13, 3 Labels, original TTL: 1800 sec, Signature-expiration: 02.10.2024, 09:59:33 +, Signature-Inception: 30.09.2024, 07:59:33 +, KeyTag 34505, Signer-Name: trjnhthang0912.click


	Status: Good. NoData-Proof required and found.


	AAAA-Query sends a valid NSEC RR as result with the query name "www.trjnhthang0912.click" equal the NSEC-owner "www.trjnhthang0912.click" and the NextOwner "\000.www.trjnhthang0912.click". 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.trjnhthang0912.click., Algorithm: 13, 3 Labels, original TTL: 1800 sec, Signature-expiration: 02.10.2024, 09:59:33 +, Signature-Inception: 30.09.2024, 07:59:33 +, KeyTag 34505, Signer-Name: trjnhthang0912.click


	Status: Good. NoData-Proof required and found.


	TLSA-Query (_443._tcp.www.trjnhthang0912.click) sends a valid NSEC RR as result with the query name "_443._tcp.www.trjnhthang0912.click" equal the NSEC-owner "_443._tcp.www.trjnhthang0912.click" and the NextOwner "\000._443._tcp.www.trjnhthang0912.click". 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, 128 Validated: RRSIG-Owner _443._tcp.www.trjnhthang0912.click., Algorithm: 13, 5 Labels, original TTL: 1800 sec, Signature-expiration: 02.10.2024, 09:59:33 +, Signature-Inception: 30.09.2024, 07:59:33 +, KeyTag 34505, Signer-Name: trjnhthang0912.click


	Status: Good. NoData-Proof required and found.


	CAA-Query sends a valid NSEC RR as result with the query name "www.trjnhthang0912.click" equal the NSEC-owner "www.trjnhthang0912.click" and the NextOwner "\000.www.trjnhthang0912.click". 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.trjnhthang0912.click., Algorithm: 13, 3 Labels, original TTL: 1800 sec, Signature-expiration: 02.10.2024, 09:59:33 +, Signature-Inception: 30.09.2024, 07:59:33 +, KeyTag 34505, Signer-Name: trjnhthang0912.click


	Status: Good. NoData-Proof required and found.

3. Name Servers

Domain	Nameserver	NS-IP
www.trjnhthang0912.click	• ben.ns.cloudflare.com / 67m50		•
trjnhthang0912.click	• ben.ns.cloudflare.com / 67m79	108.162.193.103 Toronto/Ontario/Canada (CA) - Cloudflare, Inc.	•
	•	172.64.33.103 Toronto/Ontario/Canada (CA) - Cloudflare, Inc.	•
	•	173.245.59.103 Toronto/Ontario/Canada (CA) - Cloudflare, Inc.	•
	•	2606:4700:58::adf5:3b67 Montreal/Quebec/Canada (CA) - Cloudflare, Inc.	•
	•	2803:f800:50::6ca2:c167 San José/Provincia de San José/Costa Rica (CR) - Cloudflare, Inc.	•
	•	2a06:98c1:50::ac40:2167 London/England/United Kingdom (GB) - Cloudflare, Inc.	•
	• isabel.ns.cloudflare.com / 67m49	108.162.194.104 Toronto/Ontario/Canada (CA) - Cloudflare, Inc.	•
	•	162.159.38.104 Los Angeles/California/United States (US) - Cloudflare, Inc.	•
	•	172.64.34.104 Toronto/Ontario/Canada (CA) - Cloudflare, Inc.	•
	•	2606:4700:50::a29f:2668 Montreal/Quebec/Canada (CA) - Cloudflare, Inc.	•
	•	2803:f800:50::6ca2:c268 San José/Provincia de San José/Costa Rica (CR) - Cloudflare, Inc.	•
	•	2a06:98c1:50::ac40:2268 London/England/United Kingdom (GB) - Cloudflare, Inc.	•
click	• ns.trs-dns.com
	• ns01.trs-dns.com / fra01.dns1.tucows.net		•
	• ns01.trs-dns.info / FRA1		•
	• ns01.trs-dns.net / fra01.dns2.tucows.net		•
	• ns01.trs-dns.org / CDG1		•

4. SOA-Entries

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

Domain:	click
Zone-Name:	click
Primary:	ns.trs-dns.com
Mail:	trs-ops.tucows.com
Serial:	1727772850
Refresh:	1800
Retry:	900
Expire:	604800
TTL:	300
num Entries:	4

Domain:	trjnhthang0912.click
Zone-Name:	trjnhthang0912.click
Primary:	ben.ns.cloudflare.com
Mail:	dns.cloudflare.com
Serial:	2353256685
Refresh:	10000
Retry:	2400
Expire:	604800
TTL:	1800
num Entries:	12

Domain:	www.trjnhthang0912.click
Zone-Name:	trjnhthang0912.click
Primary:	ben.ns.cloudflare.com
Mail:	dns.cloudflare.com
Serial:	2353256685
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	redirect	Sec.	G
•

7. Comments

	1. General Results, most used to calculate the result
A	name "trjnhthang0912.click" is domain, public suffix is ".click", top-level-domain is ".click", top-level-domain-type is "generic", tld-manager is "Uniregistry, Corp.", num .click-domains preloaded: 75 (complete: 245733)
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.
Y	trjnhthang0912.click	192.168.47.111	Warning: Private ip address found. No connection possible. There are two types of ip addresses: Worldwide unique, global addresses and private addresses. If you want that other users connect your domain, your domain must have minimal one A- (ipv4) or AAAA- (ipv6) entry with a global ip address. Check https://en.wikipedia.org/wiki/Private_network to understand the details: 192.168.0.0 to 192.168.255.255: Class C - 256 private net, every with 256 addresses
Y	www.trjnhthang0912.click	192.168.47.111	Warning: Private ip address found. No connection possible. There are two types of ip addresses: Worldwide unique, global addresses and private addresses. If you want that other users connect your domain, your domain must have minimal one A- (ipv4) or AAAA- (ipv6) entry with a global ip address. Check https://en.wikipedia.org/wiki/Private_network to understand the details: 192.168.0.0 to 192.168.255.255: Class C - 256 private net, every with 256 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.trjnhthang0912.click
	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
A	Info:: 7 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
A	Info:: 7 Queries complete, 7 with IPv6, 0 with IPv4.
A	Good: 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.
A	Info:: 2 different Name Servers found: ben.ns.cloudflare.com, isabel.ns.cloudflare.com, 2 Name Servers included in Delegation: ben.ns.cloudflare.com, isabel.ns.cloudflare.com, 2 Name Servers included in 1 Zone definitions: ben.ns.cloudflare.com, isabel.ns.cloudflare.com, 1 Name Servers listed in SOA.Primary: ben.ns.cloudflare.com.
A	Good: Only one SOA.Primary Name Server found.: ben.ns.cloudflare.com.
A	Good: SOA.Primary Name Server included in the delegation set.: ben.ns.cloudflare.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: ben.ns.cloudflare.com, isabel.ns.cloudflare.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
	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: cloudflare.com
A	Good: Name servers with different Country locations found: 2 Name Servers, 4 Countries: CA, CR, GB, US
A	Info: 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.
A	Good: Name Server IPv4-addresses from different subnet found:
A	Info: 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:
A	Good: Name Server IPv6 addresses from different subnets found.
A	Good: Nameserver supports TCP connections: 12 good Nameserver
A	Good: Nameserver supports Echo Capitalization: 12 good Nameserver
A	Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 12 good Nameserver
A	Good: 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: ns.trs-dns.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.
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
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: 79916 milliseconds, 79.916 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=WE1, O=Google Trust Services, C=US				0	2	2
CN=Sectigo ECC Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, C=GB, ST=Greater Manchester				0	1	1

CertSpotter-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
8157709337 precert	CN=WE1, O=Google Trust Services, C=US	2024-09-11 08:50:26	2024-12-10 08:50:25	*.trjnhthang0912.click, trjnhthang0912.click - 2 entries
7707813476 leaf cert	CN=WE1, O=Google Trust Services, C=US	2024-07-14 09:21:50	2024-10-12 09:21:49	*.trjnhthang0912.click, trjnhthang0912.click - 2 entries
7707824738 leaf cert	CN=Sectigo ECC Domain Validation Secure Server CA, O=Sectigo Limited, L=Salford, C=GB, ST=Greater Manchester	2024-07-14 00:00:00	2025-07-14 23:59:59	*.trjnhthang0912.click, trjnhthang0912.click - 2 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.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: ben.ns.cloudflare.com, isabel.ns.cloudflare.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	ben.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	isabel.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	ben.ns.cloudflare.com: 108.162.193.103, 172.64.33.103, 173.245.59.103	A	ns3.cloudflare.com (2400:cb00:2049:1::a29f:21)
5	ben.ns.cloudflare.com: 2606:4700:58::adf5:3b67, 2803:f800:50::6ca2:c167, 2a06:98c1:50::ac40:2167	AAAA	ns3.cloudflare.com (2400:cb00:2049:1::a29f:21)
6	isabel.ns.cloudflare.com: 108.162.194.104, 162.159.38.104, 172.64.34.104	A	ns3.cloudflare.com (2400:cb00:2049:1::a29f:21)
7	isabel.ns.cloudflare.com: 2606:4700:50::a29f:2668, 2803:f800:50::6ca2:c268, 2a06:98c1:50::ac40:2268	AAAA	ns3.cloudflare.com (2400:cb00:2049:1::a29f:21)

14. CAA - Entries

Domainname	Value	∑ Queries
www.trjnhthang0912.click	no CAA entry found	1
trjnhthang0912.click	no CAA entry found	1
click	no CAA entry found	1

15. TXT - Entries

Domainname	Status	∑ Queries
trjnhthang0912.click	ok	1
www.trjnhthang0912.click	ok	1
_acme-challenge.trjnhthang0912.click	missing entry or wrong length	1
_acme-challenge.www.trjnhthang0912.click	Name Error - The domain name does not exist	1
_acme-challenge.trjnhthang0912.click.trjnhthang0912.click	perhaps wrong	1
_acme-challenge.www.trjnhthang0912.click.trjnhthang0912.click	perhaps wrong	1
_acme-challenge.www.trjnhthang0912.click.www.trjnhthang0912.click	Name Error - The domain name does not exist	1

16. DomainService - Entries

No DomainServiceEntries entries found

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=46c28516-5d41-499b-a379-19e009e7df82

Last Result: https://check-your-website.server-daten.de/?q=trjnhthang0912.click - 2024-10-01 10:59:23

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

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