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




V

Connect failure - perhaps firewall

Checked:
10.07.2024 16:41:17


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
pyclbnhh.top
A

yes
1
0

AAAA

yes


www.pyclbnhh.top
A
38.49.46.78
Los Angeles/California/United States (US) - Cogent Communications
No Hostname found
yes
1
0

AAAA

yes


*.pyclbnhh.top
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 5613, Flags 256



Public Key with Algorithm 8, KeyTag 20038, 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: 22.07.2024, 00:00:00 +, Signature-Inception: 01.07.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: top
top
2 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 56384, DigestType 2 and Digest ujeMWRNATsZU31RPUZsPsofhQNZNrF1Z40mWI5PBeUU=



DS with Algorithm 8, KeyTag 26780, DigestType 2 and Digest XW54ae6OO1NqYX3olILd0dy52527GsM9btNR4soJWxs=



1 RRSIG RR to validate DS RR found



RRSIG-Owner top., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 23.07.2024, 05:00:00 +, Signature-Inception: 10.07.2024, 04: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 8, KeyTag 26780, Flags 257 (SEP = Secure Entry Point)



Public Key with Algorithm 8, KeyTag 51711, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner top., Algorithm: 8, 1 Labels, original TTL: 3600 sec, Signature-expiration: 18.07.2024, 15:19:06 +, Signature-Inception: 04.07.2024, 13:49:06 +, KeyTag 26780, Signer-Name: top



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



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

Zone: pyclbnhh.top
pyclbnhh.top
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 "ggttdn8b9agftnu189h14bbrm4dq2lee" between the hashed NSEC3-owner "ggttdn8b9agftnu189h14bbrm4dq2lee" and the hashed NextOwner "ggttnlmrd1oe59c0u3bbibt5sqsrlfq2". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: No Bitmap? Validated: RRSIG-Owner ggttdn8b9agftnu189h14bbrm4dq2lee.top., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 24.07.2024, 10:38:58 +, Signature-Inception: 10.07.2024, 09:08:58 +, KeyTag 51711, Signer-Name: top



0 DNSKEY RR found




Zone: www.pyclbnhh.top
www.pyclbnhh.top
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.pyclbnhh.top
  ns1.dnsowl.com / 67m62

pyclbnhh.top
  ns1.dnsowl.com / 67m42
162.159.26.136
Toronto/Ontario/Canada (CA) - Cloudflare, Inc.


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


 
2400:cb00:2049:1::a29f:1a88
San Francisco/California/United States (US) - CLOUDFLARE


 
2400:cb00:2049:1::a29f:1bad
San Francisco/California/United States (US) - CLOUDFLARE


  ns2.dnsowl.com / 67m43
162.159.26.49
Toronto/Ontario/Canada (CA) - Cloudflare, Inc.


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


 
2400:cb00:2049:1::a29f:1a31
San Francisco/California/United States (US) - CLOUDFLARE


 
2400:cb00:2049:1::a29f:1b82
San Francisco/California/United States (US) - CLOUDFLARE


  ns3.dnsowl.com / 67m43
162.159.26.234
Toronto/Ontario/Canada (CA) - Cloudflare, Inc.


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


 
2400:cb00:2049:1::a29f:1aea
San Francisco/California/United States (US) - CLOUDFLARE


 
2400:cb00:2049:1::a29f:1b62
San Francisco/California/United States (US) - CLOUDFLARE

top
  a.zdnscloud.com


  b.zdnscloud.com


  c.zdnscloud.com


  d.zdnscloud.com


T  f.zdnscloud.com


  g.zdnscloud.com


  i.zdnscloud.com


  j.zdnscloud.com


4. SOA-Entries


Domain:top
Zone-Name:top
Primary:a.zdnscloud.com
Mail:td_dns_gtld.knet.cn
Serial:1390229130
Refresh:600
Retry:3600
Expire:1209600
TTL:3600
num Entries:5


Domain:top
Zone-Name:top
Primary:a.zdnscloud.com
Mail:td_dns_gtld.knet.cn
Serial:1390229131
Refresh:600
Retry:3600
Expire:1209600
TTL:3600
num Entries:3


Domain:pyclbnhh.top
Zone-Name:pyclbnhh.top
Primary:ns1.dnsowl.com
Mail:hostmaster.dnsowl.com
Serial:1720622214
Refresh:7200
Retry:1800
Expire:1209600
TTL:600
num Entries:12


Domain:www.pyclbnhh.top
Zone-Name:pyclbnhh.top
Primary:ns1.dnsowl.com
Mail:hostmaster.dnsowl.com
Serial:1720622214
Refresh:7200
Retry:1800
Expire:1209600
TTL:600
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://www.pyclbnhh.top/
38.49.46.78 No GZip used - 517 / 615 - 84.07 % possible
200

Html is minified: 130.57 %
0.347
H
Server: nginx/1.26.1
Date: Wed, 10 Jul 2024 14:42:47 GMT
Connection: close
ETag: "6655dbe7-267"
Accept-Ranges: bytes
Content-Type: text/html
Content-Length: 615
Last-Modified: Tue, 28 May 2024 13:28:07 GMT

• https://www.pyclbnhh.top/
38.49.46.78
-16

1.530
V
UnknownError - Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. [::ffff:38.49.46.78]:443 (38.49.46.78:443)

• http://www.pyclbnhh.top/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
38.49.46.78
Inline-JavaScript (∑/total): 0/0 Inline-CSS (∑/total): 0/0
404

Html is minified: 110.07 %
0.360
A
Not Found
Visible Content:
Server: nginx/1.26.1
Date: Wed, 10 Jul 2024 14:42:49 GMT
Connection: close
Content-Type: text/html
Content-Length: 153

• https://38.49.46.78/
38.49.46.78
-16

1.530
V
UnknownError - Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. [::ffff:38.49.46.78]:443 (38.49.46.78:443)

7. Comments


1. General Results, most used to calculate the result

Aname "pyclbnhh.top" is domain, public suffix is ".top", top-level-domain is ".top", top-level-domain-type is "generic", tld-manager is "Jiangsu Bangning Science & Technology Co.,Ltd.", num .top-domains preloaded: 481 (complete: 245733)
AGood: All ip addresses are public addresses
Warning: Only one ip address found: www.pyclbnhh.top 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: www.pyclbnhh.top has no ipv6 address.
AGood: No asked Authoritative Name Server had a timeout
AGood - only one version with Http-Status 200
AGood: No cookie sent via http.
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
AGood: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):0 complete Content-Type - header (2 urls)
http://www.pyclbnhh.top/ 38.49.46.78


Url with incomplete Content-Type - header - missing charset
http://www.pyclbnhh.top/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 38.49.46.78


Url with incomplete Content-Type - header - missing charset
HFatal error: No https - result with http-status 200, no encryption
HFatal error: http result with http-status 200, no encryption. Add a redirect http ⇒ https, so every connection is secure. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop.
Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain www.pyclbnhh.top, 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.pyclbnhh.top

2. Header-Checks (Cross-Origin-* headers are alpha - started 2024-06-05)

U

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

3. DNS- and NameServer - Checks

AInfo:: 2 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 3 Name Servers.
AInfo:: 2 Queries complete, 2 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.ns1.dnsowl.com (162.159.26.136, 162.159.27.173, 2400:cb00:2049:1::a29f:1a88, 2400:cb00:2049:1::a29f:1bad), ns2.dnsowl.com (162.159.26.49, 162.159.27.130, 2400:cb00:2049:1::a29f:1a31, 2400:cb00:2049:1::a29f:1b82), ns3.dnsowl.com (162.159.26.234, 162.159.27.98, 2400:cb00:2049:1::a29f:1aea, 2400:cb00:2049:1::a29f:1b62)
AGood (1 - 3.0):: An average of 0.7 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 3 different Name Servers found: ns1.dnsowl.com, ns2.dnsowl.com, ns3.dnsowl.com, 3 Name Servers included in Delegation: ns1.dnsowl.com, ns2.dnsowl.com, ns3.dnsowl.com, 3 Name Servers included in 1 Zone definitions: ns1.dnsowl.com, ns2.dnsowl.com, ns3.dnsowl.com, 1 Name Servers listed in SOA.Primary: ns1.dnsowl.com.
AGood: Only one SOA.Primary Name Server found.: ns1.dnsowl.com.
AGood: SOA.Primary Name Server included in the delegation set.: ns1.dnsowl.com.
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: ns1.dnsowl.com, ns2.dnsowl.com, ns3.dnsowl.com
AGood: All Name Server Domain Names have a Public Suffix.
AGood: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
AGood: All Name Server ip addresses are public.
AGood: Minimal 2 different name servers (public suffix and public ip address) found: 3 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.: 3 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: dnsowl.com
AGood: Name servers with different Country locations found: 3 Name Servers, 2 Countries: CA, US
AInfo: Ipv4-Subnet-list: 6 Name Servers, 1 different subnets (first Byte): 162., 1 different subnets (first two Bytes): 162.159., 2 different subnets (first three Bytes): 162.159.26., 162.159.27.
AGood: Name Server IPv4-addresses from different subnet found:
AInfo: IPv6-Subnet-list: 6 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.
AGood: Nameserver supports TCP connections: 12 good Nameserver
AGood: Nameserver supports Echo Capitalization: 12 good Nameserver
XNameserver Timeout checking Echo Capitalization: f.zdnscloud.com
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 12 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 6 good Nameserver
Nameserver doesn't pass all EDNS-Checks: f.zdnscloud.com: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: g.zdnscloud.com: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns1.dnsowl.com: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok (67m62). COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns1.dnsowl.com / 162.159.26.136: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok (67m42). COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns1.dnsowl.com / 162.159.27.173: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok (67m33). COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns2.dnsowl.com / 162.159.26.49: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok (67m43). COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns2.dnsowl.com / 162.159.27.130: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok (67m41). COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns3.dnsowl.com / 162.159.26.234: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok (67m43). COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns3.dnsowl.com / 162.159.27.98: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok (67m46). COOKIE: ok. CLIENTSUBNET: ok.
AGood: All SOA have the same Serial Number
Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries.

4. Content- and Performance-critical Checks

AGood: All checks /.well-known/acme-challenge/random-filename without redirects answer with the expected http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 challenge should work. If it doesn't work: Check your vHost configuration (apachectl -S, httpd -S, nginx -T). Every combination of port and ServerName / ServerAlias (Apache) or Server (Nginx) must be unique. Merge duplicated entries in one vHost. If you use an IIS, extensionless files must be allowed in the /.well-known/acme-challenge subdirectory. Create a web.config in that directory. Content: <configuration><system.webServer><staticContent><mimeMap fileExtension="." mimeType="text/plain" /></staticContent></system.webServer></configuration>. If you have a redirect http ⇒ https, that's ok, Letsencrypt follows such redirects to port 80 / 443 (same or other server). There must be a certificate. But the certificate may be expired, self signed or with a not matching domain name. Checking the validation file Letsencrypt ignores such certificate errors. 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: 109930 milliseconds, 109.930 seconds


8. Connections

No connection informations found. Perhaps only http - connections.


9. Certificates

No certificate informations found. Perhaps only http - connections.


10. Last Certificates - Certificate Transparency Log Check

1. Source CertSpotter - active certificates (one check per day)

Issuerlast 7 daysactivenum Certs
CN=E5, O=Let's Encrypt, C=US
3
3
3
CN=E6, O=Let's Encrypt, C=US
2
2
2

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
7679648276
leaf cert
CN=E5, O=Let's Encrypt, C=US
2024-07-10 13:25:27
2024-10-08 13:25:26
www.pyclbnhh.top - 1 entries


7679490322
leaf cert
CN=E6, O=Let's Encrypt, C=US
2024-07-10 12:56:55
2024-10-08 12:56:54
www.pyclbnhh.top - 1 entries


7678971641
leaf cert
CN=E5, O=Let's Encrypt, C=US
2024-07-10 11:14:13
2024-10-08 11:14:12
www.pyclbnhh.top - 1 entries


7678979336
leaf cert
CN=E5, O=Let's Encrypt, C=US
2024-07-10 11:14:11
2024-10-08 11:14:10
www.pyclbnhh.top - 1 entries


7678781603
leaf cert
CN=E6, O=Let's Encrypt, C=US
2024-07-10 10:37:14
2024-10-08 10:37:13
www.pyclbnhh.top - 1 entries



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

Issuerlast 7 daysactivenum Certs
CN=E6, O=Let's Encrypt, C=US
1
1
1

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
13681732548
precert
CN=E6, O=Let's Encrypt, C=US
2024-07-10 08:37:14
2024-10-08 08:37:13
www.pyclbnhh.top
1 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: ns1.dnsowl.com, ns2.dnsowl.com, ns3.dnsowl.com

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

Answer: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net
2
ns1.dnsowl.com: 162.159.26.136, 162.159.27.173, 2400:cb00:2049:1::a29f:1a88, 2400:cb00:2049:1::a29f:1bad
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns2.dnsowl.com
162.159.26.49, 162.159.27.130, 2400:cb00:2049:1::a29f:1a31, 2400:cb00:2049:1::a29f:1b82

Answer: ns3.dnsowl.com
162.159.26.234, 162.159.27.98, 2400:cb00:2049:1::a29f:1aea, 2400:cb00:2049:1::a29f:1b62


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.pyclbnhh.top
0

no CAA entry found
1
0
pyclbnhh.top
0

no CAA entry found
1
0
top
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
pyclbnhh.top

ok
1
0
www.pyclbnhh.top

ok
1
0
_acme-challenge.pyclbnhh.top

Name Error - The domain name does not exist
1
0
_acme-challenge.www.pyclbnhh.top

Name Error - The domain name does not exist
1
0
_acme-challenge.pyclbnhh.top.pyclbnhh.top

Name Error - The domain name does not exist
1
0
_acme-challenge.www.pyclbnhh.top.pyclbnhh.top

Name Error - The domain name does not exist
1
0
_acme-challenge.www.pyclbnhh.top.www.pyclbnhh.top

Name Error - The domain name does not exist
1
0


15. DomainService - Entries (SPF-Check is alpha - 2024-06-22, DMARC-Detailcheck is alpha - 2024-07-06)

No DomainServiceEntries entries found



16. Cipher Suites

No results


17. Portchecks

DomainIPPortDescriptionResultAnswer
www.pyclbnhh.top
38.49.46.78
21
FTP



www.pyclbnhh.top
38.49.46.78
21
FTP



www.pyclbnhh.top
38.49.46.78
22
SSH
open
SSH-2.0-OpenSSH_8.9p1 Ubuntu-3ubuntu0.10

www.pyclbnhh.top
38.49.46.78
22
SSH
open
SSH-2.0-OpenSSH_8.9p1 Ubuntu-3ubuntu0.10
Bad: SSH without DNS SSHFP Record found
Possible DNS SSHFP Entries:
www.pyclbnhh.top IN SSHFP 3 2 f470d35f865295af3524fd79b49c4375be1a39d62e7395be180ecb9c7baf33a8
www.pyclbnhh.top IN SSHFP 4 2 e46e56977a893abdcb65acd04e7222122211e003fb8c3b2a8cefb4c1afd222eb
www.pyclbnhh.top
38.49.46.78
25
SMTP



www.pyclbnhh.top
38.49.46.78
25
SMTP



www.pyclbnhh.top
38.49.46.78
53
DNS



www.pyclbnhh.top
38.49.46.78
53
DNS



www.pyclbnhh.top
38.49.46.78
110
POP3



www.pyclbnhh.top
38.49.46.78
110
POP3



www.pyclbnhh.top
38.49.46.78
143
IMAP



www.pyclbnhh.top
38.49.46.78
143
IMAP



www.pyclbnhh.top
38.49.46.78
465
SMTP (encrypted)



www.pyclbnhh.top
38.49.46.78
465
SMTP (encrypted)



www.pyclbnhh.top
38.49.46.78
587
SMTP (encrypted, submission)



www.pyclbnhh.top
38.49.46.78
587
SMTP (encrypted, submission)



www.pyclbnhh.top
38.49.46.78
993
IMAP (encrypted)



www.pyclbnhh.top
38.49.46.78
993
IMAP (encrypted)



www.pyclbnhh.top
38.49.46.78
995
POP3 (encrypted)



www.pyclbnhh.top
38.49.46.78
995
POP3 (encrypted)



www.pyclbnhh.top
38.49.46.78
1433
MS SQL



www.pyclbnhh.top
38.49.46.78
1433
MS SQL



www.pyclbnhh.top
38.49.46.78
2082
cPanel (http)



www.pyclbnhh.top
38.49.46.78
2082
cPanel (http)



www.pyclbnhh.top
38.49.46.78
2083
cPanel (https)



www.pyclbnhh.top
38.49.46.78
2083
cPanel (https)



www.pyclbnhh.top
38.49.46.78
2086
WHM (http)



www.pyclbnhh.top
38.49.46.78
2086
WHM (http)



www.pyclbnhh.top
38.49.46.78
2087
WHM (https)



www.pyclbnhh.top
38.49.46.78
2087
WHM (https)



www.pyclbnhh.top
38.49.46.78
2089
cPanel Licensing



www.pyclbnhh.top
38.49.46.78
2089
cPanel Licensing



www.pyclbnhh.top
38.49.46.78
2095
cPanel Webmail (http)



www.pyclbnhh.top
38.49.46.78
2095
cPanel Webmail (http)



www.pyclbnhh.top
38.49.46.78
2096
cPanel Webmail (https)



www.pyclbnhh.top
38.49.46.78
2096
cPanel Webmail (https)



www.pyclbnhh.top
38.49.46.78
2222
DirectAdmin (http)



www.pyclbnhh.top
38.49.46.78
2222
DirectAdmin (http)



www.pyclbnhh.top
38.49.46.78
2222
DirectAdmin (https)



www.pyclbnhh.top
38.49.46.78
2222
DirectAdmin (https)



www.pyclbnhh.top
38.49.46.78
3306
mySql



www.pyclbnhh.top
38.49.46.78
3306
mySql



www.pyclbnhh.top
38.49.46.78
5224
Plesk Licensing



www.pyclbnhh.top
38.49.46.78
5224
Plesk Licensing



www.pyclbnhh.top
38.49.46.78
5432
PostgreSQL



www.pyclbnhh.top
38.49.46.78
5432
PostgreSQL



www.pyclbnhh.top
38.49.46.78
8080
Ookla Speedtest (http)



www.pyclbnhh.top
38.49.46.78
8080
Ookla Speedtest (http)



www.pyclbnhh.top
38.49.46.78
8080
Ookla Speedtest (https)



www.pyclbnhh.top
38.49.46.78
8080
Ookla Speedtest (https)



www.pyclbnhh.top
38.49.46.78
8083
VestaCP http



www.pyclbnhh.top
38.49.46.78
8083
VestaCP http



www.pyclbnhh.top
38.49.46.78
8083
VestaCP https



www.pyclbnhh.top
38.49.46.78
8083
VestaCP https



www.pyclbnhh.top
38.49.46.78
8443
Plesk Administration (https)



www.pyclbnhh.top
38.49.46.78
8443
Plesk Administration (https)



www.pyclbnhh.top
38.49.46.78
8447
Plesk Installer + Updates



www.pyclbnhh.top
38.49.46.78
8447
Plesk Installer + Updates



www.pyclbnhh.top
38.49.46.78
8880
Plesk Administration (http)



www.pyclbnhh.top
38.49.46.78
8880
Plesk Administration (http)



www.pyclbnhh.top
38.49.46.78
10000
Webmin (http)



www.pyclbnhh.top
38.49.46.78
10000
Webmin (http)



www.pyclbnhh.top
38.49.46.78
10000
Webmin (https)



www.pyclbnhh.top
38.49.46.78
10000
Webmin (https)





Permalink: https://check-your-website.server-daten.de/?i=51d3de08-286d-43ce-b813-976e00d2d4c8


Last Result: https://check-your-website.server-daten.de/?q=pyclbnhh.top - 2024-07-10 16:41:17


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

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