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




T

Timeout

Checked:
24.01.2023 22:53:13


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
chattur.chat
A
45.74.19.49
Las Vegas/Nevada/United States (US) - Secure Internet LLC
No Hostname found
yes
1
0

AAAA

yes


www.chattur.chat
A
45.74.19.49
Las Vegas/Nevada/United States (US) - Secure Internet LLC
No Hostname found
yes
1
0

AAAA

yes


*.chattur.chat
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 951, 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: 11.02.2023, 00:00:00 +, Signature-Inception: 21.01.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: chat
chat
1 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 45004, DigestType 2 and Digest z7rta7T5pm4Oy6Qh42jdM7iBMZp00zddOg+KiPub2lk=



1 RRSIG RR to validate DS RR found



RRSIG-Owner chat., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 06.02.2023, 17:00:00 +, Signature-Inception: 24.01.2023, 16:00:00 +, KeyTag 951, Signer-Name: (root)



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



3 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 25503, Flags 256



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



Public Key with Algorithm 8, KeyTag 50343, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner chat., Algorithm: 8, 1 Labels, original TTL: 3600 sec, Signature-expiration: 07.02.2023, 15:29:59 +, Signature-Inception: 17.01.2023, 14:29:59 +, KeyTag 45004, Signer-Name: chat



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



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

Zone: chattur.chat
chattur.chat
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 "rf87neemetfk7gkecqk8g7ojur3oaj8c" between the hashed NSEC3-owner "rf2tlreehd4rkk52qgp2n1n48pm4n92m" and the hashed NextOwner "rfspnem6sos18ntbl0fcjgnk3rih071q". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner rf2tlreehd4rkk52qgp2n1n48pm4n92m.chat., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 07.02.2023, 15:29:59 +, Signature-Inception: 17.01.2023, 14:29:59 +, KeyTag 50343, Signer-Name: chat



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "li7o7vookdaqfaf5qsb8uaaqohji4f5v" as Owner. That's the Hash of "chat" with the NextHashedOwnerName "lim63rg7n7sa2rp5b1gi26amcj7ss6k8". So that domain name is the Closest Encloser of "chattur.chat". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner li7o7vookdaqfaf5qsb8uaaqohji4f5v.chat., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 14.02.2023, 21:47:38 +, Signature-Inception: 24.01.2023, 20:47:38 +, KeyTag 50343, Signer-Name: chat



0 DNSKEY RR found




Zone: www.chattur.chat
www.chattur.chat
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.chattur.chat
  ns.confidential.domains / NS-DNS

chattur.chat
  ns.confidential.domains / NS-DNS
185.79.112.67
Amsterdam/North Holland/Netherlands (NL) - Serverius Holding B.V.


 
45.9.148.4
Amsterdam/North Holland/Netherlands (NL) - Nice IT Services Group Inc.


 
45.9.148.5
Amsterdam/North Holland/Netherlands (NL) - Nice IT Services Group Inc.


  ns.confidentialdomains.com / NS-DNS
185.79.112.67
Amsterdam/North Holland/Netherlands (NL) - Serverius Holding B.V.


 
45.9.148.4
Amsterdam/North Holland/Netherlands (NL) - Nice IT Services Group Inc.


 
45.9.148.5
Amsterdam/North Holland/Netherlands (NL) - Nice IT Services Group Inc.


  ns.confidentialdomains.net / NS-DNS
185.79.112.67
Amsterdam/North Holland/Netherlands (NL) - Serverius Holding B.V.


 
45.9.148.4
Amsterdam/North Holland/Netherlands (NL) - Nice IT Services Group Inc.


 
45.9.148.5
Amsterdam/North Holland/Netherlands (NL) - Nice IT Services Group Inc.

chat
  v0n0.nic.chat / app21.nrt1.hosts.meta.redstone.afilias-nst.info-1615580861


  v0n1.nic.chat / app14.ams2.hosts.meta.redstone.afilias-nst.info-1615580861


  v0n2.nic.chat / app9.nrt1.hosts.meta.redstone.afilias-nst.info-1615580861


  v0n3.nic.chat / app18.ams2.hosts.meta.redstone.afilias-nst.info-1615580861


  v2n0.nic.chat / FRA6


  v2n1.nic.chat / FRA6


4. SOA-Entries


Domain:chat
Zone-Name:chat
Primary:v0n0.nic.chat
Mail:hostmaster.donuts.email
Serial:1674596706
Refresh:7200
Retry:900
Expire:1209600
TTL:3600
num Entries:6


Domain:chattur.chat
Zone-Name:chattur.chat
Primary:ns.confidential.domains
Mail:hostmaster.dendrite.network
Serial:2023012400
Refresh:3600
Retry:600
Expire:1209600
TTL:3600
num Entries:9


Domain:www.chattur.chat
Zone-Name:chattur.chat
Primary:ns.confidential.domains
Mail:hostmaster.dendrite.network
Serial:2023012400
Refresh:3600
Retry:600
Expire:1209600
TTL:3600
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://chattur.chat/
45.74.19.49
-14

10.064
T
Timeout - The operation has timed out

• http://www.chattur.chat/
45.74.19.49
-14

10.044
T
Timeout - The operation has timed out

• https://chattur.chat/
45.74.19.49
-14

10.040
T
Timeout - The operation has timed out

• https://www.chattur.chat/
45.74.19.49
-14

10.054
T
Timeout - The operation has timed out

• http://chattur.chat/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
45.74.19.49
-14

10.036
T
Timeout - The operation has timed out
Visible Content:

• http://www.chattur.chat/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
45.74.19.49
-14

10.036
T
Timeout - The operation has timed out
Visible Content:

• https://45.74.19.49/
45.74.19.49
-14

10.040
T
Timeout - The operation has timed out

7. Comments


1. General Results, most used to calculate the result

Aname "chattur.chat" is domain, public suffix is ".chat", top-level-domain is ".chat", top-level-domain-type is "generic", tld-manager is "Binky Moon, LLC", num .chat-domains preloaded: 52 (complete: 216710)
AGood: All ip addresses are public addresses
Warning: Only one ip address found: chattur.chat has only one ip address.
Warning: Only one ip address found: www.chattur.chat 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: chattur.chat 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.chattur.chat has no ipv6 address.
AGood: No asked Authoritative Name Server had a timeout
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
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 chattur.chat, 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.chattur.chat, 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.chattur.chat

2. Header-Checks (alpha, started 2022-10-23, may be buggy / incomplete)

U

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

3. DNS- and NameServer - Checks

AInfo:: 6 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 3 Name Servers.
AInfo:: 6 Queries complete, 6 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
AGood: Some ip addresses of name servers found with the minimum of two DNS Queries. One to find the TLD-Zone, one to ask the TLD-Zone.ns.confidential.domains (185.79.112.67, 45.9.148.4, 45.9.148.5), ns.confidentialdomains.com (185.79.112.67, 45.9.148.4, 45.9.148.5), ns.confidentialdomains.net (185.79.112.67, 45.9.148.4, 45.9.148.5)
AGood (1 - 3.0):: An average of 2.0 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 3 different Name Servers found: ns.confidential.domains, ns.confidentialdomains.com, ns.confidentialdomains.net, 3 Name Servers included in Delegation: ns.confidential.domains, ns.confidentialdomains.com, ns.confidentialdomains.net, 3 Name Servers included in 1 Zone definitions: ns.confidential.domains, ns.confidentialdomains.com, ns.confidentialdomains.net, 1 Name Servers listed in SOA.Primary: ns.confidential.domains.
AGood: Only one SOA.Primary Name Server found.: ns.confidential.domains.
AGood: SOA.Primary Name Server included in the delegation set.: ns.confidential.domains.
AGood: Consistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Ordered list of name servers: ns.confidential.domains, ns.confidentialdomains.com, ns.confidentialdomains.net
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.
AGood: Minimal 2 different name servers (public suffix and public ip address) found: 3 different Name Servers found
Warning: No Name Server IPv6 address found. IPv6 is the future, so your name servers should be visible via IPv6.: 3 different Name Servers found
AGood: Name servers with different Top Level Domains / Public Suffix List entries found: 3 Name Servers, 3 Top Level Domains: com, net, domains
AGood: Name Servers with different domain names found.: 3 different Domains found
Warning: All Name Servers from the same Country / IP location.: 3 Name Servers, 1 Countries: NL
AInfo: Ipv4-Subnet-list: 9 Name Servers, 2 different subnets (first Byte): 185., 45., 2 different subnets (first two Bytes): 185.79., 45.9., 2 different subnets (first three Bytes): 185.79.112., 45.9.148.
AGood: Name Server IPv4-addresses from different subnet found:
AGood: Nameserver supports TCP connections: 9 good Nameserver
AInfo: Nameserver mit different domain names found. May be a problem with DNS-Updates
AGood: Nameserver supports Echo Capitalization: 9 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 9 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 9 good Nameserver
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://chattur.chat/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 45.74.19.49
-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.chattur.chat/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 45.74.19.49
-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.
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: 144586 milliseconds, 144.586 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)

No CertSpotter - CT-Log entries found


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. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: ns.confidential.domains, ns.confidentialdomains.com, ns.confidentialdomains.net

QNr.DomainTypeNS used
1
domains
NS
k.root-servers.net (2001:7fd::1)

Answer: v0n0.nic.domains, v0n1.nic.domains, v0n2.nic.domains, v0n3.nic.domains, v2n0.nic.domains, v2n1.nic.domains
2
ns.confidential.domains: 185.79.112.67, 45.9.148.4, 45.9.148.5
NS
v0n0.nic.domains (2a01:8840:22::51)
3
com
NS
b.root-servers.net (2001:500:200::b)

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
4
ns.confidentialdomains.com: 185.79.112.67, 45.9.148.4, 45.9.148.5
NS
a.gtld-servers.net (2001:503:a83e::2:30)
5
net
NS
b.root-servers.net (2001:500:200::b)

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
6
ns.confidentialdomains.net: 185.79.112.67, 45.9.148.4, 45.9.148.5
NS
a.gtld-servers.net (2001:503:a83e::2:30)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.chattur.chat
0

no CAA entry found
1
0
chattur.chat
0

no CAA entry found
1
0
chat
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
chattur.chat

ok
1
0
www.chattur.chat

ok
1
0
_acme-challenge.chattur.chat

Name Error - The domain name does not exist
1
0
_acme-challenge.www.chattur.chat

Name Error - The domain name does not exist
1
0
_acme-challenge.chattur.chat.chattur.chat

Name Error - The domain name does not exist
1
0
_acme-challenge.www.chattur.chat.chattur.chat

Name Error - The domain name does not exist
1
0
_acme-challenge.www.chattur.chat.www.chattur.chat

Name Error - The domain name does not exist
1
0


15. DomainService - Entries (SSHFP Check is new - 2022-09-24, may be incomplete, alpha, some results are required)

No DomainServiceEntries entries found



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=e9676b04-9e4f-4c21-a642-8e3ed46a03c7


Last Result: https://check-your-website.server-daten.de/?q=chattur.chat - 2023-01-24 22:53:13


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

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

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