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



T

Timeout

Checked:
07.07.2019 08:58:35


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
malkahtani.com
A
184.168.221.41
Scottsdale/Arizona/United States (US) - GoDaddy.com, LLC
Hostname: ip-184-168-221-41.ip.secureserver.net
yes
2
0

AAAA

yes


www.malkahtani.com
CNAME
malkahtani.com
yes
1
0

A
184.168.221.41
Scottsdale/Arizona/United States (US) - GoDaddy.com, LLC
Hostname: ip-184-168-221-41.ip.secureserver.net
yes


www.malkahtani.com
A
50.63.202.35
Scottsdale/Arizona/United States (US) - GoDaddy.com, LLC
No Hostname found
no



2. DNSSEC

Zone (*)DNSSEC - Informations

Zone: (root)
(root)
1 DS RR published



Status: Valid because published



3 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 25266, Flags 256



Public Key with Algorithm 8, KeyTag 59944, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 22.07.2019, 00:00:00 +, Signature-Inception: 01.07.2019, 00:00:00 +, KeyTag 20326, Signer-Name: (root)



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



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

Zone: com
com
1 DS RR in the parent zone found



1 RRSIG RR to validate DS RR found



RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 20.07.2019, 05:00:00 +, Signature-Inception: 07.07.2019, 04:00:00 +, KeyTag 59944, Signer-Name: (root)



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



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 3800, Flags 256



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



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 16.07.2019, 18:25:33 +, Signature-Inception: 01.07.2019, 18:20:33 +, KeyTag 30909, Signer-Name: com



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



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

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



DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed query name "8pcufad5qh4ikvbhp6987ifsr4kfo7bq" between the hashed NSEC3-owner "8pctcc9dj816mvn02maa3a9h31rvjn3n" and the hashed NextOwner "8pd16luqr324gujm085hl22gb882bcjp". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 8pctcc9dj816mvn02maa3a9h31rvjn3n.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 13.07.2019, 05:20:51 +, Signature-Inception: 06.07.2019, 04:10:51 +, KeyTag 3800, Signer-Name: com



0 DNSKEY RR found




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


3. Name Servers

DomainNameserverNS-IP
malkahtani.com
  pdns07.domaincontrol.com / p21
97.74.111.53
Scottsdale/Arizona/United States (US) - GoDaddy.com, LLC


 
2603:5:21f1::35
Scottsdale/Arizona/United States (US) - GoDaddy.com


  pdns08.domaincontrol.com / p18
173.201.79.53
Scottsdale/Arizona/United States (US) - GoDaddy.com, LLC


 
2603:5:22f1::35
Scottsdale/Arizona/United States (US) - GoDaddy.com

com
  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. SOA-Entries


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


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


Domain:malkahtani.com
Zone-Name:
Primary:pdns07.domaincontrol.com
Mail:dns.jomax.net
Serial:2019070602
Refresh:28800
Retry:7200
Expire:604800
TTL:600
num Entries:4


5. Screenshots

No Screenshot listed, because no url-check with https + http status 200-299, 400-599 + not-ACME-check found.

6. Url-Checks


:

:
DomainnameHttp-StatusredirectSec.G
• http://www.malkahtani.com/
50.63.202.35
302
http://www.malkahtani.com/MMoQa/
9.336
D
Connection: close
Pragma: no-cache
cache-control: no-cache
Location: /MMoQa/

• http://www.malkahtani.com/MMoQa/

302
http://www.malkahtani.com/NhoPY/MMoQa/
9.327
D
Connection: close
Pragma: no-cache
cache-control: no-cache
Location: /NhoPY/MMoQa/

• http://www.malkahtani.com/NhoPY/MMoQa/

302
http://www.malkahtani.com/ZcPMg/NhoPY/MMoQa/
9.336
D
Connection: close
Pragma: no-cache
cache-control: no-cache
Location: /ZcPMg/NhoPY/MMoQa/

• http://www.malkahtani.com/ZcPMg/NhoPY/MMoQa/

302
http://www.malkahtani.com/LPePc/ZcPMg/NhoPY/MMoQa/
9.333
D
Connection: close
Pragma: no-cache
cache-control: no-cache
Location: /LPePc/ZcPMg/NhoPY/MMoQa/

• http://malkahtani.com/
184.168.221.41
200

3.377
H
Cache-Control: no-cache
Pragma: no-cache
Content-Type: text/html; charset=utf-8
Expires: -1
Server: Microsoft-IIS/7.5
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
Date: Sun, 07 Jul 2019 06:59:06 GMT
Content-Length: 457
Age: 3
Connection: close

• http://www.malkahtani.com/
184.168.221.41
200

0.370
H
Cache-Control: no-cache
Pragma: no-cache
Content-Type: text/html; charset=utf-8
Expires: -1
Server: Microsoft-IIS/7.5
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
Date: Sun, 07 Jul 2019 06:59:06 GMT
Content-Length: 465
Age: 1
Connection: close

• https://malkahtani.com/
184.168.221.41
-14

10.026
T
Timeout - The operation has timed out

• https://www.malkahtani.com/
50.63.202.35
-14

10.027
T
Timeout - The operation has timed out

• https://www.malkahtani.com/
184.168.221.41
-14

10.026
T
Timeout - The operation has timed out

• http://malkahtani.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
184.168.221.41
302
http://malkahtani.com/eNeLn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
9.327
D
Visible Content:
Connection: close
Pragma: no-cache
cache-control: no-cache
Location: /eNeLn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

• http://www.malkahtani.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
50.63.202.35
302
http://www.malkahtani.com/LQiVV/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
9.336
D
Visible Content:
Connection: close
Pragma: no-cache
cache-control: no-cache
Location: /LQiVV/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

• http://www.malkahtani.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
184.168.221.41
302
http://www.malkahtani.com/aQgKN/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
9.333
D
Visible Content:
Connection: close
Pragma: no-cache
cache-control: no-cache
Location: /aQgKN/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

• http://www.malkahtani.com/aQgKN/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

302
http://www.malkahtani.com/noRWl/aQgKN/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
9.324
D
Visible Content:
Connection: close
Pragma: no-cache
cache-control: no-cache
Location: /noRWl/aQgKN/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

• http://www.malkahtani.com/LQiVV/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

302
http://www.malkahtani.com/QQRRg/LQiVV/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
9.336
D
Visible Content:
Connection: close
Pragma: no-cache
cache-control: no-cache
Location: /QQRRg/LQiVV/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

• http://www.malkahtani.com/noRWl/aQgKN/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

302
http://www.malkahtani.com/SZTLj/noRWl/aQgKN/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
9.327
D
Visible Content:
Connection: close
Pragma: no-cache
cache-control: no-cache
Location: /SZTLj/noRWl/aQgKN/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

• http://www.malkahtani.com/QQRRg/LQiVV/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

302
http://www.malkahtani.com/lMYWW/QQRRg/LQiVV/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
9.336
D
Visible Content:
Connection: close
Pragma: no-cache
cache-control: no-cache
Location: /lMYWW/QQRRg/LQiVV/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

• http://malkahtani.com/eNeLn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

200

3.387

Visible Content:
Cache-Control: no-cache
Pragma: no-cache
Content-Type: text/html; charset=utf-8
Expires: -1
Server: Microsoft-IIS/7.5
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
Date: Sun, 07 Jul 2019 07:00:26 GMT
Content-Length: 457
Age: 4
Connection: close

7. Comments


1. General Results, most used to calculate the result

Aname "malkahtani.com" is domain, public suffix is "com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services"
Agood: All ip addresses are public addresses
Agood: No asked Authoritative Name Server had a timeout
AGood: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
CError - more then one version with Http-Status 200. After all redirects, all users (and search engines) should see the same https url: Non-www or www, but not both with http status 200.
Dhttp://www.malkahtani.com/MMoQa/
302
http://www.malkahtani.com/NhoPY/MMoQa/
Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
Dhttp://www.malkahtani.com/ZcPMg/NhoPY/MMoQa/
302
http://www.malkahtani.com/LPePc/ZcPMg/NhoPY/MMoQa/
Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
Dhttp://www.malkahtani.com/NhoPY/MMoQa/
302
http://www.malkahtani.com/ZcPMg/NhoPY/MMoQa/
Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
Dhttp://www.malkahtani.com/ 50.63.202.35
302
http://www.malkahtani.com/MMoQa/
Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
Dhttp://malkahtani.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 184.168.221.41
302
http://malkahtani.com/eNeLn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
Dhttp://www.malkahtani.com/aQgKN/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
302
http://www.malkahtani.com/noRWl/aQgKN/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
Dhttp://www.malkahtani.com/LQiVV/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
302
http://www.malkahtani.com/QQRRg/LQiVV/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
Dhttp://www.malkahtani.com/noRWl/aQgKN/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
302
http://www.malkahtani.com/SZTLj/noRWl/aQgKN/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
Dhttp://www.malkahtani.com/QQRRg/LQiVV/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
302
http://www.malkahtani.com/lMYWW/QQRRg/LQiVV/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
Dhttp://www.malkahtani.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 50.63.202.35
302
http://www.malkahtani.com/LQiVV/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
Dhttp://www.malkahtani.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 184.168.221.41
302
http://www.malkahtani.com/aQgKN/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
Wrong redirect one domain http to other domain http. First redirect to https without changing the domain, so no new dns query is required. So the server can send the HSTS header. That's fundamental using HSTS (Http Strict Transport Security). First step: Add correct redirects http ⇒ https. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop. Then recheck your domain, should be Grade C. There is the rule to select one https version as preferred version.
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.
Khttp://www.malkahtani.com/ 184.168.221.41, Status 200

http://www.malkahtani.com/ 50.63.202.35, Status 302
configuration problem - different ip addresses with different status

2. DNS- and NameServer - Checks

AGood: Nameserver supports TCP connections: 4 good Nameserver
AGood: Nameserver supports Echo Capitalization: 4 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 4 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 4 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.

3. Content- and Performance-critical Checks

http://malkahtani.com/eNeLn/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
200

Warning: Not existing ACME-file, but Server sends 200, not 404 or redirect. May be a problem creating a Letsencrypt certificate. Checking /.well-known/acme-challenge/random-filename - a http status 404 - Not Found - is expected. If your server sends content and a http status 200, the validation file (87 bytes, token, dot and the hash of the public part of the account key) may be invisible, so Letsencrypt can't validate your domain. If it is an application that sends this content, perhaps create an exception, so /.well-known/acme-challenge sends raw files. Or create a redirect to another domain and / or port 443, but your Letsencrypt client must support such a solution. Certbot: Use webroot as authenticator - https://certbot.eff.org/docs/using.html Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
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: 169190 milliseconds, 169.190 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

Summary

No data found or small Code-update

Details

Small Code Update - wait one minute


12. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers:

No NameServer - IP address informations found. The feature is new (2020-05-07), so recheck this domain.


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.malkahtani.com



1
0
malkahtani.com
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
malkahtani.com
google-site-verification=X9ZNxHaNrHK60pc7H2OfAOCpi-zIY9ENOD2w4KoeZi4
ok
1
0
malkahtani.com
v=spf1 include:_spf.google.com ~all
ok
1
0
www.malkahtani.com
google-site-verification=X9ZNxHaNrHK60pc7H2OfAOCpi-zIY9ENOD2w4KoeZi4
ok
1
0
www.malkahtani.com
v=spf1 include:_spf.google.com ~all
ok
1
0
_acme-challenge.malkahtani.com

Name Error - The domain name does not exist
1
0
_acme-challenge.www.malkahtani.com

Name Error - The domain name does not exist
1
0
_acme-challenge.malkahtani.com.malkahtani.com

Name Error - The domain name does not exist
1
0
_acme-challenge.www.malkahtani.com.malkahtani.com

Name Error - The domain name does not exist
1
0
_acme-challenge.www.malkahtani.com.www.malkahtani.com

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 Ciphers found


17. Portchecks

No Port informations found. The feature is new (startet 2019-07-09), so recheck this domain.



Permalink: https://check-your-website.server-daten.de/?i=9488257c-d58b-4446-a5fb-3865c829fcd2


Last Result: https://check-your-website.server-daten.de/?q=malkahtani.com - 2019-07-07 08:58:35


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

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

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